January 2024 - Foundation-board - lists.openinfra.dev

Follow-up on Today's informal working group session on AI
by Julia Kreger 20 Feb '24

20 Feb '24

Greetings Directors, Earlier today, Eoghan Glynn, Phil Rob, Allison Randall, and I met from the informal working group meeting invite I sent out earlier in the week. Discussion focused around the creation of bullet points of what we need to tackle, which evolved into the general idea that we need to take on a three part approach to move forward. The first area of consensus was to draft a document laying out: * Set Common Understanding - We need to set the common words to be used and note there are two basic extremes. In essence, a spectrum from autocomplete to entirely machine generated output. We also have consensus that we expect code contributions to be made by humans, which may change as time moves on, outside of robotic process driven changes, for example requirements management or translation batch updates which occur today as well understood automated processes. * Build a common Identification system for changes - Where and How it was used. Reach consensus with some sort of labeling for commit messages, for consistency across projects. There seems to be agreement that this needs to involve identification of the tool and most likely some level of quantity or percentage. The overall goal being to get this into general practice sooner rather than later, and to likely adopt the ASF suggested Generated-By tag, in addition to some other Generated-Percentage or Generated-Level tag. Naturally we would expect the latter to likely change through the process of code review. * Establish bounds/guidelines for projects in what we expect, and what they can and cannot do. This likely includes alignment with the four opens so reviewers can attempt to determine how a tool might line up and if the contribution is able to be accepted, or not, based upon the tagging. This is the area we likely expect to explicitly name an example of what is not permissible, and possibly include a list of known tag values to aid consistency when it comes time to generate reporting. The second area of consensus is in the form of two specific paths forward above and beyond an initial guidance document. Allison made a really good point that we should not block on either of these areas. * We likely want to see some form of Attestation by the submitter of the change along the lines of DCO, that suggests "I've carefully reviewed this, I fully understand what it does, I have legal right to submit this along with a copyright assignment". In a sense, the DCO already sort of serves this purpose for some projects, but the variable of AI is an interesting one, and the consensus is that we expect there is a need for some cross-foundation collaboration on appropriate guidance since it is more than just our OpenInfra ecosystem. * We want to see a centralized review guide to both provide guidance of things to look at/for, and also help serve the pipeline of reviewers in general. It might have principles such as "does style conform?", "Does CI pass?", but this is nowhere near an exhaustive list and we expect some iteration may be necessary with our communities and projects to have the right level/form of guidance. Which leaves the next step. We'll provide a brief update during the upcoming board meeting[0], and have a call for participants to work together on drafting the guidance document. Once we have written words in a reviewable form, we'll reach out to our legal counsel for their input, and move forward from there. Thanks, -Julia [0]: https://board.openinfra.dev/en/meetings/2023-11-07

4 6

Event Feedback for In-Person Board Meeting
by Allison Price 31 Jan '24

31 Jan '24

Hi everyone, Thank you for a great first OpenInfra board meeting of 2024! As I mentioned, I wanted to share the etherpad that has upcoming OpenInfra events. Please put your name under the events you think you would be able to attend. The Foundation staff will then work with you all to identify the best event(s) for an in-person board meeting. Etherpad: https://etherpad.opendev.org/p/OpenInfraEvents2024_BoardPlanning If you have any questions, please let me know or drop them directly in the etherpad. Thank you! Allison Allison Price VP of Marketing & Community OpenInfra Foundation <https://openinfra.dev/> p: +1-214-686-6821

1 0

OpenInfra Foundation Board of Directors Meeting, January 30th, 2024 at 1500-1700 UTC.
by Julia Kreger 26 Jan '24

26 Jan '24

