From alanclark at openstack.org Tue Apr 2 13:43:13 2019 From: alanclark at openstack.org (Alan Clark) Date: Tue, 2 Apr 2019 07:43:13 -0600 Subject: [Foundation Board] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation Message-ID: <00a501d4e95a$05623e40$1026bac0$@openstack.org> As the OpenStack Foundation embraces new areas of strategic focus and as the associated Open Infrastructure projects mature, the OpenStack board desires to do its part in helping the projects thrive and grow. A key step in project advancement is the project confirmation by the Board. Confirmation will enable the Foundation to apply additional Foundation resources towards that project. In support of this process, the board at its last meeting, approved the OSF Project Confirmation Guidelines[1]. As the Guidelines point out, many factors go into the board's decisions. To ensure that the board has the mechanisms needed to be as sensitive as possible to the needs and feelings for those invested in the projects, the board will further discuss a motion to amend bylaws section 4.16 as follows: (changed text in italics). 4.16 Open Meetings and Records. Except as necessary to protect attorney-client privilege, sensitive personnel information, discuss the candidacy of potential Gold Member and Platinum Members, and discuss the review and approval of Open Infrastructure Projects, the Board of Directors shall: (i) permit observation of its meetings by Members via remote teleconference or other electronic means, and (ii) publish the Board of Directors minutes and make available to any Member on request other information and records of the Foundation as required by Delaware Corporate Law. If, during confirmation discussions, a project lead or Director feels that there is sensitive information that needs to be protected this amendment provides a mechanism for such discussion. Thanks, Alan Clark [1] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmation Guidelines -------------- next part -------------- An HTML attachment was scrubbed... URL: From Arkady.Kanevsky at dell.com Tue Apr 2 13:49:33 2019 From: Arkady.Kanevsky at dell.com (Arkady.Kanevsky at dell.com) Date: Tue, 2 Apr 2019 13:49:33 +0000 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: <00a501d4e95a$05623e40$1026bac0$@openstack.org> References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> Message-ID: <423268e6d25e483b85c9dc9977b67672@AUSX13MPS308.AMER.DELL.COM> Sounds like a good change. Alan, Do you propose we vote on it at Denver? Thanks, Arkady From: Alan Clark Sent: Tuesday, April 2, 2019 8:43 AM To: foundation at lists.openstack.org; foundation-board at lists.openstack.org Subject: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation [EXTERNAL EMAIL] As the OpenStack Foundation embraces new areas of strategic focus and as the associated Open Infrastructure projects mature, the OpenStack board desires to do its part in helping the projects thrive and grow. A key step in project advancement is the project confirmation by the Board. Confirmation will enable the Foundation to apply additional Foundation resources towards that project. In support of this process, the board at its last meeting, approved the OSF Project Confirmation Guidelines[1]. As the Guidelines point out, many factors go into the board's decisions. To ensure that the board has the mechanisms needed to be as sensitive as possible to the needs and feelings for those invested in the projects, the board will further discuss a motion to amend bylaws section 4.16 as follows: (changed text in italics). 4.16 Open Meetings and Records. Except as necessary to protect attorney-client privilege, sensitive personnel information, discuss the candidacy of potential Gold Member and Platinum Members, and discuss the review and approval of Open Infrastructure Projects, the Board of Directors shall: (i) permit observation of its meetings by Members via remote teleconference or other electronic means, and (ii) publish the Board of Directors minutes and make available to any Member on request other information and records of the Foundation as required by Delaware Corporate Law. If, during confirmation discussions, a project lead or Director feels that there is sensitive information that needs to be protected this amendment provides a mechanism for such discussion. Thanks, Alan Clark [1] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines -------------- next part -------------- An HTML attachment was scrubbed... URL: From alanclark at openstack.org Tue Apr 2 23:11:25 2019 From: alanclark at openstack.org (Alan Clark) Date: Tue, 2 Apr 2019 17:11:25 -0600 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: <423268e6d25e483b85c9dc9977b67672@AUSX13MPS308.AMER.DELL.COM> References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> <423268e6d25e483b85c9dc9977b67672@AUSX13MPS308.AMER.DELL.COM> Message-ID: <009201d4e9a9$658b9ba0$30a2d2e0$@openstack.org> The action from the last board meeting was for the motion to be made at next week's meeting. Thanks, AlanClark From: Arkady.Kanevsky at dell.com [mailto:Arkady.Kanevsky at dell.com] Sent: Tuesday, April 02, 2019 7:50 AM To: AlanClark at openstack.org; foundation at lists.openstack.org; foundation-board at lists.openstack.org Subject: Re: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation Sounds like a good change. Alan, Do you propose we vote on it at Denver? Thanks, Arkady From: Alan Clark > Sent: Tuesday, April 2, 2019 8:43 AM To: foundation at lists.openstack.org ; foundation-board at lists.openstack.org Subject: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation [EXTERNAL EMAIL] As the OpenStack Foundation embraces new areas of strategic focus and as the associated Open Infrastructure projects mature, the OpenStack board desires to do its part in helping the projects thrive and grow. A key step in project advancement is the project confirmation by the Board. Confirmation will enable the Foundation to apply additional Foundation resources towards that project. In support of this process, the board at its last meeting, approved the OSF Project Confirmation Guidelines[1]. As the Guidelines point out, many factors go into the board's decisions. To ensure that the board has the mechanisms needed to be as sensitive as possible to the needs and feelings for those invested in the projects, the board will further discuss a motion to amend bylaws section 4.16 as follows: (changed text in italics). 4.16 Open Meetings and Records. Except as necessary to protect attorney-client privilege, sensitive personnel information, discuss the candidacy of potential Gold Member and Platinum Members, and discuss the review and approval of Open Infrastructure Projects, the Board of Directors shall: (i) permit observation of its meetings by Members via remote teleconference or other electronic means, and (ii) publish the Board of Directors minutes and make available to any Member on request other information and records of the Foundation as required by Delaware Corporate Law. If, during confirmation discussions, a project lead or Director feels that there is sensitive information that needs to be protected this amendment provides a mechanism for such discussion. Thanks, Alan Clark [1] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmation Guidelines -------------- next part -------------- An HTML attachment was scrubbed... URL: From Arkady.Kanevsky at dell.com Tue Apr 2 23:15:11 2019 From: Arkady.Kanevsky at dell.com (Arkady.Kanevsky at dell.com) Date: Tue, 2 Apr 2019 23:15:11 +0000 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: <009201d4e9a9$658b9ba0$30a2d2e0$@openstack.org> References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> <423268e6d25e483b85c9dc9977b67672@AUSX13MPS308.AMER.DELL.COM> <009201d4e9a9$658b9ba0$30a2d2e0$@openstack.org> Message-ID: <07541ac9b5b847d381c6947a41906ffb@AUSX13MPS308.AMER.DELL.COM> Alan, I feel this too rushed. Any Bylaw changes typically run by legal in companies before the vote. Do not see how we can achieve that in 1 week. Thanks, Arkady From: Alan Clark Sent: Tuesday, April 2, 2019 6:11 PM To: Kanevsky, Arkady; foundation at lists.openstack.org; foundation-board at lists.openstack.org Subject: RE: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation [EXTERNAL EMAIL] The action from the last board meeting was for the motion to be made at next week's meeting. Thanks, AlanClark From: Arkady.Kanevsky at dell.com [mailto:Arkady.Kanevsky at dell.com] Sent: Tuesday, April 02, 2019 7:50 AM To: AlanClark at openstack.org; foundation at lists.openstack.org; foundation-board at lists.openstack.org Subject: Re: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation Sounds like a good change. Alan, Do you propose we vote on it at Denver? Thanks, Arkady From: Alan Clark > Sent: Tuesday, April 2, 2019 8:43 AM To: foundation at lists.openstack.org; foundation-board at lists.openstack.org Subject: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation [EXTERNAL EMAIL] As the OpenStack Foundation embraces new areas of strategic focus and as the associated Open Infrastructure projects mature, the OpenStack board desires to do its part in helping the projects thrive and grow. A key step in project advancement is the project confirmation by the Board. Confirmation will enable the Foundation to apply additional Foundation resources towards that project. In support of this process, the board at its last meeting, approved the OSF Project Confirmation Guidelines[1]. As the Guidelines point out, many factors go into the board's decisions. To ensure that the board has the mechanisms needed to be as sensitive as possible to the needs and feelings for those invested in the projects, the board will further discuss a motion to amend bylaws section 4.16 as follows: (changed text in italics). 4.16 Open Meetings and Records. Except as necessary to protect attorney-client privilege, sensitive personnel information, discuss the candidacy of potential Gold Member and Platinum Members, and discuss the review and approval of Open Infrastructure Projects, the Board of Directors shall: (i) permit observation of its meetings by Members via remote teleconference or other electronic means, and (ii) publish the Board of Directors minutes and make available to any Member on request other information and records of the Foundation as required by Delaware Corporate Law. If, during confirmation discussions, a project lead or Director feels that there is sensitive information that needs to be protected this amendment provides a mechanism for such discussion. Thanks, Alan Clark [1] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines -------------- next part -------------- An HTML attachment was scrubbed... URL: From alanclark at openstack.org Tue Apr 2 23:23:41 2019 From: alanclark at openstack.org (Alan Clark) Date: Tue, 2 Apr 2019 17:23:41 -0600 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: <07541ac9b5b847d381c6947a41906ffb@AUSX13MPS308.AMER.DELL.COM> References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> <423268e6d25e483b85c9dc9977b67672@AUSX13MPS308.AMER.DELL.COM> <009201d4e9a9$658b9ba0$30a2d2e0$@openstack.org> <07541ac9b5b847d381c6947a41906ffb@AUSX13MPS308.AMER.DELL.COM> Message-ID: <00bd01d4e9ab$1c1a6bc0$544f4340$@openstack.org> Sure. This isn't an item that needs to be rushed. From: Arkady.Kanevsky at dell.com [mailto:Arkady.Kanevsky at dell.com] Sent: Tuesday, April 02, 2019 5:15 PM To: AlanClark at openstack.org; foundation at lists.openstack.org; foundation-board at lists.openstack.org Subject: RE: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation Alan, I feel this too rushed. Any Bylaw changes typically run by legal in companies before the vote. Do not see how we can achieve that in 1 week. Thanks, Arkady From: Alan Clark > Sent: Tuesday, April 2, 2019 6:11 PM To: Kanevsky, Arkady; foundation at lists.openstack.org ; foundation-board at lists.openstack.org Subject: RE: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation [EXTERNAL EMAIL] The action from the last board meeting was for the motion to be made at next week's meeting. Thanks, AlanClark From: Arkady.Kanevsky at dell.com [mailto:Arkady.Kanevsky at dell.com] Sent: Tuesday, April 02, 2019 7:50 AM To: AlanClark at openstack.org ; foundation at lists.openstack.org ; foundation-board at lists.openstack.org Subject: Re: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation Sounds like a good change. Alan, Do you propose we vote on it at Denver? Thanks, Arkady From: Alan Clark > Sent: Tuesday, April 2, 2019 8:43 AM To: foundation at lists.openstack.org ; foundation-board at lists.openstack.org Subject: [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation [EXTERNAL EMAIL] As the OpenStack Foundation embraces new areas of strategic focus and as the associated Open Infrastructure projects mature, the OpenStack board desires to do its part in helping the projects thrive and grow. A key step in project advancement is the project confirmation by the Board. Confirmation will enable the Foundation to apply additional Foundation resources towards that project. In support of this process, the board at its last meeting, approved the OSF Project Confirmation Guidelines[1]. As the Guidelines point out, many factors go into the board's decisions. To ensure that the board has the mechanisms needed to be as sensitive as possible to the needs and feelings for those invested in the projects, the board will further discuss a motion to amend bylaws section 4.16 as follows: (changed text in italics). 4.16 Open Meetings and Records. Except as necessary to protect attorney-client privilege, sensitive personnel information, discuss the candidacy of potential Gold Member and Platinum Members, and discuss the review and approval of Open Infrastructure Projects, the Board of Directors shall: (i) permit observation of its meetings by Members via remote teleconference or other electronic means, and (ii) publish the Board of Directors minutes and make available to any Member on request other information and records of the Foundation as required by Delaware Corporate Law. If, during confirmation discussions, a project lead or Director feels that there is sensitive information that needs to be protected this amendment provides a mechanism for such discussion. Thanks, Alan Clark [1] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmation Guidelines -------------- next part -------------- An HTML attachment was scrubbed... URL: From alanclark at openstack.org Tue Apr 2 23:46:12 2019 From: alanclark at openstack.org (Alan Clark) Date: Tue, 2 Apr 2019 17:46:12 -0600 Subject: [Foundation Board] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> Message-ID: <00d601d4e9ae$41a87f50$c4f97df0$@openstack.org> Thanks for the input Sean. I’ll circle with Legal to see if the wording can be clarified. -AlanClark From: Sean McGinnis [mailto:sean.mcginnis at gmail.com] Sent: Tuesday, April 02, 2019 7:55 AM To: AlanClark at openstack.org Cc: foundation at lists.openstack.org; foundation-board at lists.openstack.org Subject: Re: [Foundation Board] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation I like the intent. I'm a little concerned with the wording making it sound like it will be the norm that discussing the review and approval of these projects will be excluded from public and recorded meetings. I understand that this enables it to happen if needed, but is there any way to codify that this is for cases where those reviews fall under the first two items mentioned to not be public? Sean On Tue, Apr 2, 2019 at 8:43 AM Alan Clark > wrote: As the OpenStack Foundation embraces new areas of strategic focus and as the associated Open Infrastructure projects mature, the OpenStack board desires to do its part in helping the projects thrive and grow. A key step in project advancement is the project confirmation by the Board. Confirmation will enable the Foundation to apply additional Foundation resources towards that project. In support of this process, the board at its last meeting, approved the OSF Project Confirmation Guidelines[1]. As the Guidelines point out, many factors go into the board’s decisions. To ensure that the board has the mechanisms needed to be as sensitive as possible to the needs and feelings for those invested in the projects, the board will further discuss a motion to amend bylaws section 4.16 as follows: (changed text in italics). 4.16 Open Meetings and Records. Except as necessary to protect attorney-client privilege, sensitive personnel information, discuss the candidacy of potential Gold Member and Platinum Members, and discuss the review and approval of Open Infrastructure Projects, the Board of Directors shall: (i) permit observation of its meetings by Members via remote teleconference or other electronic means, and (ii) publish the Board of Directors minutes and make available to any Member on request other information and records of the Foundation as required by Delaware Corporate Law. If, during confirmation discussions, a project lead or Director feels that there is sensitive information that needs to be protected this amendment provides a mechanism for such discussion. Thanks, Alan Clark [1] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines _______________________________________________ Foundation-board mailing list Foundation-board at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean.mcginnis at gmail.com Tue Apr 2 13:54:30 2019 From: sean.mcginnis at gmail.com (Sean McGinnis) Date: Tue, 2 Apr 2019 08:54:30 -0500 Subject: [Foundation Board] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: <00a501d4e95a$05623e40$1026bac0$@openstack.org> References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> Message-ID: I like the intent. I'm a little concerned with the wording making it sound like it will be the norm that discussing the review and approval of these projects will be excluded from public and recorded meetings. I understand that this enables it to happen if needed, but is there any way to codify that this is for cases where those reviews fall under the first two items mentioned to not be public? Sean On Tue, Apr 2, 2019 at 8:43 AM Alan Clark wrote: > As the OpenStack Foundation embraces new areas of strategic focus and as > the associated Open Infrastructure projects mature, the OpenStack board > desires to do its part in helping the projects thrive and grow. A key step > in project advancement is the project confirmation by the Board. > Confirmation will enable the Foundation to apply additional Foundation > resources towards that project. In support of this process, the board at > its last meeting, approved the OSF Project Confirmation Guidelines[1]. As > the Guidelines point out, many factors go into the board’s decisions. To > ensure that the board has the mechanisms needed to be as sensitive as > possible to the needs and feelings for those invested in the projects, the > board will further discuss a motion to amend bylaws section 4.16 as > follows: (changed text in italics). > > > > 4.16 Open Meetings and Records. Except as necessary to protect > attorney-client privilege, sensitive personnel information, discuss the > candidacy of potential Gold Member and Platinum Members, *and discuss the > review and approval of Open Infrastructure Projects, *the Board of > Directors shall: (i) permit observation of its meetings by Members via > remote teleconference or other electronic means, and (ii) publish the Board > of Directors minutes and make available to any Member on request other > information and records of the Foundation as required by Delaware Corporate > Law. > > > > If, during confirmation discussions, a project lead or Director feels that > there is sensitive information that needs to be protected this amendment > provides a mechanism for such discussion. > > > > Thanks, > > Alan Clark > > > > > > [1] > https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines > > > _______________________________________________ > Foundation-board mailing list > Foundation-board at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gr at ham.ie Fri Apr 5 14:54:50 2019 From: gr at ham.ie (Graham Hayes) Date: Fri, 5 Apr 2019 15:54:50 +0100 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: <00a501d4e95a$05623e40$1026bac0$@openstack.org> References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> Message-ID: On 02/04/2019 14:43, Alan Clark wrote: > 4.16 Open Meetings and Records. Except as necessary to protect > attorney-client privilege, sensitive personnel information, discuss the > candidacy of potential Gold Member and Platinum Members, /and discuss > the review and approval of Open Infrastructure Projects, /the Board of > Directors shall: (i) permit observation of its meetings by Members via > remote teleconference or other electronic means, and (ii) publish the > Board of Directors minutes and make available to any Member on request > other information and records of the Foundation as required by Delaware > Corporate Law. > > > > If, during confirmation discussions, a project lead or Director feels > that there is sensitive information that needs to be protected this > amendment provides a mechanism for such discussion. > I am still not sure what could be required for an executive session that is not covered by "sensitive personnel information" that would require this. Personally, for me, this looks like we are not abiding by our own ethos of the Four Opens - I do understand if there is personel issues with a potential project, we would want to have it discussed behind closed doors, but everything else should be in the open. If the project that is about to be included has large enough personnel issues that they could cause issues for its inclusion in the foundation, there is a very high chance that they are going to fail some of the confirmation guidelines, and that *is* something the community should have visiblity into. Even from an optics perspective - the board deciding to include or not include a project behind closed doors is not something that is representitive of the OpenStack community, and not something I think the community should be supporting. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From allison at lohutok.net Mon Apr 8 17:20:46 2019 From: allison at lohutok.net (Allison Randal) Date: Mon, 8 Apr 2019 18:20:46 +0100 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> Message-ID: <91341018-2d36-df49-70f6-7c60d5549e26@lohutok.net> We talked about this in the board meeting today, and thought that "Except as necessary" at the beginning of the sentence is sufficient for the bylaws to express that open meetings are the norm, and executive sessions are only for special limited circumstances. But, since our process for the Gold and Platinum Member candidacy is to always schedule an executive session, that might create an assumption that we will do the same for project confirmation. We thought the best place to be explicit that open meetings are the normal process for confirmation review would be in the process section at the bottom of the project confirmation guidelines: https://wiki.openstack.org/w/index.php?title=Governance/Foundation/OSFProjectConfirmationGuidelines I volunteered to make a first draft, so here is a bullet point, to add just after the point "Representatives of the pilot project will attend a discussion meeting with the Board..." ====== The discussion meeting will be an open meeting. The Board, the Foundation staff, or the pilot project may optionally request an executive session for part of the meeting, if some discussion topics have special sensitivity for legal or privacy reasons. ====== The idea is that we'll refine the wording here on the mailing lists, and then the Board will vote on the wording change to the confirmation guidelines at the same Board meeting where we vote on the Bylaws wording change. Allison On 4/2/19 2:54 PM, Sean McGinnis wrote: > I like the intent. I'm a little concerned with the wording making it > sound like it will be the norm that discussing the review and approval > of these projects will be excluded from public and recorded meetings. > > I understand that this enables it to happen if needed, but is there any > way to codify that this is for cases where those reviews fall under the > first two items mentioned to not be public? > > Sean > > > On Tue, Apr 2, 2019 at 8:43 AM Alan Clark > wrote: > > As the OpenStack Foundation embraces new areas of strategic focus > and as the associated Open Infrastructure projects mature, the > OpenStack board desires to do its part in helping the projects > thrive and grow.  A key step in project advancement is the project > confirmation by the Board.  Confirmation will enable the Foundation > to apply additional Foundation resources towards that project.  In > support of this process, the board at its last meeting, approved the > OSF Project Confirmation Guidelines[1].  As the Guidelines point > out, many factors go into the board’s decisions.  To ensure that the > board has the mechanisms needed to be as sensitive as possible to > the needs and feelings for those invested in the projects, the board > will further discuss a motion to amend bylaws section 4.16 as > follows: (changed text in italics).____ > > __ __ > > 4.16 Open Meetings and Records.  Except as necessary to protect > attorney-client privilege, sensitive personnel information, discuss > the candidacy of potential Gold Member and Platinum Members, /and > discuss the review and approval of Open Infrastructure Projects, > /the Board of Directors shall: (i) permit observation of its > meetings by Members via remote teleconference or other electronic > means, and (ii) publish the Board of Directors minutes and make > available to any Member on request other information and records of > the Foundation as required by Delaware Corporate Law.____ > > __ __ > > If, during confirmation discussions, a project lead or Director > feels that there is sensitive information that needs to be protected > this amendment provides a mechanism for such discussion.____ > > __ __ > > Thanks,____ > > Alan Clark____ > > __ __ > > __ __ > > [1] > https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmationGuidelines____ > > __ __ > > _______________________________________________ > Foundation-board mailing list > Foundation-board at lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board > > > _______________________________________________ > Foundation mailing list > Foundation at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation > From alanclark at openstack.org Tue Apr 9 22:25:28 2019 From: alanclark at openstack.org (Alan Clark) Date: Tue, 9 Apr 2019 16:25:28 -0600 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: <91341018-2d36-df49-70f6-7c60d5549e26@lohutok.net> References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> <91341018-2d36-df49-70f6-7c60d5549e26@lohutok.net> Message-ID: <005d01d4ef23$23872420$6a956c60$@openstack.org> Allison, Thank you for leading this task. I would like to suggest an additional thought to include in the wording. That the official voting will be performed within the open meetings. The same is done for Gold and Platinum member discussions today. Regards, AlanClark >-----Original Message----- >From: Allison Randal [mailto:allison at lohutok.net] >Sent: Monday, April 08, 2019 11:21 AM >To: Sean McGinnis >Cc: foundation at lists.openstack.org; foundation-board at lists.openstack.org >Subject: Re: [OpenStack Foundation] [Foundation Board] Bylaws change >proposed at next week's OpenStack board meeting to support Open >Infrastructure project confirmation > >We talked about this in the board meeting today, and thought that "Except as >necessary" at the beginning of the sentence is sufficient for the bylaws to express >that open meetings are the norm, and executive sessions are only for special >limited circumstances. But, since our process for the Gold and Platinum Member >candidacy is to always schedule an executive session, that might create an >assumption that we will do the same for project confirmation. We thought the >best place to be explicit that open meetings are the normal process for >confirmation review would be in the process section at the bottom of the project >confirmation guidelines: > >https://wiki.openstack.org/w/index.php?title=Governance/Foundation/OSFProje >ctConfirmationGuidelines > >I volunteered to make a first draft, so here is a bullet point, to add just after the >point "Representatives of the pilot project will attend a discussion meeting with >the Board..." > >====== >The discussion meeting will be an open meeting. The Board, the Foundation staff, >or the pilot project may optionally request an executive session for part of the >meeting, if some discussion topics have special sensitivity for legal or privacy >reasons. >====== > >The idea is that we'll refine the wording here on the mailing lists, and then the >Board will vote on the wording change to the confirmation guidelines at the same >Board meeting where we vote on the Bylaws wording change. > >Allison > >On 4/2/19 2:54 PM, Sean McGinnis wrote: >> I like the intent. I'm a little concerned with the wording making it >> sound like it will be the norm that discussing the review and approval >> of these projects will be excluded from public and recorded meetings. >> >> I understand that this enables it to happen if needed, but is there >> any way to codify that this is for cases where those reviews fall >> under the first two items mentioned to not be public? >> >> Sean >> >> >> On Tue, Apr 2, 2019 at 8:43 AM Alan Clark > > wrote: >> >> As the OpenStack Foundation embraces new areas of strategic focus >> and as the associated Open Infrastructure projects mature, the >> OpenStack board desires to do its part in helping the projects >> thrive and grow. A key step in project advancement is the project >> confirmation by the Board. Confirmation will enable the Foundation >> to apply additional Foundation resources towards that project. In >> support of this process, the board at its last meeting, approved the >> OSF Project Confirmation Guidelines[1]. As the Guidelines point >> out, many factors go into the board’s decisions. To ensure that the >> board has the mechanisms needed to be as sensitive as possible to >> the needs and feelings for those invested in the projects, the board >> will further discuss a motion to amend bylaws section 4.16 as >> follows: (changed text in italics).____ >> >> __ __ >> >> 4.16 Open Meetings and Records. Except as necessary to protect >> attorney-client privilege, sensitive personnel information, discuss >> the candidacy of potential Gold Member and Platinum Members, /and >> discuss the review and approval of Open Infrastructure Projects, >> /the Board of Directors shall: (i) permit observation of its >> meetings by Members via remote teleconference or other electronic >> means, and (ii) publish the Board of Directors minutes and make >> available to any Member on request other information and records of >> the Foundation as required by Delaware Corporate Law.____ >> >> __ __ >> >> If, during confirmation discussions, a project lead or Director >> feels that there is sensitive information that needs to be protected >> this amendment provides a mechanism for such discussion.____ >> >> __ __ >> >> Thanks,____ >> >> Alan Clark____ >> >> __ __ >> >> __ __ >> >> [1] >> >> https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfir >> mationGuidelines____ >> >> __ __ >> >> _______________________________________________ >> Foundation-board mailing list >> Foundation-board at lists.openstack.org >> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board >> >> >> _______________________________________________ >> Foundation mailing list >> Foundation at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >> > >_______________________________________________ >Foundation mailing list >Foundation at lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation From allison at openstack.org Tue Apr 16 20:28:59 2019 From: allison at openstack.org (Allison Price) Date: Tue, 16 Apr 2019 15:28:59 -0500 Subject: [Foundation Board] OpenStack Stein Highlights & Coverage Message-ID: <03905B0B-1243-49A7-B502-9E06A3186CEF@openstack.org> Hi everyone, The OpenStack community delivered Stein last week - a huge thanks to your teams and the 150+ organizations who contributed to the 19th release! We have had some great conversations with reporters who are excited about some of the features that were delivered, particularly: Bare metal and network improvements for containers Enhancements for edge computing / 5G use cases Improved resource management and tracking Since then, the release has earned global media coverage, with headlines emphasizing key features and community progress. Here are a few that stand out: The Register: Raise a Stein for OpenStack: Latest release brings faster containers, cloud resource management SDxCentral: OpenStack Stein saunters closer to Kubernetes, 5G and the Edge ComputerWorldUK: Community pursues tighter Kubernetes integration in OpenStack Stein TechCrunch: OpenStack Stein launches with improved Kubernetes support eWeek: OpenStack Stein improves cloud identity and orchestration You can also check out the evolving coverage list . We look forward to seeing everyone in 2 weeks where we can celebrate the community’s release achievements together! Cheers, Allison -------------- next part -------------- An HTML attachment was scrubbed... URL: From allison at lohutok.net Mon Apr 22 14:18:56 2019 From: allison at lohutok.net (Allison Randal) Date: Mon, 22 Apr 2019 10:18:56 -0400 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: <005d01d4ef23$23872420$6a956c60$@openstack.org> References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> <91341018-2d36-df49-70f6-7c60d5549e26@lohutok.net> <005d01d4ef23$23872420$6a956c60$@openstack.org> Message-ID: Hi Alan, That sounds like a good addition. To keep the wording simple, I'll suggest changing the last line of the process section to read: ========== The Board will review the project's application and vote whether to confirm it in the open meeting. ========== Allison On 4/9/19 6:25 PM, Alan Clark wrote: > Allison, Thank you for leading this task. I would like to suggest an additional thought to include in the wording. > > That the official voting will be performed within the open meetings. The same is done for Gold and Platinum member discussions today. > > Regards, > AlanClark > >> -----Original Message----- >> From: Allison Randal [mailto:allison at lohutok.net] >> Sent: Monday, April 08, 2019 11:21 AM >> To: Sean McGinnis >> Cc: foundation at lists.openstack.org; foundation-board at lists.openstack.org >> Subject: Re: [OpenStack Foundation] [Foundation Board] Bylaws change >> proposed at next week's OpenStack board meeting to support Open >> Infrastructure project confirmation >> >> We talked about this in the board meeting today, and thought that "Except as >> necessary" at the beginning of the sentence is sufficient for the bylaws to express >> that open meetings are the norm, and executive sessions are only for special >> limited circumstances. But, since our process for the Gold and Platinum Member >> candidacy is to always schedule an executive session, that might create an >> assumption that we will do the same for project confirmation. We thought the >> best place to be explicit that open meetings are the normal process for >> confirmation review would be in the process section at the bottom of the project >> confirmation guidelines: >> >> https://wiki.openstack.org/w/index.php?title=Governance/Foundation/OSFProje >> ctConfirmationGuidelines >> >> I volunteered to make a first draft, so here is a bullet point, to add just after the >> point "Representatives of the pilot project will attend a discussion meeting with >> the Board..." >> >> ====== >> The discussion meeting will be an open meeting. The Board, the Foundation staff, >> or the pilot project may optionally request an executive session for part of the >> meeting, if some discussion topics have special sensitivity for legal or privacy >> reasons. >> ====== >> >> The idea is that we'll refine the wording here on the mailing lists, and then the >> Board will vote on the wording change to the confirmation guidelines at the same >> Board meeting where we vote on the Bylaws wording change. >> >> Allison >> >> On 4/2/19 2:54 PM, Sean McGinnis wrote: >>> I like the intent. I'm a little concerned with the wording making it >>> sound like it will be the norm that discussing the review and approval >>> of these projects will be excluded from public and recorded meetings. >>> >>> I understand that this enables it to happen if needed, but is there >>> any way to codify that this is for cases where those reviews fall >>> under the first two items mentioned to not be public? >>> >>> Sean >>> >>> >>> On Tue, Apr 2, 2019 at 8:43 AM Alan Clark >> > wrote: >>> >>> As the OpenStack Foundation embraces new areas of strategic focus >>> and as the associated Open Infrastructure projects mature, the >>> OpenStack board desires to do its part in helping the projects >>> thrive and grow. A key step in project advancement is the project >>> confirmation by the Board. Confirmation will enable the Foundation >>> to apply additional Foundation resources towards that project. In >>> support of this process, the board at its last meeting, approved the >>> OSF Project Confirmation Guidelines[1]. As the Guidelines point >>> out, many factors go into the board’s decisions. To ensure that the >>> board has the mechanisms needed to be as sensitive as possible to >>> the needs and feelings for those invested in the projects, the board >>> will further discuss a motion to amend bylaws section 4.16 as >>> follows: (changed text in italics).____ >>> >>> __ __ >>> >>> 4.16 Open Meetings and Records. Except as necessary to protect >>> attorney-client privilege, sensitive personnel information, discuss >>> the candidacy of potential Gold Member and Platinum Members, /and >>> discuss the review and approval of Open Infrastructure Projects, >>> /the Board of Directors shall: (i) permit observation of its >>> meetings by Members via remote teleconference or other electronic >>> means, and (ii) publish the Board of Directors minutes and make >>> available to any Member on request other information and records of >>> the Foundation as required by Delaware Corporate Law.____ >>> >>> __ __ >>> >>> If, during confirmation discussions, a project lead or Director >>> feels that there is sensitive information that needs to be protected >>> this amendment provides a mechanism for such discussion.____ >>> >>> __ __ >>> >>> Thanks,____ >>> >>> Alan Clark____ >>> >>> __ __ >>> >>> __ __ >>> >>> [1] >>> >>> https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfir >>> mationGuidelines____ >>> >>> __ __ >>> >>> _______________________________________________ >>> Foundation-board mailing list >>> Foundation-board at lists.openstack.org >>> >>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board >>> >>> >>> _______________________________________________ >>> Foundation mailing list >>> Foundation at lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >>> >> >> _______________________________________________ >> Foundation mailing list >> Foundation at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation > > > _______________________________________________ > Foundation mailing list > Foundation at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation > From mark.radcliffe at dlapiper.com Mon Apr 22 16:17:55 2019 From: mark.radcliffe at dlapiper.com (Radcliffe, Mark) Date: Mon, 22 Apr 2019 16:17:55 +0000 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> <91341018-2d36-df49-70f6-7c60d5549e26@lohutok.net> <005d01d4ef23$23872420$6a956c60$@openstack.org> Message-ID: I think that this approach is fine if included in the process section. -----Original Message----- From: Allison Randal Sent: Monday, April 22, 2019 7:19 AM To: AlanClark at openstack.org; 'Sean McGinnis' Cc: foundation at lists.openstack.org; foundation-board at lists.openstack.org Subject: Re: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation [EXTERNAL] Hi Alan, That sounds like a good addition. To keep the wording simple, I'll suggest changing the last line of the process section to read: ========== The Board will review the project's application and vote whether to confirm it in the open meeting. ========== Allison On 4/9/19 6:25 PM, Alan Clark wrote: > Allison, Thank you for leading this task. I would like to suggest an additional thought to include in the wording. > > That the official voting will be performed within the open meetings. The same is done for Gold and Platinum member discussions today. > > Regards, > AlanClark > >> -----Original Message----- >> From: Allison Randal [mailto:allison at lohutok.net] >> Sent: Monday, April 08, 2019 11:21 AM >> To: Sean McGinnis >> Cc: foundation at lists.openstack.org; >> foundation-board at lists.openstack.org >> Subject: Re: [OpenStack Foundation] [Foundation Board] Bylaws change >> proposed at next week's OpenStack board meeting to support Open >> Infrastructure project confirmation >> >> We talked about this in the board meeting today, and thought that >> "Except as necessary" at the beginning of the sentence is sufficient >> for the bylaws to express that open meetings are the norm, and >> executive sessions are only for special limited circumstances. But, >> since our process for the Gold and Platinum Member candidacy is to >> always schedule an executive session, that might create an assumption >> that we will do the same for project confirmation. We thought the >> best place to be explicit that open meetings are the normal process >> for confirmation review would be in the process section at the bottom of the project confirmation guidelines: >> >> https://wiki.openstack.org/w/index.php?title=Governance/Foundation/OS >> FProje >> ctConfirmationGuidelines >> >> I volunteered to make a first draft, so here is a bullet point, to >> add just after the point "Representatives of the pilot project will >> attend a discussion meeting with the Board..." >> >> ====== >> The discussion meeting will be an open meeting. The Board, the >> Foundation staff, or the pilot project may optionally request an >> executive session for part of the meeting, if some discussion topics >> have special sensitivity for legal or privacy reasons. >> ====== >> >> The idea is that we'll refine the wording here on the mailing lists, >> and then the Board will vote on the wording change to the >> confirmation guidelines at the same Board meeting where we vote on the Bylaws wording change. >> >> Allison >> >> On 4/2/19 2:54 PM, Sean McGinnis wrote: >>> I like the intent. I'm a little concerned with the wording making it >>> sound like it will be the norm that discussing the review and >>> approval of these projects will be excluded from public and recorded meetings. >>> >>> I understand that this enables it to happen if needed, but is there >>> any way to codify that this is for cases where those reviews fall >>> under the first two items mentioned to not be public? >>> >>> Sean >>> >>> >>> On Tue, Apr 2, 2019 at 8:43 AM Alan Clark >> > wrote: >>> >>> As the OpenStack Foundation embraces new areas of strategic focus >>> and as the associated Open Infrastructure projects mature, the >>> OpenStack board desires to do its part in helping the projects >>> thrive and grow. A key step in project advancement is the project >>> confirmation by the Board. Confirmation will enable the Foundation >>> to apply additional Foundation resources towards that project. In >>> support of this process, the board at its last meeting, approved the >>> OSF Project Confirmation Guidelines[1]. As the Guidelines point >>> out, many factors go into the board’s decisions. To ensure that the >>> board has the mechanisms needed to be as sensitive as possible to >>> the needs and feelings for those invested in the projects, the board >>> will further discuss a motion to amend bylaws section 4.16 as >>> follows: (changed text in italics).____ >>> >>> __ __ >>> >>> 4.16 Open Meetings and Records. Except as necessary to protect >>> attorney-client privilege, sensitive personnel information, discuss >>> the candidacy of potential Gold Member and Platinum Members, /and >>> discuss the review and approval of Open Infrastructure Projects, >>> /the Board of Directors shall: (i) permit observation of its >>> meetings by Members via remote teleconference or other electronic >>> means, and (ii) publish the Board of Directors minutes and make >>> available to any Member on request other information and records of >>> the Foundation as required by Delaware Corporate Law.____ >>> >>> __ __ >>> >>> If, during confirmation discussions, a project lead or Director >>> feels that there is sensitive information that needs to be protected >>> this amendment provides a mechanism for such discussion.____ >>> >>> __ __ >>> >>> Thanks,____ >>> >>> Alan Clark____ >>> >>> __ __ >>> >>> __ __ >>> >>> [1] >>> >>> https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConf >>> ir >>> mationGuidelines____ >>> >>> __ __ >>> >>> _______________________________________________ >>> Foundation-board mailing list >>> Foundation-board at lists.openstack.org >>> >>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board >>> >>> >>> _______________________________________________ >>> Foundation mailing list >>> Foundation at lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >>> >> >> _______________________________________________ >> Foundation mailing list >> Foundation at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation > > > _______________________________________________ > Foundation mailing list > Foundation at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation > _______________________________________________ Foundation-board mailing list Foundation-board at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board Please consider the environment before printing this email. The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster at dlapiper.com. Thank you. From clemens.hardewig at crandale.de Mon Apr 22 16:50:51 2019 From: clemens.hardewig at crandale.de (=?utf-8?Q?Clemens_Hardewig?=) Date: Mon, 22 Apr 2019 16:50:51 +0000 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> <91341018-2d36-df49-70f6-7c60d5549e26@lohutok.net> <005d01d4ef23$23872420$6a956c60$@openstack.org> Message-ID: All, Very good proposal, thanks! Br c Von meinem iPhone gesendet > Am 22.04.2019 um 18:19 schrieb Radcliffe, Mark : > > I think that this approach is fine if included in the process section. > -----Original Message----- > From: Allison Randal > Sent: Monday, April 22, 2019 7:19 AM > To: AlanClark at openstack.org; 'Sean McGinnis' > Cc: foundation at lists.openstack.org; foundation-board at lists.openstack.org > Subject: Re: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation > > [EXTERNAL] > > Hi Alan, > > That sounds like a good addition. To keep the wording simple, I'll suggest changing the last line of the process section to read: > > ========== > The Board will review the project's application and vote whether to confirm it in the open meeting. > ========== > > Allison > >> On 4/9/19 6:25 PM, Alan Clark wrote: >> Allison, Thank you for leading this task. I would like to suggest an additional thought to include in the wording. >> >> That the official voting will be performed within the open meetings. The same is done for Gold and Platinum member discussions today. >> >> Regards, >> AlanClark >> >>> -----Original Message----- >>> From: Allison Randal [mailto:allison at lohutok.net] >>> Sent: Monday, April 08, 2019 11:21 AM >>> To: Sean McGinnis >>> Cc: foundation at lists.openstack.org; >>> foundation-board at lists.openstack.org >>> Subject: Re: [OpenStack Foundation] [Foundation Board] Bylaws change >>> proposed at next week's OpenStack board meeting to support Open >>> Infrastructure project confirmation >>> >>> We talked about this in the board meeting today, and thought that >>> "Except as necessary" at the beginning of the sentence is sufficient >>> for the bylaws to express that open meetings are the norm, and >>> executive sessions are only for special limited circumstances. But, >>> since our process for the Gold and Platinum Member candidacy is to >>> always schedule an executive session, that might create an assumption >>> that we will do the same for project confirmation. We thought the >>> best place to be explicit that open meetings are the normal process >>> for confirmation review would be in the process section at the bottom of the project confirmation guidelines: >>> >>> https://wiki.openstack.org/w/index.php?title=Governance/Foundation/OS >>> FProje >>> ctConfirmationGuidelines >>> >>> I volunteered to make a first draft, so here is a bullet point, to >>> add just after the point "Representatives of the pilot project will >>> attend a discussion meeting with the Board..." >>> >>> ====== >>> The discussion meeting will be an open meeting. The Board, the >>> Foundation staff, or the pilot project may optionally request an >>> executive session for part of the meeting, if some discussion topics >>> have special sensitivity for legal or privacy reasons. >>> ====== >>> >>> The idea is that we'll refine the wording here on the mailing lists, >>> and then the Board will vote on the wording change to the >>> confirmation guidelines at the same Board meeting where we vote on the Bylaws wording change. >>> >>> Allison >>> >>>> On 4/2/19 2:54 PM, Sean McGinnis wrote: >>>> I like the intent. I'm a little concerned with the wording making it >>>> sound like it will be the norm that discussing the review and >>>> approval of these projects will be excluded from public and recorded meetings. >>>> >>>> I understand that this enables it to happen if needed, but is there >>>> any way to codify that this is for cases where those reviews fall >>>> under the first two items mentioned to not be public? >>>> >>>> Sean >>>> >>>> >>>> On Tue, Apr 2, 2019 at 8:43 AM Alan Clark >>> > wrote: >>>> >>>> As the OpenStack Foundation embraces new areas of strategic focus >>>> and as the associated Open Infrastructure projects mature, the >>>> OpenStack board desires to do its part in helping the projects >>>> thrive and grow. A key step in project advancement is the project >>>> confirmation by the Board. Confirmation will enable the Foundation >>>> to apply additional Foundation resources towards that project. In >>>> support of this process, the board at its last meeting, approved the >>>> OSF Project Confirmation Guidelines[1]. As the Guidelines point >>>> out, many factors go into the board’s decisions. To ensure that the >>>> board has the mechanisms needed to be as sensitive as possible to >>>> the needs and feelings for those invested in the projects, the board >>>> will further discuss a motion to amend bylaws section 4.16 as >>>> follows: (changed text in italics).____ >>>> >>>> __ __ >>>> >>>> 4.16 Open Meetings and Records. Except as necessary to protect >>>> attorney-client privilege, sensitive personnel information, discuss >>>> the candidacy of potential Gold Member and Platinum Members, /and >>>> discuss the review and approval of Open Infrastructure Projects, >>>> /the Board of Directors shall: (i) permit observation of its >>>> meetings by Members via remote teleconference or other electronic >>>> means, and (ii) publish the Board of Directors minutes and make >>>> available to any Member on request other information and records of >>>> the Foundation as required by Delaware Corporate Law.____ >>>> >>>> __ __ >>>> >>>> If, during confirmation discussions, a project lead or Director >>>> feels that there is sensitive information that needs to be protected >>>> this amendment provides a mechanism for such discussion.____ >>>> >>>> __ __ >>>> >>>> Thanks,____ >>>> >>>> Alan Clark____ >>>> >>>> __ __ >>>> >>>> __ __ >>>> >>>> [1] >>>> >>>> https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConf >>>> ir >>>> mationGuidelines____ >>>> >>>> __ __ >>>> >>>> _______________________________________________ >>>> Foundation-board mailing list >>>> Foundation-board at lists.openstack.org >>>> >>>> >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board >>>> >>>> >>>> _______________________________________________ >>>> Foundation mailing list >>>> Foundation at lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >>>> >>> >>> _______________________________________________ >>> Foundation mailing list >>> Foundation at lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >> >> >> _______________________________________________ >> Foundation mailing list >> Foundation at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >> > > _______________________________________________ > Foundation-board mailing list > Foundation-board at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board > > Please consider the environment before printing this email. > > The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster at dlapiper.com. Thank you. > _______________________________________________ > Foundation-board mailing list > Foundation-board at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board From ACLARK at suse.com Mon Apr 22 17:38:49 2019 From: ACLARK at suse.com (Alan Clark) Date: Mon, 22 Apr 2019 17:38:49 +0000 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> <91341018-2d36-df49-70f6-7c60d5549e26@lohutok.net> <005d01d4ef23$23872420$6a956c60$@openstack.org> Message-ID: That works! AlanClark >-----Original Message----- >From: Allison Randal [mailto:allison at lohutok.net] >Sent: Monday, April 22, 2019 8:19 AM >To: 'Sean McGinnis' ; AlanClark at openstack.org >Cc: foundation at lists.openstack.org; foundation-board at lists.openstack.org >Subject: Re: [Foundation Board] [OpenStack Foundation] Bylaws change >proposed at next week's OpenStack board meeting to support Open >Infrastructure project confirmation > >Hi Alan, > >That sounds like a good addition. To keep the wording simple, I'll suggest >changing the last line of the process section to read: > >========== >The Board will review the project's application and vote whether to confirm it in >the open meeting. >========== > >Allison > >On 4/9/19 6:25 PM, Alan Clark wrote: >> Allison, Thank you for leading this task. I would like to suggest an additional >thought to include in the wording. >> >> That the official voting will be performed within the open meetings. The same >is done for Gold and Platinum member discussions today. >> >> Regards, >> AlanClark >> >>> -----Original Message----- >>> From: Allison Randal [mailto:allison at lohutok.net] >>> Sent: Monday, April 08, 2019 11:21 AM >>> To: Sean McGinnis >>> Cc: foundation at lists.openstack.org; >>> foundation-board at lists.openstack.org >>> Subject: Re: [OpenStack Foundation] [Foundation Board] Bylaws change >>> proposed at next week's OpenStack board meeting to support Open >>> Infrastructure project confirmation >>> >>> We talked about this in the board meeting today, and thought that >>> "Except as necessary" at the beginning of the sentence is sufficient >>> for the bylaws to express that open meetings are the norm, and >>> executive sessions are only for special limited circumstances. But, >>> since our process for the Gold and Platinum Member candidacy is to >>> always schedule an executive session, that might create an assumption >>> that we will do the same for project confirmation. We thought the >>> best place to be explicit that open meetings are the normal process >>> for confirmation review would be in the process section at the bottom of the >project confirmation guidelines: >>> >>> https://wiki.openstack.org/w/index.php?title=Governance/Foundation/OS >>> FProje >>> ctConfirmationGuidelines >>> >>> I volunteered to make a first draft, so here is a bullet point, to >>> add just after the point "Representatives of the pilot project will >>> attend a discussion meeting with the Board..." >>> >>> ====== >>> The discussion meeting will be an open meeting. The Board, the >>> Foundation staff, or the pilot project may optionally request an >>> executive session for part of the meeting, if some discussion topics >>> have special sensitivity for legal or privacy reasons. >>> ====== >>> >>> The idea is that we'll refine the wording here on the mailing lists, >>> and then the Board will vote on the wording change to the >>> confirmation guidelines at the same Board meeting where we vote on the >Bylaws wording change. >>> >>> Allison >>> >>> On 4/2/19 2:54 PM, Sean McGinnis wrote: >>>> I like the intent. I'm a little concerned with the wording making it >>>> sound like it will be the norm that discussing the review and >>>> approval of these projects will be excluded from public and recorded >meetings. >>>> >>>> I understand that this enables it to happen if needed, but is there >>>> any way to codify that this is for cases where those reviews fall >>>> under the first two items mentioned to not be public? >>>> >>>> Sean >>>> >>>> >>>> On Tue, Apr 2, 2019 at 8:43 AM Alan Clark >>> > wrote: >>>> >>>> As the OpenStack Foundation embraces new areas of strategic focus >>>> and as the associated Open Infrastructure projects mature, the >>>> OpenStack board desires to do its part in helping the projects >>>> thrive and grow. A key step in project advancement is the project >>>> confirmation by the Board. Confirmation will enable the Foundation >>>> to apply additional Foundation resources towards that project. In >>>> support of this process, the board at its last meeting, approved the >>>> OSF Project Confirmation Guidelines[1]. As the Guidelines point >>>> out, many factors go into the board’s decisions. To ensure that the >>>> board has the mechanisms needed to be as sensitive as possible to >>>> the needs and feelings for those invested in the projects, the board >>>> will further discuss a motion to amend bylaws section 4.16 as >>>> follows: (changed text in italics).____ >>>> >>>> __ __ >>>> >>>> 4.16 Open Meetings and Records. Except as necessary to protect >>>> attorney-client privilege, sensitive personnel information, discuss >>>> the candidacy of potential Gold Member and Platinum Members, /and >>>> discuss the review and approval of Open Infrastructure Projects, >>>> /the Board of Directors shall: (i) permit observation of its >>>> meetings by Members via remote teleconference or other electronic >>>> means, and (ii) publish the Board of Directors minutes and make >>>> available to any Member on request other information and records of >>>> the Foundation as required by Delaware Corporate Law.____ >>>> >>>> __ __ >>>> >>>> If, during confirmation discussions, a project lead or Director >>>> feels that there is sensitive information that needs to be protected >>>> this amendment provides a mechanism for such discussion.____ >>>> >>>> __ __ >>>> >>>> Thanks,____ >>>> >>>> Alan Clark____ >>>> >>>> __ __ >>>> >>>> __ __ >>>> >>>> [1] >>>> >>>> https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConf >>>> ir >>>> mationGuidelines____ >>>> >>>> __ __ >>>> >>>> _______________________________________________ >>>> Foundation-board mailing list >>>> Foundation-board at lists.openstack.org >>>> >>>> >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board >>>> >>>> >>>> _______________________________________________ >>>> Foundation mailing list >>>> Foundation at lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >>>> >>> >>> _______________________________________________ >>> Foundation mailing list >>> Foundation at lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >> >> >> _______________________________________________ >> Foundation mailing list >> Foundation at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation >> > >_______________________________________________ >Foundation-board mailing list >Foundation-board at lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation-board From markmc at redhat.com Sun Apr 28 20:45:43 2019 From: markmc at redhat.com (Mark McLoughlin) Date: Sun, 28 Apr 2019 21:45:43 +0100 Subject: [Foundation Board] [OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation In-Reply-To: References: <00a501d4e95a$05623e40$1026bac0$@openstack.org> Message-ID: On Fri, Apr 5, 2019 at 4:02 PM Graham Hayes wrote: > On 02/04/2019 14:43, Alan Clark wrote: > > > 4.16 Open Meetings and Records. Except as necessary to protect > > attorney-client privilege, sensitive personnel information, discuss the > > candidacy of potential Gold Member and Platinum Members, /and discuss > > the review and approval of Open Infrastructure Projects, /the Board of > > Directors shall: (i) permit observation of its meetings by Members via > > remote teleconference or other electronic means, and (ii) publish the > > Board of Directors minutes and make available to any Member on request > > other information and records of the Foundation as required by Delaware > > Corporate Law. > > > > > > > > If, during confirmation discussions, a project lead or Director feels > > that there is sensitive information that needs to be protected this > > amendment provides a mechanism for such discussion. > > > I am still not sure what could be required for an executive session that > is not covered by "sensitive personnel information" that would require > this. > > Personally, for me, this looks like we are not abiding by our own ethos > of the Four Opens - I do understand if there is personel issues with a > potential project, we would want to have it discussed behind closed > doors, but everything else should be in the open. If the project > that is about to be included has large enough personnel issues that > they could cause issues for its inclusion in the foundation, there > is a very high chance that they are going to fail some of the > confirmation guidelines, and that *is* something the community > should have visiblity into. > > Even from an optics perspective - the board deciding to include or > not include a project behind closed doors is not something that > is representitive of the OpenStack community, and not something > I think the community should be supporting. > I know there's some lingering concern about this, and I'm generally against matters of wider community interest being discussed in executive session, but I'm comfortable about this proposal because: a) There is no default expectation of having an executive session before every confirmation vote - indeed, we've had two now with no executive session b) Anyone who does request an executive session will have to justify to the board why the topic is so sensitive that it requires executive session c) Confirming a project means the OSF making a long-term commitment to that project - I'd much rather there to be some mechanism for people to raise sensitive concerns, rather than risk projects being confirmed without those concerns ever getting raised d) The confirmation vote will happen in public - if there is any controversy, I expect it would be apparent from the voting, and I expect board members would feel compelled to give some explanation for their voting rather than leave the community completely in the dark Hope that helps, Mark. -------------- next part -------------- An HTML attachment was scrubbed... URL: