September 2023 - Foundation - lists.openinfra.dev

October meeting of the OpenInfra Board of Directors has been cancelled
by Julia Kreger 22 Sep '23

22 Sep '23

Greetings, Per my email to the foundation-board list[0] on September 19th, I have cancelled the October meeting of the Board of Directors after discussion with the Foundation staff and the Vice-Chair. We will meet in November during the scheduled time. For those of you attending that meeting, please be prepared for us to utilize the entire scheduled window as we will have a number of topics to address during that meeting in large part due to the time of year in preparation for 2024. Thanks, and we'll see you in November! -Julia [0]: https://lists.openinfra.dev/archives/list/foundation-board@lists.openinfra.…

1 0

Mailman v3 migration for OpenInfra mailing lists 2023-09-21
by Jeremy Stanley 21 Sep '23

21 Sep '23

On Thursday, September 21 at 15:30 UTC, the OpenDev Collaboratory systems administrators will be migrating the lists.openinfra.dev mailing list site from the aging Mailman 2.1.29 server to a newer Mailman 3.3.8 deployment. This maintenance window is expected to last no more than one hour. The key takeaways are as follows: * There will be a brief outage for the site while DNS is updated and configuration, subscriber lists and message archives are imported, but incoming messages should correctly queue at the sender's end and arrive at the conclusion of our work * Because this is on a new server, there are new IP addresses from which list mail will be originating: 162.209.78.70 and 2001:4800:7813:516:be76:4eff:fe04:5423 * Moderation queues will not be copied to the new server, so moderators are encouraged to process any held messages prior to the migration time in order to avoid losing them * Anyone wishing to adjust their list subscriptions, or handle moderation or list configuration after the migration, needs to use the Sign Up button on the Web page to create a new account; it will be linked to your imported roles as soon as you confirm by following a URL from an E-mail message the server sends you, and is global for all sites on the server so you only need to do this once * The software providing Web front-ends for list management and archive browsing is entirely new in Mailman v3 and therefore has a much different appearance, though we've added appropriate redirects and frozen copies of old archives in order to accommodate existing hyperlinks If you have any questions or concerns, feel free to follow up on the service-discuss mailing list or find us in the #opendev channel on the OFTC IRC network. -- Jeremy Stanley

1 1

None
by None 21 Sep '23

21 Sep '23

> How are participating organizations going to join the foundation, and > what dollar amounts grant the donor organization what rights? Is it a > good idea to look at separating the (currently singular) Project > Policy Board into at least two boards, one focused on technical > matters and another focused on legal, copyright, and trademark issues? As I said during the Town Hall session at the Conference, I think there needs to be a Board of directors (where membership is linked to your company commitment to OpenStack, including monetary) that is separate from the Technical board (which should become a pure elected code committer meritocracy). This board of directors should handle how the Foundation money is spent (including setting compensation for Foundation employees, if any), should encourage participation and focus on legal issues. Should they also handle (or participate to) the OpenStack scope definition ? The board of directors could have Strategic members (that show a multi-year monetary commitment, together with some measurable level of strategic involvement in the project, to be defined) with one seat each. It should also have Sustaining members: a number of seats for representatives of the wider ecosystem of companies showing interest in OpenStack. For example, if you have 5 strategic members and 80 ordinary companies, you could have a total of 9 seats, with all ordinary companies holding an election to decide who should represent them on their 4 board seats. The Technical board should rule on all technical matters, and should be purely elected from the current corpus of code committers (one author / one vote). It should be kept small for efficiency reasons (9 or 11 members ?). There could be safeguards in place to avoid that a single company gets more than 50% of the seats. I think PTLs should run for election like any other committer: if they don't end up being elected, they can still participate to technical board meetings, but without a vote. -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Foundation mailing list Foundation(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

1 0

None
by None 21 Sep '23

21 Sep '23

> Should the foundation even have employees, or should foundation roles > simply be employees of donor organizations, with their salaries > composing some part of foundation membership dues? I'd say both options are on the table, and they don't have to be exclusive. Someone working full-time on Foundation-owned tasks (see "Scope of Foundation" thread) should be considered working on the Foundation. In the same area, will the foundation need specific officers (delegations of power from the board of directors or technical board) ? Or can it all be run from the boards themselves ? What would be those roles ? I'm a big fan of letting people do the work and impose themselves as the natural person in charge (rather than be appointed and not necessarily do the work well), but in this precise case it may fall a bit short... -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Foundation mailing list Foundation(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

1 0

None
by None 21 Sep '23

21 Sep '23