Greetings, The next meeting of the OpenInfra Foundation Board of Directors will be on Tuesday, January 30th, 2024 from 7:00 to 9:00 AM US Pacific (1500-1700 UTC). During this meeting, we will be seating directors for 2024, and performing the required housekeeping activities for the new year. We also anticipate receiving an update from the foundation staff as we begin our work for this year. Meeting Date: January 30th, 2024 Meeting Time: 1500-1700 UTC / 7:00 - 9:00 AM US Pacific Video conference: https://zoom.us/j/96201224963 International dial-in (audio only): https://zoom.us/zoomconference (conference ID #962 0122 4963) To join the session by phone only: +1 669 900 6833 US (San Jose) OR +1 646 876 9923 US (New York) Meeting ID: 962 0122 4963 Agenda: https://board.openinfra.dev/meetings/2024-01-30 Please feel free to reach out if you have any questions. Thanks, -Julia

1 0

Update on EU Cyber Resilience Act (CRA)
by Thierry Carrez 05 Jan '24

05 Jan '24

Hi everyone, Last month the Cyber-Resilience Act (“CRA”) passed a major milestone, with a common text being agreed upon between the European Commission, Council and Parliament at the end of the Trilogue negotiations. The text, which was until now only available as selected leaks, was formally published on December 20 within this communication to the Parliament: https://data.consilium.europa.eu/doc/document/ST-17000-2023-INIT/EN/pdf The intent and spirit of the text remains very much the same: applying CE marking and basic product security principles to software. As such, it is going to affect all organizations providing software products on the European market, whether they leverage open source software or not. That said, it’s clear in this version of the text that the engagement of a lot of open source advocacy groups (including OpenInfra Foundation) has led to multiple clarifications. Those clarifications reduce the disconnect between the text and the openly-developed open source model, and reduce the risk of global chilling effects around open source development participation. In particular: - The funding of essential project support functions, without the intention to make a profit, does not constitute “commercial activity” and therefore is not within the scope of this regulation (see recital 10 on page 10 and recital 10c on page 12) - There is now a clear distinction between the development and the supply phases, with the regulation clearly triggering at the supply phase (when the software is put on the market in the course of a commercial activity) (recital 10c, page 12) - Foundations should be considered “open-source software stewards” (as defined in Article 3 point (18a), page 76), and should be subject to a light-touch and tailor-made regulatory regime (recital 10d, page 13), exempted from penalties (article 53(10a), page 159) The proposed text is likely to be adopted as-is by the Parliament (see cover letter on page 2), so now is a good time to get more familiar with its details. Even if the text is adopted as-is, there is a lot more to come in the future as this regulation will need practical implementation guidelines. We’ll continue to watch that space and keep you informed of future developments – I’ll be representing the OpenInfra Foundation in conversations on this topic at the EU Open Source Policy Summit and FOSDEM events in Brussels in a few weeks. We also plan to continue policy news briefings during board meetings in 2024, like DLA Piper did in Vancouver last year. Regards, Thierry Carrez General Manager, OpenInfra Foundation

2 2

OpenInfra Labs pilot project archival
by Jeremy Stanley 05 Jan '24

05 Jan '24

OpenInfra Labs was launched as a pilot project, supported by the OpenInfra Foundation, almost 4 years ago. The project provided a home for projects in areas such as AI, telemetry, and more, and activities that contributed to advance research and collaboration in these areas. OpenInfra Labs was created during challenging times, with a global pandemic unfolding and limiting efficient collaboration around the globe, and this phenomenon made it very hard for the pilot project to reach its full potential. At the same time, newly forming research efforts and organizations started to overtake some of the activities previously performed in OpenInfra Labs. These factors contributed to OpenInfra Labs reaching the end of its lifecycle; remaining community members have been winding down the pilot project, and are now ready for the final step. In line with the above, I'm hereby informing you that OpenInfra Labs is now archived as an OpenInfra pilot project. OpenInfra Foundation staff is working to complete the process, which includes deactivating the project's mailing list while leaving the archives available, making a note on the project's website about the archival, and making sure that other publicly available resources and artifacts of the pilot project will also remain available for future reference. Please read the related segment in the 2023 OpenInfra Foundation Annual Report for further details as it becomes available. -- Jeremy Stanley on behalf of the OpenInfra Labs community

1 0