> On May 27, 2020, at 10:16 AM, Justin Erenkrantz <[email protected]> wrote:
>
> On Wed, May 6, 2020 at 9:59 PM Greg Stein <[email protected]> wrote:
>
>> How about just sticking to buildstream.a.o now, and if/when additional
>> tools want to live at Apache, *then* we can stand up some kind of
>> "collective" of the various tools ?
>>
>
> To close the loop, that's probably the best course of action on balance.
>
> To that end, we have a JIRA filed for the trademark sign-off:
>
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183
I had reviewed this last week. I added a comment to “ping” VP, Brand.
>
> Once that is completed, we'd like to proceed with the mailing list creation
> - specifically: [email protected] and
> [email protected].
>
> Sander and I have a tentative list of whom the initial bootstrap
> subscribers to private@ would be; once that private list is created, we'd
> like to sub them and then have a conversation about expanding the private@
> list further.
>
> Then, we'd start to migrate all of the public conversations from
> [email protected] traffic over to the new dev@ list.
>
> Then, we'd proceed with the software grants, moving code bases over, etc,
> etc.
>
> Any feedback or concerns with this approach?
+1 from me.
Regards,
Dave
>
> Thanks. -- justin
