You are viewing a plain text version of this content. The canonical link for it is here.
Posted to discuss@petri.apache.org by Dave Fisher <wa...@apache.org> on 2022/03/09 16:01:29 UTC
[DISCUSS] Is BuildStream Ready?
BuildStream is nearly ready to become a TLP.
They have cleared up all of the licensing issues in their codebase.
Perhaps the only additional activity I would like to see is a discussion about rolling a Release following the Apache Release Policy on dev@buildstream.a.o
Thoughts?
All the best,
Dave
Re: [DISCUSS] Is BuildStream Ready?
Posted by Greg Stein <gs...@gmail.com>.
Agreed. I will not be able to attend the meeting, but Sander and Humbedooh
will be there. I would assume Dave, too (?).
+1 (binding)
Cheers,
-g
On Tue, Sep 20, 2022 at 6:05 PM Daniel Gruno <hu...@apache.org> wrote:
> No point in waiting another month really, so yes.
>
> On 2022-09-20 17:54, Dave Fisher wrote:
> > Hi Sander,
> >
> > I say we should go for it in tomorrow’s Board Meeting. (I’m not sure if
> I can attend.)
> >
> > Best,
> > Dave
> >
> >> On Sep 20, 2022, at 1:18 PM, Tristan Van Berkom <tv...@apache.org> wrote:
> >>
> >> On 2022/09/20 16:31:02 Dave Fisher wrote:
> >>> IMO Sander’s reply with a Direct to TLP Resolution counts as a request
> from BuildStream.
> >>
> >> +1
> >>
> >> Cheers,
> >> -Tristan
> >>
> >>>
> >>> BR,
> >>> Dave
> >>>
> >>>> On Sep 20, 2022, at 7:46 AM, Daniel Gruno <hu...@apache.org>
> wrote:
> >>>>
> >>>> While I don't see a *ton* of communication on the BuildStream lists,
> I do see some (low/medium activity is just fine in my book), and I have not
> seen anything that would indicate that the project has any misapprehensions
> towards the apache way or our other legal/procedural frameworks. As such, I
> would be in favor of graduation provided the request comes from the
> BuildStream project. If that has already happened, and I missed it, I would
> appreciate a link to this request.
> >>>>
> >>>> With regards,
> >>>> Daniel.
> >>>>
> >>>> On 2022/09/17 13:07:57 Sander Striker wrote:
> >>>>> Hi,
> >>>>>
> >>>>> BuildStream has been in the process of migrating to the ASF as a
> Petri
> >>>>> culture since
> >>>>> early 2020. Of course the past few years have shown to be
> interesting, and
> >>>>> have also
> >>>>> impacted mentor availability. Despite this, the community managed
> to get
> >>>>> the codebase
> >>>>> relicensed, added a new committer, and is getting ready to get its
> 2.0
> >>>>> release over the
> >>>>> line, which would be the first release under the ASF banner.
> >>>>>
> >>>>> I'm sure we can find more i's to dot and more t's to cross, but I
> >>>>> personally don't think that
> >>>>> we need to hold up recognizing BuildStream as an ASF project. Petri
> PMC
> >>>>> members,
> >>>>> what are your thoughts on the matter?
> >>>>>
> >>>>> I've included a draft resolution below for your convenience and
> >>>>> consideration.
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Sander
> >>>>> --
> >>>>> Establish the Apache BuildStream Project
> >>>>>
> >>>>> WHEREAS, the Board of Directors deems it to be in the best interests
> of
> >>>>> the Foundation and consistent with the Foundation's purpose to
> >>>>> establish a Project Management Committee charged with the creation
> and
> >>>>> maintenance of open-source software, for distribution at no charge to
> >>>>> the public, related to efficiently and correctly developing, building
> >>>>> and integrating software stacks.
> >>>>>
> >>>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >>>>> (PMC), to be known as the "Apache BuildStream Project", be and hereby
> >>>>> is established pursuant to Bylaws of the Foundation; and be it
> further
> >>>>>
> >>>>> RESOLVED, that the Apache BuildStream be and hereby is responsible
> for
> >>>>> the creation and maintenance of software related to efficiently and
> >>>>> correctly developing, building and integrating software stacks; and
> be
> >>>>> it further
> >>>>>
> >>>>> RESOLVED, that the office of "Vice President, Apache BuildStream" be
> >>>>> and hereby is created, the person holding such office to serve at the
> >>>>> direction of the Board of Directors as the chair of the Apache
> >>>>> BuildStream Project, and to have primary responsibility for
> management
> >>>>> of the projects within the scope of responsibility of the Apache
> >>>>> BuildStream Project; and be it further
> >>>>>
> >>>>> RESOLVED, that the persons listed immediately below be and hereby are
> >>>>> appointed to serve as the initial members of the Apache BuildStream
> >>>>> Project:
> >>>>>
> >>>>> * Tristan Van Berkom <tv...@apache.org>
> >>>>> * Jürg Billeter <ju...@apache.org>
> >>>>> * Abderrahim Kitouni <ak...@apache.org>
> >>>>> * Benjamin Schubert <be...@apache.org>
> >>>>> * Chandan Singh <ch...@apache.org>
> >>>>> * Sander Striker <st...@apache.org>
> >>>>>
> >>>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tristan Van Berkom be
> >>>>> appointed to the office of Vice President, Apache BuildStream, to
> serve
> >>>>> in accordance with and subject to the direction of the Board of
> >>>>> Directors and the Bylaws of the Foundation until death, resignation,
> >>>>> retirement, removal or disqualification, or until a successor is
> >>>>> appointed.
> >>>>>
> >>>>> On Fri, Sep 16, 2022 at 9:37 AM Sander Striker <s....@striker.nl>
> wrote:
> >>>>>
> >>>>>> Hi Dave,
> >>>>>>
> >>>>>> On 2, this was already done:
> >>>>>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183.
> >>>>>>
> >>>>>> Is there anything else that would be prohibiting the submission of
> the
> >>>>>> Direct to TLP Resolution?
> >>>>>>
> >>>>>> Cheers,
> >>>>>>
> >>>>>> Sander
> >>>>>>
> >>>>>> On Mon, Aug 8, 2022 at 9:28 PM Dave Fisher <wa...@apache.org> wrote:
> >>>>>>
> >>>>>>> Hi -
> >>>>>>>
> >>>>>>> BuildStream is close to ready.
> >>>>>>>
> >>>>>>> See
> https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05 and
> >>>>>>> https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05
> >>>>>>>
> >>>>>>> I think that next steps are:
> >>>>>>>
> >>>>>>> (1) Prepare a Direct to TLP Resolution for the September board
> meeting.
> >>>>>>> (2) Do a Podling Name Search so that the resolution will get a
> green
> >>>>>>> checkbox.
> >>>>>>> (3) Question? Does the website need to be compliant before
> becoming a
> >>>>>>> TLP? (I think no, but want to be prepared if the board disagrees.)
> >>>>>>> (4) Anything else?
> >>>>>>>
> >>>>>>> The Petri Board report is due on Friday and I want to include the
> results
> >>>>>>> of this discussion in the report.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Dave
> >>>>>>>
> >>>>>>>> On Jul 21, 2022, at 12:33 PM, Dave Fisher <wa...@apache.org>
> wrote:
> >>>>>>>>
> >>>>>>>> Hey Petri Peeps,
> >>>>>>>>
> >>>>>>>> We need to discuss BuildStream’s status and how we will help
> bring this
> >>>>>>> to a TLP establishing Board Resolution.
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> Dave
> >>>>>>>>
> >>>>>>>>> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
> >>>>>>>>>
> >>>>>>>>> BuildStream is nearly ready to become a TLP.
> >>>>>>>>>
> >>>>>>>>> They have cleared up all of the licensing issues in their
> codebase.
> >>>>>>>>>
> >>>>>>>>> Perhaps the only additional activity I would like to see is a
> >>>>>>> discussion about rolling a Release following the Apache Release
> Policy on
> >>>>>>> dev@buildstream.a.o
> >>>>>>>>>
> >>>>>>>>> Thoughts?
> >>>>>>>>>
> >>>>>>>>> All the best,
> >>>>>>>>> Dave
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>
> >>>
> >
>
>
Re: [DISCUSS] Is BuildStream Ready?
Posted by Daniel Gruno <hu...@apache.org>.
No point in waiting another month really, so yes.
On 2022-09-20 17:54, Dave Fisher wrote:
> Hi Sander,
>
> I say we should go for it in tomorrow’s Board Meeting. (I’m not sure if I can attend.)
>
> Best,
> Dave
>
>> On Sep 20, 2022, at 1:18 PM, Tristan Van Berkom <tv...@apache.org> wrote:
>>
>> On 2022/09/20 16:31:02 Dave Fisher wrote:
>>> IMO Sander’s reply with a Direct to TLP Resolution counts as a request from BuildStream.
>>
>> +1
>>
>> Cheers,
>> -Tristan
>>
>>>
>>> BR,
>>> Dave
>>>
>>>> On Sep 20, 2022, at 7:46 AM, Daniel Gruno <hu...@apache.org> wrote:
>>>>
>>>> While I don't see a *ton* of communication on the BuildStream lists, I do see some (low/medium activity is just fine in my book), and I have not seen anything that would indicate that the project has any misapprehensions towards the apache way or our other legal/procedural frameworks. As such, I would be in favor of graduation provided the request comes from the BuildStream project. If that has already happened, and I missed it, I would appreciate a link to this request.
>>>>
>>>> With regards,
>>>> Daniel.
>>>>
>>>> On 2022/09/17 13:07:57 Sander Striker wrote:
>>>>> Hi,
>>>>>
>>>>> BuildStream has been in the process of migrating to the ASF as a Petri
>>>>> culture since
>>>>> early 2020. Of course the past few years have shown to be interesting, and
>>>>> have also
>>>>> impacted mentor availability. Despite this, the community managed to get
>>>>> the codebase
>>>>> relicensed, added a new committer, and is getting ready to get its 2.0
>>>>> release over the
>>>>> line, which would be the first release under the ASF banner.
>>>>>
>>>>> I'm sure we can find more i's to dot and more t's to cross, but I
>>>>> personally don't think that
>>>>> we need to hold up recognizing BuildStream as an ASF project. Petri PMC
>>>>> members,
>>>>> what are your thoughts on the matter?
>>>>>
>>>>> I've included a draft resolution below for your convenience and
>>>>> consideration.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Sander
>>>>> --
>>>>> Establish the Apache BuildStream Project
>>>>>
>>>>> WHEREAS, the Board of Directors deems it to be in the best interests of
>>>>> the Foundation and consistent with the Foundation's purpose to
>>>>> establish a Project Management Committee charged with the creation and
>>>>> maintenance of open-source software, for distribution at no charge to
>>>>> the public, related to efficiently and correctly developing, building
>>>>> and integrating software stacks.
>>>>>
>>>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>>>> (PMC), to be known as the "Apache BuildStream Project", be and hereby
>>>>> is established pursuant to Bylaws of the Foundation; and be it further
>>>>>
>>>>> RESOLVED, that the Apache BuildStream be and hereby is responsible for
>>>>> the creation and maintenance of software related to efficiently and
>>>>> correctly developing, building and integrating software stacks; and be
>>>>> it further
>>>>>
>>>>> RESOLVED, that the office of "Vice President, Apache BuildStream" be
>>>>> and hereby is created, the person holding such office to serve at the
>>>>> direction of the Board of Directors as the chair of the Apache
>>>>> BuildStream Project, and to have primary responsibility for management
>>>>> of the projects within the scope of responsibility of the Apache
>>>>> BuildStream Project; and be it further
>>>>>
>>>>> RESOLVED, that the persons listed immediately below be and hereby are
>>>>> appointed to serve as the initial members of the Apache BuildStream
>>>>> Project:
>>>>>
>>>>> * Tristan Van Berkom <tv...@apache.org>
>>>>> * Jürg Billeter <ju...@apache.org>
>>>>> * Abderrahim Kitouni <ak...@apache.org>
>>>>> * Benjamin Schubert <be...@apache.org>
>>>>> * Chandan Singh <ch...@apache.org>
>>>>> * Sander Striker <st...@apache.org>
>>>>>
>>>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tristan Van Berkom be
>>>>> appointed to the office of Vice President, Apache BuildStream, to serve
>>>>> in accordance with and subject to the direction of the Board of
>>>>> Directors and the Bylaws of the Foundation until death, resignation,
>>>>> retirement, removal or disqualification, or until a successor is
>>>>> appointed.
>>>>>
>>>>> On Fri, Sep 16, 2022 at 9:37 AM Sander Striker <s....@striker.nl> wrote:
>>>>>
>>>>>> Hi Dave,
>>>>>>
>>>>>> On 2, this was already done:
>>>>>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183.
>>>>>>
>>>>>> Is there anything else that would be prohibiting the submission of the
>>>>>> Direct to TLP Resolution?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Sander
>>>>>>
>>>>>> On Mon, Aug 8, 2022 at 9:28 PM Dave Fisher <wa...@apache.org> wrote:
>>>>>>
>>>>>>> Hi -
>>>>>>>
>>>>>>> BuildStream is close to ready.
>>>>>>>
>>>>>>> See https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05 and
>>>>>>> https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05
>>>>>>>
>>>>>>> I think that next steps are:
>>>>>>>
>>>>>>> (1) Prepare a Direct to TLP Resolution for the September board meeting.
>>>>>>> (2) Do a Podling Name Search so that the resolution will get a green
>>>>>>> checkbox.
>>>>>>> (3) Question? Does the website need to be compliant before becoming a
>>>>>>> TLP? (I think no, but want to be prepared if the board disagrees.)
>>>>>>> (4) Anything else?
>>>>>>>
>>>>>>> The Petri Board report is due on Friday and I want to include the results
>>>>>>> of this discussion in the report.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Dave
>>>>>>>
>>>>>>>> On Jul 21, 2022, at 12:33 PM, Dave Fisher <wa...@apache.org> wrote:
>>>>>>>>
>>>>>>>> Hey Petri Peeps,
>>>>>>>>
>>>>>>>> We need to discuss BuildStream’s status and how we will help bring this
>>>>>>> to a TLP establishing Board Resolution.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Dave
>>>>>>>>
>>>>>>>>> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
>>>>>>>>>
>>>>>>>>> BuildStream is nearly ready to become a TLP.
>>>>>>>>>
>>>>>>>>> They have cleared up all of the licensing issues in their codebase.
>>>>>>>>>
>>>>>>>>> Perhaps the only additional activity I would like to see is a
>>>>>>> discussion about rolling a Release following the Apache Release Policy on
>>>>>>> dev@buildstream.a.o
>>>>>>>>>
>>>>>>>>> Thoughts?
>>>>>>>>>
>>>>>>>>> All the best,
>>>>>>>>> Dave
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>
>>>
>
Re: [DISCUSS] Is BuildStream Ready?
Posted by Dave Fisher <wa...@apache.org>.
Hi Sander,
I say we should go for it in tomorrow’s Board Meeting. (I’m not sure if I can attend.)
Best,
Dave
> On Sep 20, 2022, at 1:18 PM, Tristan Van Berkom <tv...@apache.org> wrote:
>
> On 2022/09/20 16:31:02 Dave Fisher wrote:
>> IMO Sander’s reply with a Direct to TLP Resolution counts as a request from BuildStream.
>
> +1
>
> Cheers,
> -Tristan
>
>>
>> BR,
>> Dave
>>
>>> On Sep 20, 2022, at 7:46 AM, Daniel Gruno <hu...@apache.org> wrote:
>>>
>>> While I don't see a *ton* of communication on the BuildStream lists, I do see some (low/medium activity is just fine in my book), and I have not seen anything that would indicate that the project has any misapprehensions towards the apache way or our other legal/procedural frameworks. As such, I would be in favor of graduation provided the request comes from the BuildStream project. If that has already happened, and I missed it, I would appreciate a link to this request.
>>>
>>> With regards,
>>> Daniel.
>>>
>>> On 2022/09/17 13:07:57 Sander Striker wrote:
>>>> Hi,
>>>>
>>>> BuildStream has been in the process of migrating to the ASF as a Petri
>>>> culture since
>>>> early 2020. Of course the past few years have shown to be interesting, and
>>>> have also
>>>> impacted mentor availability. Despite this, the community managed to get
>>>> the codebase
>>>> relicensed, added a new committer, and is getting ready to get its 2.0
>>>> release over the
>>>> line, which would be the first release under the ASF banner.
>>>>
>>>> I'm sure we can find more i's to dot and more t's to cross, but I
>>>> personally don't think that
>>>> we need to hold up recognizing BuildStream as an ASF project. Petri PMC
>>>> members,
>>>> what are your thoughts on the matter?
>>>>
>>>> I've included a draft resolution below for your convenience and
>>>> consideration.
>>>>
>>>> Cheers,
>>>>
>>>> Sander
>>>> --
>>>> Establish the Apache BuildStream Project
>>>>
>>>> WHEREAS, the Board of Directors deems it to be in the best interests of
>>>> the Foundation and consistent with the Foundation's purpose to
>>>> establish a Project Management Committee charged with the creation and
>>>> maintenance of open-source software, for distribution at no charge to
>>>> the public, related to efficiently and correctly developing, building
>>>> and integrating software stacks.
>>>>
>>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>>> (PMC), to be known as the "Apache BuildStream Project", be and hereby
>>>> is established pursuant to Bylaws of the Foundation; and be it further
>>>>
>>>> RESOLVED, that the Apache BuildStream be and hereby is responsible for
>>>> the creation and maintenance of software related to efficiently and
>>>> correctly developing, building and integrating software stacks; and be
>>>> it further
>>>>
>>>> RESOLVED, that the office of "Vice President, Apache BuildStream" be
>>>> and hereby is created, the person holding such office to serve at the
>>>> direction of the Board of Directors as the chair of the Apache
>>>> BuildStream Project, and to have primary responsibility for management
>>>> of the projects within the scope of responsibility of the Apache
>>>> BuildStream Project; and be it further
>>>>
>>>> RESOLVED, that the persons listed immediately below be and hereby are
>>>> appointed to serve as the initial members of the Apache BuildStream
>>>> Project:
>>>>
>>>> * Tristan Van Berkom <tv...@apache.org>
>>>> * Jürg Billeter <ju...@apache.org>
>>>> * Abderrahim Kitouni <ak...@apache.org>
>>>> * Benjamin Schubert <be...@apache.org>
>>>> * Chandan Singh <ch...@apache.org>
>>>> * Sander Striker <st...@apache.org>
>>>>
>>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tristan Van Berkom be
>>>> appointed to the office of Vice President, Apache BuildStream, to serve
>>>> in accordance with and subject to the direction of the Board of
>>>> Directors and the Bylaws of the Foundation until death, resignation,
>>>> retirement, removal or disqualification, or until a successor is
>>>> appointed.
>>>>
>>>> On Fri, Sep 16, 2022 at 9:37 AM Sander Striker <s....@striker.nl> wrote:
>>>>
>>>>> Hi Dave,
>>>>>
>>>>> On 2, this was already done:
>>>>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183.
>>>>>
>>>>> Is there anything else that would be prohibiting the submission of the
>>>>> Direct to TLP Resolution?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Sander
>>>>>
>>>>> On Mon, Aug 8, 2022 at 9:28 PM Dave Fisher <wa...@apache.org> wrote:
>>>>>
>>>>>> Hi -
>>>>>>
>>>>>> BuildStream is close to ready.
>>>>>>
>>>>>> See https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05 and
>>>>>> https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05
>>>>>>
>>>>>> I think that next steps are:
>>>>>>
>>>>>> (1) Prepare a Direct to TLP Resolution for the September board meeting.
>>>>>> (2) Do a Podling Name Search so that the resolution will get a green
>>>>>> checkbox.
>>>>>> (3) Question? Does the website need to be compliant before becoming a
>>>>>> TLP? (I think no, but want to be prepared if the board disagrees.)
>>>>>> (4) Anything else?
>>>>>>
>>>>>> The Petri Board report is due on Friday and I want to include the results
>>>>>> of this discussion in the report.
>>>>>>
>>>>>> Thanks,
>>>>>> Dave
>>>>>>
>>>>>>> On Jul 21, 2022, at 12:33 PM, Dave Fisher <wa...@apache.org> wrote:
>>>>>>>
>>>>>>> Hey Petri Peeps,
>>>>>>>
>>>>>>> We need to discuss BuildStream’s status and how we will help bring this
>>>>>> to a TLP establishing Board Resolution.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Dave
>>>>>>>
>>>>>>>> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
>>>>>>>>
>>>>>>>> BuildStream is nearly ready to become a TLP.
>>>>>>>>
>>>>>>>> They have cleared up all of the licensing issues in their codebase.
>>>>>>>>
>>>>>>>> Perhaps the only additional activity I would like to see is a
>>>>>> discussion about rolling a Release following the Apache Release Policy on
>>>>>> dev@buildstream.a.o
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>>
>>>>>>>> All the best,
>>>>>>>> Dave
>>>>>>>
>>>>>>
>>>>>>
>>>>
>>
>>
Re: [DISCUSS] Is BuildStream Ready?
Posted by Tristan Van Berkom <tv...@apache.org>.
On 2022/09/20 16:31:02 Dave Fisher wrote:
> IMO Sander’s reply with a Direct to TLP Resolution counts as a request from BuildStream.
+1
Cheers,
-Tristan
>
> BR,
> Dave
>
> > On Sep 20, 2022, at 7:46 AM, Daniel Gruno <hu...@apache.org> wrote:
> >
> > While I don't see a *ton* of communication on the BuildStream lists, I do see some (low/medium activity is just fine in my book), and I have not seen anything that would indicate that the project has any misapprehensions towards the apache way or our other legal/procedural frameworks. As such, I would be in favor of graduation provided the request comes from the BuildStream project. If that has already happened, and I missed it, I would appreciate a link to this request.
> >
> > With regards,
> > Daniel.
> >
> > On 2022/09/17 13:07:57 Sander Striker wrote:
> >> Hi,
> >>
> >> BuildStream has been in the process of migrating to the ASF as a Petri
> >> culture since
> >> early 2020. Of course the past few years have shown to be interesting, and
> >> have also
> >> impacted mentor availability. Despite this, the community managed to get
> >> the codebase
> >> relicensed, added a new committer, and is getting ready to get its 2.0
> >> release over the
> >> line, which would be the first release under the ASF banner.
> >>
> >> I'm sure we can find more i's to dot and more t's to cross, but I
> >> personally don't think that
> >> we need to hold up recognizing BuildStream as an ASF project. Petri PMC
> >> members,
> >> what are your thoughts on the matter?
> >>
> >> I've included a draft resolution below for your convenience and
> >> consideration.
> >>
> >> Cheers,
> >>
> >> Sander
> >> --
> >> Establish the Apache BuildStream Project
> >>
> >> WHEREAS, the Board of Directors deems it to be in the best interests of
> >> the Foundation and consistent with the Foundation's purpose to
> >> establish a Project Management Committee charged with the creation and
> >> maintenance of open-source software, for distribution at no charge to
> >> the public, related to efficiently and correctly developing, building
> >> and integrating software stacks.
> >>
> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> (PMC), to be known as the "Apache BuildStream Project", be and hereby
> >> is established pursuant to Bylaws of the Foundation; and be it further
> >>
> >> RESOLVED, that the Apache BuildStream be and hereby is responsible for
> >> the creation and maintenance of software related to efficiently and
> >> correctly developing, building and integrating software stacks; and be
> >> it further
> >>
> >> RESOLVED, that the office of "Vice President, Apache BuildStream" be
> >> and hereby is created, the person holding such office to serve at the
> >> direction of the Board of Directors as the chair of the Apache
> >> BuildStream Project, and to have primary responsibility for management
> >> of the projects within the scope of responsibility of the Apache
> >> BuildStream Project; and be it further
> >>
> >> RESOLVED, that the persons listed immediately below be and hereby are
> >> appointed to serve as the initial members of the Apache BuildStream
> >> Project:
> >>
> >> * Tristan Van Berkom <tv...@apache.org>
> >> * Jürg Billeter <ju...@apache.org>
> >> * Abderrahim Kitouni <ak...@apache.org>
> >> * Benjamin Schubert <be...@apache.org>
> >> * Chandan Singh <ch...@apache.org>
> >> * Sander Striker <st...@apache.org>
> >>
> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tristan Van Berkom be
> >> appointed to the office of Vice President, Apache BuildStream, to serve
> >> in accordance with and subject to the direction of the Board of
> >> Directors and the Bylaws of the Foundation until death, resignation,
> >> retirement, removal or disqualification, or until a successor is
> >> appointed.
> >>
> >> On Fri, Sep 16, 2022 at 9:37 AM Sander Striker <s....@striker.nl> wrote:
> >>
> >>> Hi Dave,
> >>>
> >>> On 2, this was already done:
> >>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183.
> >>>
> >>> Is there anything else that would be prohibiting the submission of the
> >>> Direct to TLP Resolution?
> >>>
> >>> Cheers,
> >>>
> >>> Sander
> >>>
> >>> On Mon, Aug 8, 2022 at 9:28 PM Dave Fisher <wa...@apache.org> wrote:
> >>>
> >>>> Hi -
> >>>>
> >>>> BuildStream is close to ready.
> >>>>
> >>>> See https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05 and
> >>>> https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05
> >>>>
> >>>> I think that next steps are:
> >>>>
> >>>> (1) Prepare a Direct to TLP Resolution for the September board meeting.
> >>>> (2) Do a Podling Name Search so that the resolution will get a green
> >>>> checkbox.
> >>>> (3) Question? Does the website need to be compliant before becoming a
> >>>> TLP? (I think no, but want to be prepared if the board disagrees.)
> >>>> (4) Anything else?
> >>>>
> >>>> The Petri Board report is due on Friday and I want to include the results
> >>>> of this discussion in the report.
> >>>>
> >>>> Thanks,
> >>>> Dave
> >>>>
> >>>>> On Jul 21, 2022, at 12:33 PM, Dave Fisher <wa...@apache.org> wrote:
> >>>>>
> >>>>> Hey Petri Peeps,
> >>>>>
> >>>>> We need to discuss BuildStream’s status and how we will help bring this
> >>>> to a TLP establishing Board Resolution.
> >>>>>
> >>>>> Thanks,
> >>>>> Dave
> >>>>>
> >>>>>> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
> >>>>>>
> >>>>>> BuildStream is nearly ready to become a TLP.
> >>>>>>
> >>>>>> They have cleared up all of the licensing issues in their codebase.
> >>>>>>
> >>>>>> Perhaps the only additional activity I would like to see is a
> >>>> discussion about rolling a Release following the Apache Release Policy on
> >>>> dev@buildstream.a.o
> >>>>>>
> >>>>>> Thoughts?
> >>>>>>
> >>>>>> All the best,
> >>>>>> Dave
> >>>>>
> >>>>
> >>>>
> >>
>
>
Re: [DISCUSS] Is BuildStream Ready?
Posted by Dave Fisher <wa...@apache.org>.
IMO Sander’s reply with a Direct to TLP Resolution counts as a request from BuildStream.
BR,
Dave
> On Sep 20, 2022, at 7:46 AM, Daniel Gruno <hu...@apache.org> wrote:
>
> While I don't see a *ton* of communication on the BuildStream lists, I do see some (low/medium activity is just fine in my book), and I have not seen anything that would indicate that the project has any misapprehensions towards the apache way or our other legal/procedural frameworks. As such, I would be in favor of graduation provided the request comes from the BuildStream project. If that has already happened, and I missed it, I would appreciate a link to this request.
>
> With regards,
> Daniel.
>
> On 2022/09/17 13:07:57 Sander Striker wrote:
>> Hi,
>>
>> BuildStream has been in the process of migrating to the ASF as a Petri
>> culture since
>> early 2020. Of course the past few years have shown to be interesting, and
>> have also
>> impacted mentor availability. Despite this, the community managed to get
>> the codebase
>> relicensed, added a new committer, and is getting ready to get its 2.0
>> release over the
>> line, which would be the first release under the ASF banner.
>>
>> I'm sure we can find more i's to dot and more t's to cross, but I
>> personally don't think that
>> we need to hold up recognizing BuildStream as an ASF project. Petri PMC
>> members,
>> what are your thoughts on the matter?
>>
>> I've included a draft resolution below for your convenience and
>> consideration.
>>
>> Cheers,
>>
>> Sander
>> --
>> Establish the Apache BuildStream Project
>>
>> WHEREAS, the Board of Directors deems it to be in the best interests of
>> the Foundation and consistent with the Foundation's purpose to
>> establish a Project Management Committee charged with the creation and
>> maintenance of open-source software, for distribution at no charge to
>> the public, related to efficiently and correctly developing, building
>> and integrating software stacks.
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache BuildStream Project", be and hereby
>> is established pursuant to Bylaws of the Foundation; and be it further
>>
>> RESOLVED, that the Apache BuildStream be and hereby is responsible for
>> the creation and maintenance of software related to efficiently and
>> correctly developing, building and integrating software stacks; and be
>> it further
>>
>> RESOLVED, that the office of "Vice President, Apache BuildStream" be
>> and hereby is created, the person holding such office to serve at the
>> direction of the Board of Directors as the chair of the Apache
>> BuildStream Project, and to have primary responsibility for management
>> of the projects within the scope of responsibility of the Apache
>> BuildStream Project; and be it further
>>
>> RESOLVED, that the persons listed immediately below be and hereby are
>> appointed to serve as the initial members of the Apache BuildStream
>> Project:
>>
>> * Tristan Van Berkom <tv...@apache.org>
>> * Jürg Billeter <ju...@apache.org>
>> * Abderrahim Kitouni <ak...@apache.org>
>> * Benjamin Schubert <be...@apache.org>
>> * Chandan Singh <ch...@apache.org>
>> * Sander Striker <st...@apache.org>
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tristan Van Berkom be
>> appointed to the office of Vice President, Apache BuildStream, to serve
>> in accordance with and subject to the direction of the Board of
>> Directors and the Bylaws of the Foundation until death, resignation,
>> retirement, removal or disqualification, or until a successor is
>> appointed.
>>
>> On Fri, Sep 16, 2022 at 9:37 AM Sander Striker <s....@striker.nl> wrote:
>>
>>> Hi Dave,
>>>
>>> On 2, this was already done:
>>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183.
>>>
>>> Is there anything else that would be prohibiting the submission of the
>>> Direct to TLP Resolution?
>>>
>>> Cheers,
>>>
>>> Sander
>>>
>>> On Mon, Aug 8, 2022 at 9:28 PM Dave Fisher <wa...@apache.org> wrote:
>>>
>>>> Hi -
>>>>
>>>> BuildStream is close to ready.
>>>>
>>>> See https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05 and
>>>> https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05
>>>>
>>>> I think that next steps are:
>>>>
>>>> (1) Prepare a Direct to TLP Resolution for the September board meeting.
>>>> (2) Do a Podling Name Search so that the resolution will get a green
>>>> checkbox.
>>>> (3) Question? Does the website need to be compliant before becoming a
>>>> TLP? (I think no, but want to be prepared if the board disagrees.)
>>>> (4) Anything else?
>>>>
>>>> The Petri Board report is due on Friday and I want to include the results
>>>> of this discussion in the report.
>>>>
>>>> Thanks,
>>>> Dave
>>>>
>>>>> On Jul 21, 2022, at 12:33 PM, Dave Fisher <wa...@apache.org> wrote:
>>>>>
>>>>> Hey Petri Peeps,
>>>>>
>>>>> We need to discuss BuildStream’s status and how we will help bring this
>>>> to a TLP establishing Board Resolution.
>>>>>
>>>>> Thanks,
>>>>> Dave
>>>>>
>>>>>> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
>>>>>>
>>>>>> BuildStream is nearly ready to become a TLP.
>>>>>>
>>>>>> They have cleared up all of the licensing issues in their codebase.
>>>>>>
>>>>>> Perhaps the only additional activity I would like to see is a
>>>> discussion about rolling a Release following the Apache Release Policy on
>>>> dev@buildstream.a.o
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> All the best,
>>>>>> Dave
>>>>>
>>>>
>>>>
>>
Re: [DISCUSS] Is BuildStream Ready?
Posted by Daniel Gruno <hu...@apache.org>.
While I don't see a *ton* of communication on the BuildStream lists, I do see some (low/medium activity is just fine in my book), and I have not seen anything that would indicate that the project has any misapprehensions towards the apache way or our other legal/procedural frameworks. As such, I would be in favor of graduation provided the request comes from the BuildStream project. If that has already happened, and I missed it, I would appreciate a link to this request.
With regards,
Daniel.
On 2022/09/17 13:07:57 Sander Striker wrote:
> Hi,
>
> BuildStream has been in the process of migrating to the ASF as a Petri
> culture since
> early 2020. Of course the past few years have shown to be interesting, and
> have also
> impacted mentor availability. Despite this, the community managed to get
> the codebase
> relicensed, added a new committer, and is getting ready to get its 2.0
> release over the
> line, which would be the first release under the ASF banner.
>
> I'm sure we can find more i's to dot and more t's to cross, but I
> personally don't think that
> we need to hold up recognizing BuildStream as an ASF project. Petri PMC
> members,
> what are your thoughts on the matter?
>
> I've included a draft resolution below for your convenience and
> consideration.
>
> Cheers,
>
> Sander
> --
> Establish the Apache BuildStream Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to
> establish a Project Management Committee charged with the creation and
> maintenance of open-source software, for distribution at no charge to
> the public, related to efficiently and correctly developing, building
> and integrating software stacks.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache BuildStream Project", be and hereby
> is established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache BuildStream be and hereby is responsible for
> the creation and maintenance of software related to efficiently and
> correctly developing, building and integrating software stacks; and be
> it further
>
> RESOLVED, that the office of "Vice President, Apache BuildStream" be
> and hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache
> BuildStream Project, and to have primary responsibility for management
> of the projects within the scope of responsibility of the Apache
> BuildStream Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache BuildStream
> Project:
>
> * Tristan Van Berkom <tv...@apache.org>
> * Jürg Billeter <ju...@apache.org>
> * Abderrahim Kitouni <ak...@apache.org>
> * Benjamin Schubert <be...@apache.org>
> * Chandan Singh <ch...@apache.org>
> * Sander Striker <st...@apache.org>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tristan Van Berkom be
> appointed to the office of Vice President, Apache BuildStream, to serve
> in accordance with and subject to the direction of the Board of
> Directors and the Bylaws of the Foundation until death, resignation,
> retirement, removal or disqualification, or until a successor is
> appointed.
>
> On Fri, Sep 16, 2022 at 9:37 AM Sander Striker <s....@striker.nl> wrote:
>
> > Hi Dave,
> >
> > On 2, this was already done:
> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183.
> >
> > Is there anything else that would be prohibiting the submission of the
> > Direct to TLP Resolution?
> >
> > Cheers,
> >
> > Sander
> >
> > On Mon, Aug 8, 2022 at 9:28 PM Dave Fisher <wa...@apache.org> wrote:
> >
> >> Hi -
> >>
> >> BuildStream is close to ready.
> >>
> >> See https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05 and
> >> https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05
> >>
> >> I think that next steps are:
> >>
> >> (1) Prepare a Direct to TLP Resolution for the September board meeting.
> >> (2) Do a Podling Name Search so that the resolution will get a green
> >> checkbox.
> >> (3) Question? Does the website need to be compliant before becoming a
> >> TLP? (I think no, but want to be prepared if the board disagrees.)
> >> (4) Anything else?
> >>
> >> The Petri Board report is due on Friday and I want to include the results
> >> of this discussion in the report.
> >>
> >> Thanks,
> >> Dave
> >>
> >> > On Jul 21, 2022, at 12:33 PM, Dave Fisher <wa...@apache.org> wrote:
> >> >
> >> > Hey Petri Peeps,
> >> >
> >> > We need to discuss BuildStream’s status and how we will help bring this
> >> to a TLP establishing Board Resolution.
> >> >
> >> > Thanks,
> >> > Dave
> >> >
> >> >> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
> >> >>
> >> >> BuildStream is nearly ready to become a TLP.
> >> >>
> >> >> They have cleared up all of the licensing issues in their codebase.
> >> >>
> >> >> Perhaps the only additional activity I would like to see is a
> >> discussion about rolling a Release following the Apache Release Policy on
> >> dev@buildstream.a.o
> >> >>
> >> >> Thoughts?
> >> >>
> >> >> All the best,
> >> >> Dave
> >> >
> >>
> >>
>
Re: [DISCUSS] Is BuildStream Ready?
Posted by Sander Striker <s....@striker.nl>.
Hi,
BuildStream has been in the process of migrating to the ASF as a Petri
culture since
early 2020. Of course the past few years have shown to be interesting, and
have also
impacted mentor availability. Despite this, the community managed to get
the codebase
relicensed, added a new committer, and is getting ready to get its 2.0
release over the
line, which would be the first release under the ASF banner.
I'm sure we can find more i's to dot and more t's to cross, but I
personally don't think that
we need to hold up recognizing BuildStream as an ASF project. Petri PMC
members,
what are your thoughts on the matter?
I've included a draft resolution below for your convenience and
consideration.
Cheers,
Sander
--
Establish the Apache BuildStream Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to efficiently and correctly developing, building
and integrating software stacks.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache BuildStream Project", be and hereby
is established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache BuildStream be and hereby is responsible for
the creation and maintenance of software related to efficiently and
correctly developing, building and integrating software stacks; and be
it further
RESOLVED, that the office of "Vice President, Apache BuildStream" be
and hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache
BuildStream Project, and to have primary responsibility for management
of the projects within the scope of responsibility of the Apache
BuildStream Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache BuildStream
Project:
* Tristan Van Berkom <tv...@apache.org>
* Jürg Billeter <ju...@apache.org>
* Abderrahim Kitouni <ak...@apache.org>
* Benjamin Schubert <be...@apache.org>
* Chandan Singh <ch...@apache.org>
* Sander Striker <st...@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tristan Van Berkom be
appointed to the office of Vice President, Apache BuildStream, to serve
in accordance with and subject to the direction of the Board of
Directors and the Bylaws of the Foundation until death, resignation,
retirement, removal or disqualification, or until a successor is
appointed.
On Fri, Sep 16, 2022 at 9:37 AM Sander Striker <s....@striker.nl> wrote:
> Hi Dave,
>
> On 2, this was already done:
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183.
>
> Is there anything else that would be prohibiting the submission of the
> Direct to TLP Resolution?
>
> Cheers,
>
> Sander
>
> On Mon, Aug 8, 2022 at 9:28 PM Dave Fisher <wa...@apache.org> wrote:
>
>> Hi -
>>
>> BuildStream is close to ready.
>>
>> See https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05 and
>> https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05
>>
>> I think that next steps are:
>>
>> (1) Prepare a Direct to TLP Resolution for the September board meeting.
>> (2) Do a Podling Name Search so that the resolution will get a green
>> checkbox.
>> (3) Question? Does the website need to be compliant before becoming a
>> TLP? (I think no, but want to be prepared if the board disagrees.)
>> (4) Anything else?
>>
>> The Petri Board report is due on Friday and I want to include the results
>> of this discussion in the report.
>>
>> Thanks,
>> Dave
>>
>> > On Jul 21, 2022, at 12:33 PM, Dave Fisher <wa...@apache.org> wrote:
>> >
>> > Hey Petri Peeps,
>> >
>> > We need to discuss BuildStream’s status and how we will help bring this
>> to a TLP establishing Board Resolution.
>> >
>> > Thanks,
>> > Dave
>> >
>> >> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
>> >>
>> >> BuildStream is nearly ready to become a TLP.
>> >>
>> >> They have cleared up all of the licensing issues in their codebase.
>> >>
>> >> Perhaps the only additional activity I would like to see is a
>> discussion about rolling a Release following the Apache Release Policy on
>> dev@buildstream.a.o
>> >>
>> >> Thoughts?
>> >>
>> >> All the best,
>> >> Dave
>> >
>>
>>
Re: [DISCUSS] Is BuildStream Ready?
Posted by Sander Striker <s....@striker.nl>.
Hi Dave,
On 2, this was already done:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-183.
Is there anything else that would be prohibiting the submission of the
Direct to TLP Resolution?
Cheers,
Sander
On Mon, Aug 8, 2022 at 9:28 PM Dave Fisher <wa...@apache.org> wrote:
> Hi -
>
> BuildStream is close to ready.
>
> See https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05 and
> https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05
>
> I think that next steps are:
>
> (1) Prepare a Direct to TLP Resolution for the September board meeting.
> (2) Do a Podling Name Search so that the resolution will get a green
> checkbox.
> (3) Question? Does the website need to be compliant before becoming a TLP?
> (I think no, but want to be prepared if the board disagrees.)
> (4) Anything else?
>
> The Petri Board report is due on Friday and I want to include the results
> of this discussion in the report.
>
> Thanks,
> Dave
>
> > On Jul 21, 2022, at 12:33 PM, Dave Fisher <wa...@apache.org> wrote:
> >
> > Hey Petri Peeps,
> >
> > We need to discuss BuildStream’s status and how we will help bring this
> to a TLP establishing Board Resolution.
> >
> > Thanks,
> > Dave
> >
> >> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
> >>
> >> BuildStream is nearly ready to become a TLP.
> >>
> >> They have cleared up all of the licensing issues in their codebase.
> >>
> >> Perhaps the only additional activity I would like to see is a
> discussion about rolling a Release following the Apache Release Policy on
> dev@buildstream.a.o
> >>
> >> Thoughts?
> >>
> >> All the best,
> >> Dave
> >
>
>
Re: [DISCUSS] Is BuildStream Ready?
Posted by Dave Fisher <wa...@apache.org>.
Hi -
BuildStream is close to ready.
See https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05 and https://lists.apache.org/thread/8olj5v8gqt2p49rjp01lwms26971bj05
I think that next steps are:
(1) Prepare a Direct to TLP Resolution for the September board meeting.
(2) Do a Podling Name Search so that the resolution will get a green checkbox.
(3) Question? Does the website need to be compliant before becoming a TLP? (I think no, but want to be prepared if the board disagrees.)
(4) Anything else?
The Petri Board report is due on Friday and I want to include the results of this discussion in the report.
Thanks,
Dave
> On Jul 21, 2022, at 12:33 PM, Dave Fisher <wa...@apache.org> wrote:
>
> Hey Petri Peeps,
>
> We need to discuss BuildStream’s status and how we will help bring this to a TLP establishing Board Resolution.
>
> Thanks,
> Dave
>
>> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
>>
>> BuildStream is nearly ready to become a TLP.
>>
>> They have cleared up all of the licensing issues in their codebase.
>>
>> Perhaps the only additional activity I would like to see is a discussion about rolling a Release following the Apache Release Policy on dev@buildstream.a.o
>>
>> Thoughts?
>>
>> All the best,
>> Dave
>
Re: [DISCUSS] Is BuildStream Ready?
Posted by Dave Fisher <wa...@apache.org>.
Hey Petri Peeps,
We need to discuss BuildStream’s status and how we will help bring this to a TLP establishing Board Resolution.
Thanks,
Dave
> On Mar 9, 2022, at 8:01 AM, Dave Fisher <wa...@apache.org> wrote:
>
> BuildStream is nearly ready to become a TLP.
>
> They have cleared up all of the licensing issues in their codebase.
>
> Perhaps the only additional activity I would like to see is a discussion about rolling a Release following the Apache Release Policy on dev@buildstream.a.o
>
> Thoughts?
>
> All the best,
> Dave