| Re: [oniro-pmc] Oniro Alpha Release: basic information from EF |
Hello, On Friday, 3 June 2022 14:09:32 CEST Stefan Schmidt wrote: > Hello Agustin. > > Two points stick out here I want to discuss further. > > 1) " We would welcome a code freeze and starting the Release process for > Oniro Alpha as soon as possible." What kind of code freeze do you expect to > happen here? We are still heavy in development and are surely not freezing > everything and sitting on our hands waiting on IP check. What I proposed in > the call this week was that we do git tags for alpha which are a clear base > for any checking that need to be done (release review, IP, etc) Git tags should be enough. > > 2) "Considering that we need to release under the new IP Policy, the > tentative Oniro Alpha release day is July 28th." Why do we need to release > under the new IP policy? Who decided that? I find it rather unpleasant > that we are forced to wait 2 months to move forward while EF sort out a new > policy to come in place. Are other project also unable to do releases in > this time-frame? Even if this is supposed to be only a onetime thing this > still has potential to jeopardize the Oniro Goofy roadmap we planned for > 2022. The rationale is explained in this talk: * Video: https://www.youtube.com/watch?v=kbzV-z0lr68 * Slides: attached Slide 4 bullet point 3 (min 6:50) and slide 5 bullet point 1 (min 8) are essential for us to release in a reasonable time frame. Basically, the new process reduces the need to track dependencies on third party content (most of our content) and the need to get EF Board approval for additional third party content licenses. The gap between the licenses of the 3rd party content we consume and distribute vs the current approved licenses at EF[1] (including those in our Oniro TLP charter[2]) is very big. The approval process at Board level involves many guarantees and the Board meeting cadence and agenda does not play in our favour. Please check also the slide 7 where we anticipated the timeline. Quite frankly, I did not recalled back then the discrepancy between our intention to release in June and the IP Policy approval timeline. I did just yesterday. It is also true that, at EF, we have been working on topics directly affecting our release for months, partly as a result of the challenges we face with Oniro in the IP front, including modernising our tooling, increasing capacity for license compliance related tasks... The posted presentation correspond to April 2022. Not sure if you were involved but the week before I scheduled a specific session about this with our Oniro IP team but we had to cancel because Wayne, the speaker, got sick. I provided the info about this presentation is short notice a few days later. Not sure how many of the Oniro contributors attended. > Also, when you say 28th of July, would that be the date where we can > make the release official or would that be the date where we could submit > it to the EF IP to find time and check it all. Which would easily take a > few more weeks if it is not based on the work done already. The date where we can make the release official. The work to get to that point would be done in advance. > > Another thing that is also still unclear to mm (maybe Alberto has more > insight) is how the new IP policy EF rolls out will play with the IP > compliance toolchain and process we have in place already? Is there any > alignment going on? > > Regards > Stefan Schmidt > > > -----Original Message----- > > From: Agustín Benito Bethencourt [mailto:agustin.benito@eclipse- > > foundation.org] > > Sent: Friday, June 3, 2022 1:26 PM > > To: Pavel Zhukov <pavel.zhukov@xxxxxxxxxx> > > Cc: Stefan Schmidt <stefan.schmidt@xxxxxxxxxx>; oniro-pmc@xxxxxxxxxxx; > > Pawel Stankiewicz <pawel.stankiewicz@xxxxxxxxxx>; > > sebastien.heurtematte@xxxxxxxxxxxxxxxxxxxxxx; Alberto Pianon > > <pianon@xxxxxxxx> > > Subject: Oniro Alpha Release: basic information from EF > > > > Hello Pavel, > > > > this mail contains relevant information about how to release at EF and > > about the timeline for Oniro Alpha release. > > > > ## Links and references > > > > During the last Oniro IT meeting I mentioned that I would bring basic > > information about Releases at EF as well as an update about how things are > > going at Eclipse Foundation that might affect our release. > > > > The first step would be to learn about EF default release process. Please > > read the following information: > > * Development Process: Project lifecycle: Release Review: https:// > > www.eclipse.org/projects/dev_process/#6_2_Project_Lifecycle > > * EF Release Reviews: https://www.eclipse.org/projects/tools/reviews.php > > * Development Process: Release: > > https://www.eclipse.org/projects/dev_process/ > > #6_4_Releases > > * Project Handbook: Release: https://www.eclipse.org/projects/handbook/ > > #release > > * Project Handbook:Project Management Infrastructure: > > https://www.eclipse.org/ projects/handbook/#pmi > > > > * Releases and Reviews: > > https://www.eclipse.org/projects/handbook/#pmi-releases > > > > * Simultaneous Releases: > > https://www.eclipse.org/projects/handbook/#pmi-joining-a-simultaneous-> > release > > * Project Handbook:Project Checklist: https://www.eclipse.org/projects/ > > handbook/#checklist > > > > Other interesting links > > > > I would also check the Glossary. Learning about the terminology we use > > makes communication easy. > > * Project Handbook:Glossary: https://www.eclipse.org/projects/handbook/ > > #glossary > > > > Licenses: > > * 3rd Party Licenses: https://www.eclipse.org/legal/licenses.php > > > > ## Other relevant points to consider > > > > My main goal is to try to provide the highest level possible or certainty > > to developers and the project in general, considering that this is the > > first time EF will release an operating system (family) and that this is > > the first time for most developers that they release under EF. > > > > Both, the Oniro project and EF have been adapting and introducing changes > > in different areas, not just to come to this point and be efficient but to > > work on a more continuous basis in the coming months to avoid risks in > > the Oniro Platform v2.0 release. > > > > ### New IP Policy > > > > New relevant changes have been introduced by the EF IP Team in the EF IP > > Policy. Such changes will require EF Board approval. The vote is scheduled > > already for June 28. The (potentially) approved policy will come into > > effect thirty days later (July 28). > > > > The changes introduced in IP Policy will have a highly positive effect in > > the coming Oniro releases compared of releasing with the current policy. > > This means that July 28 is the earliest date that we can apply the new > > policy, so is the earliest date that Oniro can release under that policy. > > > > Subsequent releases will not experience this constrain. > > > > ## License reviews > > > > We would welcome a code freeze and starting the Release process for Oniro > > Alpha as soon as possible. In any case, EF is already working on the Oniro > > licenses review. We are expecting an initial output of this effort on week > > 24, maybe earlier. > > > > ## Release Timeline > > > > Considering that we need to release under the new IP Policy, the tentative > > Oniro Alpha release day is July 28th. > > > > The license review effort is expected to be done on time for that day. We > > will have more certainty once we have the output of the preliminary > > license review. > > We are optimistic. > > > > I suggest to start with the Release process as soon as is technically > > possible. At EF, we'll do the necessary leg work in advance to avoid any > > further delay from the proposed date. > > > > ## Meeting > > > > I suggest to have dedicated regular sessions to coordinate the release > > among the different parties involved: > > * Oniro Release Manager > > * Project Committers and PMC > > * Oniro Platform Release Roadmap Team (RR Team) > > * Oniro Marketing > > * EF Release Management (Sebastien) and Oniro IT team. > > * Any other? > > > > I put a couple of options on the table: > > * Thursdays from 10 to 10:45 CEST > > * Thursdays from 16:15 to 17:00 CEST > > > > During the first session we can decide how we are going to publish the > > timeline of the Oniro releases as well as the ToC of the required Release > > Plan, including the Release checklist we mentioned during the meeting you > > were present on Tuesday. > > > > Let's not forget that the RR Team has some attributions related with the > > Roadmap that will influence the discussions. But since such team is not > > operational yet, we will need to do our best to promote alignment. > > > > Best Regards > > -- > > Agustin Benito Bethencourt > > Oniro Program Manager | Eclipse Foundation Eclipse Foundation: The > > Community for Open Innovation and Collaboration [1] https://www.eclipse.org/legal/licenses.php [2] https://projects.eclipse.org/projects/oniro/charter Best Regards -- Agustin Benito Bethencourt Oniro Program Manager | Eclipse Foundation Eclipse Foundation: The Community for Open Innovation and Collaboration
Attachment:
2022.04 IP-Due-Diligence-Overhaul.pdf
Description: Adobe PDF document