You are viewing a plain text version of this content. The canonical link for it is here.
Posted to discuss@petri.apache.org by Justin Erenkrantz <ju...@erenkrantz.com> on 2020/04/25 15:39:52 UTC
Buildstream migration tasks
Hi discuss@,
As posted on buildstream-list@gnome.org [1], we'd like to begin migrating
Buildstream over to the ASF. As mentors, Sander and I feel that the rough
priority list should be as follows:
1) Migration of the relevant mailing lists
2) Migration of the source code to ASF (including CLAs/software grants as
necessary)
3) Conducting a Buildstream release under the ASF auspices and rules
4) Migrate the website and other public documentation to ASF
Once these items are completed, I believe that Buildstream would be able to
stand on its own as a independent PMC. Until then, we'd keep in
coordination with the Petri PMC.
GUADEC 2020 is coming up in late July, so we'd like to demonstrate progress
by then; I don't believe that we have to have everything completed by then,
but it's a good milestone to work towards.
For the lists, we'd like to avoid having to rename the lists and
infrastructure at a later date. How does the Petri PMC feel about this? I
know that the Incubator prefers an intermediate step of going to <podling>-
dev@incubator.apache.org ; but, for existing OSS communities trying to come
in, that'd be 2 additional changes. So, how do we feel about going
straight to the eventual TLP domain? We can definitely have suitable
disclaimers on the releases and websites until there is an independent PMC
stood up.
Sander and I have kicked around builds.apache.org as the eventual domain
for Buildstream as we eventually seeing it become an umbrella PMC with
other build-related projects - as such Buildstream as the TLP name might
not be ideal. That said, there already exists a builds.apache.org for the
ASF CI tooling...so, I think that we're open to other suggestions here -
we'll also solicit feedback from the existing Buildstream community in
parallel.
Once we agree upon the domain name, we'd want to request creation of a dev@
and private@ list and then we can start on migrating traffic and begin
coordination steps 2-4 above on those mailing lists.
Cheers. -- justin
1. https://mail.gnome.org/archives/buildstream-list/2020-April/msg00010.html
Re: Buildstream migration tasks
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Justin Erenkrantz wrote on Fri, 29 May 2020 17:15 -0400:
> On Thu, May 28, 2020 at 1:24 PM Dave Fisher <wa...@apache.org> wrote:
>
> > >> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183
> > >
> > > I had reviewed this last week. I added a comment to “ping” VP, Brand.
> >
> > Mark has approved the name search.
> >
>
> Cool. I've filed a JIRA to create buildstream.apache.org domain:
>
> https://issues.apache.org/jira/browse/INFRA-20355
>
> Once that is completed, I'll request the creation of the mailing lists.
> (I'm an officer, so I think that I might be able to self-service request
> that; but, happy to defer that request to others if desired.)
If anything, I'd have recommended that a Buildstream community member
with less Apache experience request the mailing lists and us (= petri,
mentors, etc) simply sign off on the request — to share the workload and
transfer knowledge (in this case, knowledge of what Infra is to projects
and how to interface with them) — but I don't think the tooling supports
this.
> Have a great weekend! -- justin
Cheers,
Daniel
Re: Buildstream migration tasks
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On Thu, May 28, 2020 at 1:24 PM Dave Fisher <wa...@apache.org> wrote:
> >> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183
> >
> > I had reviewed this last week. I added a comment to “ping” VP, Brand.
>
> Mark has approved the name search.
>
Cool. I've filed a JIRA to create buildstream.apache.org domain:
https://issues.apache.org/jira/browse/INFRA-20355
Once that is completed, I'll request the creation of the mailing lists.
(I'm an officer, so I think that I might be able to self-service request
that; but, happy to defer that request to others if desired.)
Have a great weekend! -- justin
Re: Buildstream migration tasks
Posted by Dave Fisher <wa...@apache.org>.
> On May 27, 2020, at 10:26 AM, Dave Fisher <wa...@apache.org> wrote:
>
>
>
>> On May 27, 2020, at 10:16 AM, Justin Erenkrantz <ju...@erenkrantz.com> wrote:
>>
>> On Wed, May 6, 2020 at 9:59 PM Greg Stein <gs...@gmail.com> 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.
Mark has approved the name search.
>
>>
>> Once that is completed, we'd like to proceed with the mailing list creation
>> - specifically: dev@buildstream.apache.org and
>> private@buildstream.apache.org.
>>
>> 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
>> buildstream-list@gnome.org 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
>
Re: Buildstream migration tasks
Posted by Dave Fisher <wa...@apache.org>.
> On May 27, 2020, at 10:16 AM, Justin Erenkrantz <ju...@erenkrantz.com> wrote:
>
> On Wed, May 6, 2020 at 9:59 PM Greg Stein <gs...@gmail.com> 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: dev@buildstream.apache.org and
> private@buildstream.apache.org.
>
> 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
> buildstream-list@gnome.org 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
Re: Buildstream migration tasks
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On Wed, May 6, 2020 at 9:59 PM Greg Stein <gs...@gmail.com> 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
Once that is completed, we'd like to proceed with the mailing list creation
- specifically: dev@buildstream.apache.org and
private@buildstream.apache.org.
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
buildstream-list@gnome.org 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?
Thanks. -- justin
Re: Buildstream migration tasks
Posted by Greg Stein <gs...@gmail.com>.
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 ?
On Sat, May 2, 2020 at 2:01 PM Sander Striker <s....@striker.nl> wrote:
> Hi Dave,
>
> Funnily enough I have that page in my recent browser history. "
> builds.apache.org" is indeed not the most practical in that sense. I
> guess
> we run into one of the top problems in engineering again, naming things. I
> need to be a in a more creative mood for that, as currently only
> "construction site" and "redibute" spring to mind. The latter being short
> for REpeatable DIstributable BUild and TEst... If anyone has a lightbulb
> moment...
>
> Cheers,
>
> Sander
>
>
> On Sat, May 2, 2020, 17:57 Dave Fisher <wa...@apache.org> wrote:
>
> > -1 on builds.apache.org. This sub domain is used for Infrastructure
> > Jenkins by almost every Apache project. I’m surprised you haven’t
> noticed.
> >
> > Sent from my iPhone
> >
> > > On May 2, 2020, at 5:02 AM, Sander Striker <s....@striker.nl>
> wrote:
> > >
> > > On Sat, Apr 25, 2020 at 7:34 PM Daniel Shahaf <d.s@daniel.shahaf.name
> >
> > > wrote:
> > >
> > >> Justin Erenkrantz wrote on Sat, 25 Apr 2020 15:39 +00:00:
> > >>> For the lists, we'd like to avoid having to rename the lists and
> > >>> infrastructure at a later date. How does the Petri PMC feel about
> > >> this? I
> > >>> know that the Incubator prefers an intermediate step of going to
> > >> <podling>-
> > >>> dev@incubator.apache.org ;
> > >>
> > >> The Incubator switched to dev@<podling>.incubator.apache.org and then
> > to
> > >> dev@<podling>.apache.org (e.g., https://nuttx.apache.org/community/).
> > >>
> > >>> but, for existing OSS communities trying to come
> > >>> in, that'd be 2 additional changes. So, how do we feel about going
> > >>> straight to the eventual TLP domain? We can definitely have suitable
> > >>> disclaimers on the releases and websites until there is an
> independent
> > >> PMC
> > >>> stood up.
> > >>
> > >> Sounds good to me, though we might want to give trademarks@ a heads
> up.
> > >>
> > >
> > > FYI, I gave trademarks@ a heads-up.
> > >
> > >
> > >> Cheers,
> > >>
> > >> Daniel
> > >>
> > >
> > > Cheers,
> > >
> > > Sander
> >
> >
>
Re: Buildstream migration tasks
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Dave Fisher wrote on Wed, 06 May 2020 18:36 -0700:
> Apache Continuum
Already taken; attic'd in 2016: https://continuum.apache.org/
Re: Buildstream migration tasks
Posted by Dave Fisher <wa...@comcast.net>.
A couple of ideas. The wife and I just binged Star Trek: TNG:
Ideas:
Apache Q
Apache Continuum
or
Apache Redbud (REproducibleDistributedBUilDs)
Best Regards,
Dave
Sent from my iPhone
> On May 3, 2020, at 5:25 AM, Greg Stein <gs...@gmail.com> wrote:
>
> haha... this is pretty close-to-home, as I grew up in Oregon, which had a
> huge native indian population that affected naming everywhere. I was just
> yelling about some dufus saying "Tillamook" wrong, over on Skype a few
> hours ago. (synchronicity!!)
>
>> On Sat, May 2, 2020 at 6:48 PM Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>>
>> https://en.wikipedia.org/wiki/Apache#Housing:
>>
>> All people in the Apache tribe lived in one of three types of
>> houses. The first of which is the teepee,
>
>
> I've stayed in teepees out at Kahneeta Hot Springs [1].
>
>
>> for those who lived in
>> the plains. Another type of housing is the [[Wigwam|wickiup]],
>
>
> We had a Wigwam store [2] near where I grew up, and I visited that many
> times since our family was into camping. The gear there was great.
>
> The "Wickiup Reservoir"[3] in Oregon is great for fishing. Spent many
> weekends there, with my father/brother fishing.
>
>
>> an
>> 8-foot-tall (2.4 m) frame of wood held together with yucca fibers
>> and covered in brush usually in the Apache groups in the highlands.
>> [...] The final housing is the hogan, an earthen structure in the
>> desert area that was good for cool keeping in the hot weather of
>> northern Mexico.
>>
>
> Bah. Got nothing more.
>
>
>>
>> HTH. There are a number of nouns in there…
>>
>
> Thank you. Some wonderful ideas, and some excellent childhood nostalgia!
>
> Maybe the Buildstream peeps can find some interesting ideas, from these
> "building" concepts.
>
> Cheers,
> -g
>
> [1] https://en.wikipedia.org/wiki/Kah-Nee-Ta
> [2] https://en.wikipedia.org/wiki/Wigwam_Stores_Inc.
> [3] https://en.wikipedia.org/wiki/Wickiup_Reservoir;"Wickiup Reservoir is
> dubbed as the best lake for brown trout fishing in the state"
Re: Buildstream migration tasks
Posted by Greg Stein <gs...@gmail.com>.
haha... this is pretty close-to-home, as I grew up in Oregon, which had a
huge native indian population that affected naming everywhere. I was just
yelling about some dufus saying "Tillamook" wrong, over on Skype a few
hours ago. (synchronicity!!)
On Sat, May 2, 2020 at 6:48 PM Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> https://en.wikipedia.org/wiki/Apache#Housing:
>
> All people in the Apache tribe lived in one of three types of
> houses. The first of which is the teepee,
I've stayed in teepees out at Kahneeta Hot Springs [1].
> for those who lived in
> the plains. Another type of housing is the [[Wigwam|wickiup]],
We had a Wigwam store [2] near where I grew up, and I visited that many
times since our family was into camping. The gear there was great.
The "Wickiup Reservoir"[3] in Oregon is great for fishing. Spent many
weekends there, with my father/brother fishing.
> an
> 8-foot-tall (2.4 m) frame of wood held together with yucca fibers
> and covered in brush usually in the Apache groups in the highlands.
> [...] The final housing is the hogan, an earthen structure in the
> desert area that was good for cool keeping in the hot weather of
> northern Mexico.
>
Bah. Got nothing more.
>
> HTH. There are a number of nouns in there…
>
Thank you. Some wonderful ideas, and some excellent childhood nostalgia!
Maybe the Buildstream peeps can find some interesting ideas, from these
"building" concepts.
Cheers,
-g
[1] https://en.wikipedia.org/wiki/Kah-Nee-Ta
[2] https://en.wikipedia.org/wiki/Wigwam_Stores_Inc.
[3] https://en.wikipedia.org/wiki/Wickiup_Reservoir;"Wickiup Reservoir is
dubbed as the best lake for brown trout fishing in the state"
Re: Buildstream migration tasks
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
https://en.wikipedia.org/wiki/Apache#Housing:
All people in the Apache tribe lived in one of three types of
houses. The first of which is the teepee, for those who lived in
the plains. Another type of housing is the [[Wigwam|wickiup]], an
8-foot-tall (2.4 m) frame of wood held together with yucca fibers
and covered in brush usually in the Apache groups in the highlands.
[...] The final housing is the hogan, an earthen structure in the
desert area that was good for cool keeping in the hot weather of
northern Mexico.
HTH. There are a number of nouns in there…
Sander Striker wrote on Sat, 02 May 2020 21:01 +0200:
> Hi Dave,
>
> Funnily enough I have that page in my recent browser history. "
> builds.apache.org" is indeed not the most practical in that sense. I guess
> we run into one of the top problems in engineering again, naming things. I
> need to be a in a more creative mood for that, as currently only
> "construction site" and "redibute" spring to mind. The latter being short
> for REpeatable DIstributable BUild and TEst... If anyone has a lightbulb
> moment...
>
> Cheers,
>
> Sander
>
>
> On Sat, May 2, 2020, 17:57 Dave Fisher <wa...@apache.org> wrote:
>
> > -1 on builds.apache.org. This sub domain is used for Infrastructure
> > Jenkins by almost every Apache project. I’m surprised you haven’t noticed.
> >
> > Sent from my iPhone
> >
> > > On May 2, 2020, at 5:02 AM, Sander Striker <s....@striker.nl> wrote:
> > >
> > > On Sat, Apr 25, 2020 at 7:34 PM Daniel Shahaf <d....@daniel.shahaf.name>
> > > wrote:
> > >
> > >> Justin Erenkrantz wrote on Sat, 25 Apr 2020 15:39 +00:00:
> > >>> For the lists, we'd like to avoid having to rename the lists and
> > >>> infrastructure at a later date. How does the Petri PMC feel about
> > >> this? I
> > >>> know that the Incubator prefers an intermediate step of going to
> > >> <podling>-
> > >>> dev@incubator.apache.org ;
> > >>
> > >> The Incubator switched to dev@<podling>.incubator.apache.org and then
> > to
> > >> dev@<podling>.apache.org (e.g., https://nuttx.apache.org/community/).
> > >>
> > >>> but, for existing OSS communities trying to come
> > >>> in, that'd be 2 additional changes. So, how do we feel about going
> > >>> straight to the eventual TLP domain? We can definitely have suitable
> > >>> disclaimers on the releases and websites until there is an independent
> > >> PMC
> > >>> stood up.
> > >>
> > >> Sounds good to me, though we might want to give trademarks@ a heads up.
> > >>
> > >
> > > FYI, I gave trademarks@ a heads-up.
> > >
> > >
> > >> Cheers,
> > >>
> > >> Daniel
> > >>
> > >
> > > Cheers,
> > >
> > > Sander
> >
> >
Re: Buildstream migration tasks
Posted by Sander Striker <s....@striker.nl>.
Hi Dave,
Funnily enough I have that page in my recent browser history. "
builds.apache.org" is indeed not the most practical in that sense. I guess
we run into one of the top problems in engineering again, naming things. I
need to be a in a more creative mood for that, as currently only
"construction site" and "redibute" spring to mind. The latter being short
for REpeatable DIstributable BUild and TEst... If anyone has a lightbulb
moment...
Cheers,
Sander
On Sat, May 2, 2020, 17:57 Dave Fisher <wa...@apache.org> wrote:
> -1 on builds.apache.org. This sub domain is used for Infrastructure
> Jenkins by almost every Apache project. I’m surprised you haven’t noticed.
>
> Sent from my iPhone
>
> > On May 2, 2020, at 5:02 AM, Sander Striker <s....@striker.nl> wrote:
> >
> > On Sat, Apr 25, 2020 at 7:34 PM Daniel Shahaf <d....@daniel.shahaf.name>
> > wrote:
> >
> >> Justin Erenkrantz wrote on Sat, 25 Apr 2020 15:39 +00:00:
> >>> For the lists, we'd like to avoid having to rename the lists and
> >>> infrastructure at a later date. How does the Petri PMC feel about
> >> this? I
> >>> know that the Incubator prefers an intermediate step of going to
> >> <podling>-
> >>> dev@incubator.apache.org ;
> >>
> >> The Incubator switched to dev@<podling>.incubator.apache.org and then
> to
> >> dev@<podling>.apache.org (e.g., https://nuttx.apache.org/community/).
> >>
> >>> but, for existing OSS communities trying to come
> >>> in, that'd be 2 additional changes. So, how do we feel about going
> >>> straight to the eventual TLP domain? We can definitely have suitable
> >>> disclaimers on the releases and websites until there is an independent
> >> PMC
> >>> stood up.
> >>
> >> Sounds good to me, though we might want to give trademarks@ a heads up.
> >>
> >
> > FYI, I gave trademarks@ a heads-up.
> >
> >
> >> Cheers,
> >>
> >> Daniel
> >>
> >
> > Cheers,
> >
> > Sander
>
>
Re: Buildstream migration tasks
Posted by Dave Fisher <wa...@apache.org>.
-1 on builds.apache.org. This sub domain is used for Infrastructure Jenkins by almost every Apache project. I’m surprised you haven’t noticed.
Sent from my iPhone
> On May 2, 2020, at 5:02 AM, Sander Striker <s....@striker.nl> wrote:
>
> On Sat, Apr 25, 2020 at 7:34 PM Daniel Shahaf <d....@daniel.shahaf.name>
> wrote:
>
>> Justin Erenkrantz wrote on Sat, 25 Apr 2020 15:39 +00:00:
>>> For the lists, we'd like to avoid having to rename the lists and
>>> infrastructure at a later date. How does the Petri PMC feel about
>> this? I
>>> know that the Incubator prefers an intermediate step of going to
>> <podling>-
>>> dev@incubator.apache.org ;
>>
>> The Incubator switched to dev@<podling>.incubator.apache.org and then to
>> dev@<podling>.apache.org (e.g., https://nuttx.apache.org/community/).
>>
>>> but, for existing OSS communities trying to come
>>> in, that'd be 2 additional changes. So, how do we feel about going
>>> straight to the eventual TLP domain? We can definitely have suitable
>>> disclaimers on the releases and websites until there is an independent
>> PMC
>>> stood up.
>>
>> Sounds good to me, though we might want to give trademarks@ a heads up.
>>
>
> FYI, I gave trademarks@ a heads-up.
>
>
>> Cheers,
>>
>> Daniel
>>
>
> Cheers,
>
> Sander
Re: Buildstream migration tasks
Posted by Sander Striker <s....@striker.nl>.
On Sat, Apr 25, 2020 at 7:34 PM Daniel Shahaf <d....@daniel.shahaf.name>
wrote:
> Justin Erenkrantz wrote on Sat, 25 Apr 2020 15:39 +00:00:
> > For the lists, we'd like to avoid having to rename the lists and
> > infrastructure at a later date. How does the Petri PMC feel about
> this? I
> > know that the Incubator prefers an intermediate step of going to
> <podling>-
> > dev@incubator.apache.org ;
>
> The Incubator switched to dev@<podling>.incubator.apache.org and then to
> dev@<podling>.apache.org (e.g., https://nuttx.apache.org/community/).
>
> > but, for existing OSS communities trying to come
> > in, that'd be 2 additional changes. So, how do we feel about going
> > straight to the eventual TLP domain? We can definitely have suitable
> > disclaimers on the releases and websites until there is an independent
> PMC
> > stood up.
>
> Sounds good to me, though we might want to give trademarks@ a heads up.
>
FYI, I gave trademarks@ a heads-up.
> Cheers,
>
> Daniel
>
Cheers,
Sander
Re: Buildstream migration tasks
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Justin Erenkrantz wrote on Sat, 25 Apr 2020 15:39 +00:00:
> For the lists, we'd like to avoid having to rename the lists and
> infrastructure at a later date. How does the Petri PMC feel about this? I
> know that the Incubator prefers an intermediate step of going to <podling>-
> dev@incubator.apache.org ;
The Incubator switched to dev@<podling>.incubator.apache.org and then to
dev@<podling>.apache.org (e.g., https://nuttx.apache.org/community/).
> but, for existing OSS communities trying to come
> in, that'd be 2 additional changes. So, how do we feel about going
> straight to the eventual TLP domain? We can definitely have suitable
> disclaimers on the releases and websites until there is an independent PMC
> stood up.
Sounds good to me, though we might want to give trademarks@ a heads up.
Cheers,
Daniel