> What, if any, technical roles should be placed into the foundation? > Release management? Community management? Infrastructure development > like Jenkins and source control, list management, etc? I think the foundation should definitely own the infrastructure necessary to produce OpenStack core projects. Servers and manpower could be donated by one member (and its value be deduced somehow of its membership fee), but in the end, I think the task of keeping everything running should be a Foundation task. > Should openstack.org and the maintenance of that site be moved under > control of foundation employees? I think it would make sense. openstack.org would probably end up being the foundation domain ? -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Foundation mailing list Foundation(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

1 0

None
by None 21 Sep '23

21 Sep '23

> How are participating organizations going to join the foundation, and > what dollar amounts grant the donor organization what rights? Is it a > good idea to look at separating the (currently singular) Project > Policy Board into at least two boards, one focused on technical > matters and another focused on legal, copyright, and trademark issues? As I said during the Town Hall session at the Conference, I think there needs to be a Board of directors (where membership is linked to your company commitment to OpenStack, including monetary) that is separate from the Technical board (which should become a pure elected code committer meritocracy). This board of directors should handle how the Foundation money is spent (including setting compensation for Foundation employees, if any), should encourage participation and focus on legal issues. Should they also handle (or participate to) the OpenStack scope definition ? The board of directors could have Strategic members (that show a multi-year monetary commitment, together with some measurable level of strategic involvement in the project, to be defined) with one seat each. It should also have Sustaining members: a number of seats for representatives of the wider ecosystem of companies showing interest in OpenStack. For example, if you have 5 strategic members and 80 ordinary companies, you could have a total of 9 seats, with all ordinary companies holding an election to decide who should represent them on their 4 board seats. The Technical board should rule on all technical matters, and should be purely elected from the current corpus of code committers (one author / one vote). It should be kept small for efficiency reasons (9 or 11 members ?). There could be safeguards in place to avoid that a single company gets more than 50% of the seats. I think PTLs should run for election like any other committer: if they don't end up being elected, they can still participate to technical board meetings, but without a vote. -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Foundation mailing list Foundation(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

1 0

None
by None 21 Sep '23

21 Sep '23

> What, if any, technical roles should be placed into the foundation? > Release management? Community management? Infrastructure development > like Jenkins and source control, list management, etc? I think the foundation should definitely own the infrastructure necessary to produce OpenStack core projects. Servers and manpower could be donated by one member (and its value be deduced somehow of its membership fee), but in the end, I think the task of keeping everything running should be a Foundation task. > Should openstack.org and the maintenance of that site be moved under > control of foundation employees? I think it would make sense. openstack.org would probably end up being the foundation domain ? -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Foundation mailing list Foundation(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

1 0

None
by None 21 Sep '23

21 Sep '23

> Should the foundation even have employees, or should foundation roles > simply be employees of donor organizations, with their salaries > composing some part of foundation membership dues? I'd say both options are on the table, and they don't have to be exclusive. Someone working full-time on Foundation-owned tasks (see "Scope of Foundation" thread) should be considered working on the Foundation. In the same area, will the foundation need specific officers (delegations of power from the board of directors or technical board) ? Or can it all be run from the boards themselves ? What would be those roles ? I'm a big fan of letting people do the work and impose themselves as the natural person in charge (rather than be appointed and not necessarily do the work well), but in this precise case it may fall a bit short... -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Foundation mailing list Foundation(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation

1 0

OpenInfra Live - Sept. 21 at 9 a.m. CT / 1400 UTC
by Kristin Barrientos 20 Sep '23

20 Sep '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenStack Large Scale SIG. Episode: Large Scale Ops Deep Dive: NIPA Cloud In the "Large Scale Ops Deep Dive" series, a panel of OpenStack operators invites special guests to talk about their deployment and discuss their operations. For this episode, our guests will be Dr. Abhisak Chulya and Charnsilp Chinprasert from NIPA Cloud, Thailand's largest OpenStack public cloud provider. Speakers: Dr. Abhisak Chulya, Charnsilp Chinprasert, Arnaud Morin, Felix Huettner, Thierry Carrez, Kristin Barrientos Date and time: Sept. 21 at 9 a.m. CT / 1400 UTC You can watch us live on: YouTube: https://www.youtube.com/watch?v=ir9v_UK_MIA LinkedIn: https://www.linkedin.com/events/7085718563113603072/comments/ WeChat: recording will be posted on OpenStack WeChat after the live stream Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[Diversity] Diversity and Inclusion WG Meeting reminder
by Amy Marrich 11 Sep '23

11 Sep '23

This is a reminder that the Diversity and Inclusion WG will be meeting tomorrow at 14:00 UTC in the #openinfra-diversity channel on OFTC. We hope members of all OpenInfra projects join us as we look at the progress on responses to the Foundation-wide diversity survey. Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/diversity-wg-agenda

1 0