You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Alex Heneveld <al...@cloudsoftcorp.com> on 2014/04/25 12:03:57 UTC
Re: [PROPOSAL] Brooklyn -- merging mailing lists
Henry,
Gotcha. So with that in mind, our users list is not so active that it
couldn't be merged with the dev list. And we'd like to get existing
users more deeply involved!
So +1 to Henry's suggestion to have a dev@ list but *not* a users@ list
initially as we seek to enter the Apache incubator.
Copying both brooklyn-* lists here in case anyone in the existing
community really wants to to *keep* the users list.
Best
Alex
On 25/04/2014 00:34, Henry Saputra wrote:
> Hi Alex,
>
> Looking forward for Brooklyn as part of ASF incubator, awesome project.
>
> Most existing projects that come to Apache incubator already had user
> and dev lists, but most of the times the IPMCs encourage to have
> initially dev@ list to focus on integration with ASF and also to
> centralized discussion about the development of the project.
>
> But, if both lists are active and have a lot of posts then by all
> means go ahead to have both lists as proposed.
>
> - Henry
>
>
>
> On Thu, Apr 24, 2014 at 2:19 PM, Alex Heneveld
> <al...@cloudsoftcorp.com> wrote:
>> Hi Henry,
>>
>> Thanks for the feedback. We currently have both a dev and a user list, as
>> Chip notes, and they are used by different people. That's why we thought we
>> should move both across to apache as part of this proposal.
>>
>> Does that make sense in this situation?
>>
>> Best
>> Alex
>>
>>
>>
>> On 24/04/2014 22:07, Chip Childers wrote:
>>> On Thu, Apr 24, 2014 at 12:59:15PM -0700, Henry Saputra wrote:
>>>> Hi Chip,
>>>>
>>>> Like most initial incubator projects, I think you just need dev and
>>>> private lists for start and maybe add user list later?
>>>>
>>>> - Henry
>>> I'll let the Brooklyn community speak up on that topic, since it's their
>>> project.
>>>
>>> That said, I'd note that they are coming in as an existing community
>>> with both a dev and user list in google groups. It would be odd, IMO,
>>> for that to change with a move to the ASF.
>>>
>>> -chip
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [brooklyn-users] [PROPOSAL] Brooklyn -- merging mailing lists
Posted by Jim Jagielski <ji...@jaguNET.com>.
Related-Topic: If an additional Mentor would be beneficial,
I volunteer.
On Apr 25, 2014, at 7:05 AM, Duncan Johnston Watt <du...@cloudsoftcorp.com> wrote:
> +1 to deprecating brooklyn-users and focusing on -dev list.
>
>
> On 25 April 2014 11:03, Alex Heneveld <al...@cloudsoftcorp.com>wrote:
>
>>
>> Henry,
>>
>> Gotcha. So with that in mind, our users list is not so active that it
>> couldn't be merged with the dev list. And we'd like to get existing users
>> more deeply involved!
>>
>> So +1 to Henry's suggestion to have a dev@ list but *not* a users@ list
>> initially as we seek to enter the Apache incubator.
>>
>> Copying both brooklyn-* lists here in case anyone in the existing
>> community really wants to to *keep* the users list.
>>
>> Best
>> Alex
>>
>>
>> On 25/04/2014 00:34, Henry Saputra wrote:
>>
>>> Hi Alex,
>>>
>>> Looking forward for Brooklyn as part of ASF incubator, awesome project.
>>>
>>> Most existing projects that come to Apache incubator already had user
>>> and dev lists, but most of the times the IPMCs encourage to have
>>> initially dev@ list to focus on integration with ASF and also to
>>> centralized discussion about the development of the project.
>>>
>>> But, if both lists are active and have a lot of posts then by all
>>> means go ahead to have both lists as proposed.
>>>
>>> - Henry
>>>
>>>
>>>
>>> On Thu, Apr 24, 2014 at 2:19 PM, Alex Heneveld
>>> <al...@cloudsoftcorp.com> wrote:
>>>
>>>> Hi Henry,
>>>>
>>>> Thanks for the feedback. We currently have both a dev and a user list,
>>>> as
>>>> Chip notes, and they are used by different people. That's why we thought
>>>> we
>>>> should move both across to apache as part of this proposal.
>>>>
>>>> Does that make sense in this situation?
>>>>
>>>> Best
>>>> Alex
>>>>
>>>>
>>>>
>>>> On 24/04/2014 22:07, Chip Childers wrote:
>>>>
>>>>> On Thu, Apr 24, 2014 at 12:59:15PM -0700, Henry Saputra wrote:
>>>>>
>>>>>> Hi Chip,
>>>>>>
>>>>>> Like most initial incubator projects, I think you just need dev and
>>>>>> private lists for start and maybe add user list later?
>>>>>>
>>>>>> - Henry
>>>>>>
>>>>> I'll let the Brooklyn community speak up on that topic, since it's their
>>>>> project.
>>>>>
>>>>> That said, I'd note that they are coming in as an existing community
>>>>> with both a dev and user list in google groups. It would be odd, IMO,
>>>>> for that to change with a move to the ASF.
>>>>>
>>>>> -chip
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "brooklyn-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to brooklyn-users+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Duncan Johnston-Watt
> CEO | Cloudsoft Corporation
>
> Twitter | @duncanjw
> Mobile | +44 777 190 2653
> Skype | duncan_johnstonwatt
> Linkedin | www.linkedin.com/in/duncanjohnstonwatt
>
> Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
> Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
>
> This e-mail message is confidential and for use by the addressee only. If
> the message is received by anyone other than the addressee, please return
> the message to the sender by replying to it and then delete the message
> from your computer. Internet e-mails are not necessarily secure. Cloudsoft
> Corporation Limited does not accept responsibility for changes made to this
> message after it was sent.
>
> Whilst all reasonable care has been taken to avoid the transmission of
> viruses, it is the responsibility of the recipient to ensure that the
> onward transmission, opening or use of this message and any attachments
> will not adversely affect its systems or data. No responsibility is
> accepted by Cloudsoft Corporation Limited in this regard and the recipient
> should carry out such virus and other checks as it considers appropriate.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [brooklyn-users] Re: [PROPOSAL] Brooklyn -- merging mailing lists
Posted by Duncan Johnston Watt <du...@cloudsoftcorp.com>.
+1 to deprecating brooklyn-users and focusing on -dev list.
On 25 April 2014 11:03, Alex Heneveld <al...@cloudsoftcorp.com>wrote:
>
> Henry,
>
> Gotcha. So with that in mind, our users list is not so active that it
> couldn't be merged with the dev list. And we'd like to get existing users
> more deeply involved!
>
> So +1 to Henry's suggestion to have a dev@ list but *not* a users@ list
> initially as we seek to enter the Apache incubator.
>
> Copying both brooklyn-* lists here in case anyone in the existing
> community really wants to to *keep* the users list.
>
> Best
> Alex
>
>
> On 25/04/2014 00:34, Henry Saputra wrote:
>
>> Hi Alex,
>>
>> Looking forward for Brooklyn as part of ASF incubator, awesome project.
>>
>> Most existing projects that come to Apache incubator already had user
>> and dev lists, but most of the times the IPMCs encourage to have
>> initially dev@ list to focus on integration with ASF and also to
>> centralized discussion about the development of the project.
>>
>> But, if both lists are active and have a lot of posts then by all
>> means go ahead to have both lists as proposed.
>>
>> - Henry
>>
>>
>>
>> On Thu, Apr 24, 2014 at 2:19 PM, Alex Heneveld
>> <al...@cloudsoftcorp.com> wrote:
>>
>>> Hi Henry,
>>>
>>> Thanks for the feedback. We currently have both a dev and a user list,
>>> as
>>> Chip notes, and they are used by different people. That's why we thought
>>> we
>>> should move both across to apache as part of this proposal.
>>>
>>> Does that make sense in this situation?
>>>
>>> Best
>>> Alex
>>>
>>>
>>>
>>> On 24/04/2014 22:07, Chip Childers wrote:
>>>
>>>> On Thu, Apr 24, 2014 at 12:59:15PM -0700, Henry Saputra wrote:
>>>>
>>>>> Hi Chip,
>>>>>
>>>>> Like most initial incubator projects, I think you just need dev and
>>>>> private lists for start and maybe add user list later?
>>>>>
>>>>> - Henry
>>>>>
>>>> I'll let the Brooklyn community speak up on that topic, since it's their
>>>> project.
>>>>
>>>> That said, I'd note that they are coming in as an existing community
>>>> with both a dev and user list in google groups. It would be odd, IMO,
>>>> for that to change with a move to the ASF.
>>>>
>>>> -chip
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "brooklyn-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to brooklyn-users+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
Duncan Johnston-Watt
CEO | Cloudsoft Corporation
Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.