← Back to team overview

fuel-dev team mailing list archive

Re: Let's close fuel-dev mailing list

 

Is there a way we can simply move all fuel-dev subscriptions over to the
fuel mailinglist?  seamless for current subscribers?
If not... then sure, let's simply tell everyone on this list the URL they
need to hit to re-subscribe to the proper list.

TL;DR:   +3 to Aleksandra.

Kind regards,
-Paul

On Wed, Oct 15, 2014 at 8:30 AM, Dmitry Borodaenko <dborodaenko@xxxxxxxxxxxx
> wrote:

> +2 to Aleksandra
>
> On Wed, Oct 15, 2014 at 6:33 AM, Mike Scherbakov <mscherbakov@xxxxxxxxxxxx
> > wrote:
>
>> +1 to Aleksandra
>>
>> On Wed, Oct 15, 2014 at 5:14 PM, Aleksandra Fedorova <
>> afedorova@xxxxxxxxxxxx> wrote:
>>
>>> By historical reasons we have three general Launchpad groups: fuel-dev,
>>> fuel and fuel-all. Currently none of them has any particular meaning in
>>> terms of Launchpad management: there aren't special access rights, no
>>> assigned bugs and no specific membership policy. fuel-dev and fuel are
>>> open, and fuel-all is delegated, i.e. requires approval.
>>>
>>> And each of them has its own mailing list.
>>>
>>> I suggest we close fuel-dev in favor of openstack-dev@ mailing list,
>>> and close fuel-all completely. But explicitly promote the fuel@
>>> Launchpad mailing lists as an open mailing list for user discussions. The
>>> same way as we have #fuel IRC channel, separate from #fuel-dev.
>>>
>>>
>>> On Wed, Oct 15, 2014 at 4:54 PM, Dmitriy Novakovskiy <
>>> dnovakovskiy@xxxxxxxxxxxx> wrote:
>>>
>>>> Most often I've been reaching out to fuel-dev for generic advice around
>>>> fuel/puppet/fuel way of configuring OpenStack. Whenever discussion has
>>>> ended in bugs - I've reported them. Not sure if putting that kind of
>>>> discussions to openstack-dev w/ fuel tag is the best choice
>>>>
>>>> How about keeping fuel-dev alive/renamed to fuel-community?
>>>>
>>>>
>>>> On Wednesday, October 15, 2014, Matthew Mosesohn <
>>>> mmosesohn@xxxxxxxxxxxx> wrote:
>>>>
>>>>> I like Dmitry's idea. A fuel user's list isn't a terrible idea. I
>>>>> agree that putting dev talk on openstack-dev is just fine and it should
>>>>> encourage other devels.
>>>>> The argument against it, of course, is that any time someone reports a
>>>>> problem on this list, we'll ask them to open a bug in LP.
>>>>>
>>>>> On Wed, Oct 15, 2014 at 4:44 PM, Dmitriy Novakovskiy <
>>>>> dnovakovskiy@xxxxxxxxxxxx> wrote:
>>>>>
>>>>>> So how can should to Fuel people (like me - not contributing code,
>>>>>> but asking questions, reporting bugs, reviewing docs) be in touch w/ fuel
>>>>>> developers? Shall we write to "openstack-dev with '[Fuel]' tag"?
>>>>>>
>>>>>> ---
>>>>>> Regards,
>>>>>>
>>>>>> *Dmitriy Novakovskiy*
>>>>>> Sales Engineer, Mirantis EMEA
>>>>>>
>>>>>> *Skype:* dmitriy.novakovskiy
>>>>>> *Operating from:* Ukraine
>>>>>>
>>>>>> On Wed, Oct 15, 2014 at 12:11 PM, Dmitry Pyzhov <dpyzhov@xxxxxxxxxxxx
>>>>>> > wrote:
>>>>>>
>>>>>>> Ok,
>>>>>>>
>>>>>>> I'm going to kill this list by lazy consensus
>>>>>>> <http://www.apache.org/foundation/glossary.html#LazyConsensus> if
>>>>>>> no-one objects within the next three days.
>>>>>>>
>>>>>>> On Fri, Oct 10, 2014 at 12:16 AM, Lukasz Oles <loles@xxxxxxxxxxxx>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 it is really confusing
>>>>>>>>
>>>>>>>> On Thu, Oct 9, 2014 at 9:32 PM, Dmitry Pyzhov <dpyzhov@xxxxxxxxxxxx>
>>>>>>>> wrote:
>>>>>>>> > Guys,
>>>>>>>> >
>>>>>>>> > Not everyone is subscribed to our outdated fuel-dev mailing list.
>>>>>>>> If someone
>>>>>>>> > write to it, he/she does not reach the all of the developers.
>>>>>>>> What is worth,
>>>>>>>> > it is hard to notice. We have migrated to openstack-dev with
>>>>>>>> '[Fuel]' tag.
>>>>>>>> > It was surprise for me that old mailing list is still in use:
>>>>>>>> > https://www.mail-archive.com/fuel-dev@xxxxxxxxxxxxxxxxxxx/
>>>>>>>> >
>>>>>>>> > Let's close fuel-dev list.
>>>>>>>> >
>>>>>>>> > --
>>>>>>>> > Mailing list: https://launchpad.net/~fuel-dev
>>>>>>>> > Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>>>>>>> > Unsubscribe : https://launchpad.net/~fuel-dev
>>>>>>>> > More help   : https://help.launchpad.net/ListHelp
>>>>>>>> >
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Łukasz Oleś
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Mailing list: https://launchpad.net/~fuel-dev
>>>>>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>>>>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Mailing list: https://launchpad.net/~fuel-dev
>>>>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>>>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> --
>>>> ---
>>>> Regards,
>>>>
>>>> *Dmitriy Novakovskiy*
>>>> Sales Engineer, Mirantis EMEA
>>>>
>>>> *Skype:* dmitriy.novakovskiy
>>>> *Operating from:* Ukraine
>>>>
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~fuel-dev
>>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> --
>>> Aleksandra Fedorova
>>> bookwar
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "fuel-core-team" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to fuel-core-team+unsubscribe@xxxxxxxxxxxx.
>>> For more options, visit
>>> https://groups.google.com/a/mirantis.com/d/optout.
>>>
>>
>>
>>
>> --
>> Mike Scherbakov
>> #mihgen
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "fuel-core-team" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to fuel-core-team+unsubscribe@xxxxxxxxxxxx.
>> For more options, visit https://groups.google.com/a/mirantis.com/d/optout
>> .
>>
>
>
>
> --
> Dmitry Borodaenko
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>

Follow ups

References