CFV: Dissolve the Portola Project
Mikael Vidstedt
mikael.vidstedt at oracle.com
Tue May 7 23:49:03 UTC 2024
The CFV on “Dissolve the Portola Project”[1] has now concluded.
Valid votes cast by Project Members per the census [2] are:
Yes: 6
No: 0
Veto: 0
According to the Bylaws definition of Lazy Consensus [3], this is sufficient to dissolve the project.
The project resources such as project web page [4] and email list [5] will be deleted/archived/made read-only as appropriate, and the project removed from the OpenJDK census [2]. The source code repository [6] was already archived last month because of the lack of activity.
[1] https://mail.openjdk.org/pipermail/portola-dev/2024-April/000569.html
[2] https://openjdk.org/census#portola
[3] https://openjdk.org/bylaws#lazy-consensus
[4] https://openjdk.org/projects/portola
[5] https://mail.openjdk.org/pipermail/portola-dev
[6] http://git.openjdk.org/portola
Cheers,
Mikael
On Apr 15, 2024, at 1:40 PM, Mikael Vidstedt <mikael.vidstedt at oracle.com> wrote:
According to section 6 of the bylaws [1], the Committers of a Project may decide, by Lazy Consensus, to request that a Project should be dissolved. When a Project is dissolved its materials are archived. A dissolved Project may be re-created by being re-proposed.
The work that was done in this Project has been integrated into the mainline JDK project, and this mailing list has been inactive since March 2022.
I therefore propose that the Portola Project [2] should be dissolved.
Votes are due by 2pm PT, April 29th 2024
Only current Portola Project Committers [3] are eligible to vote.
Votes must be cast in the open by replying to this mailing list.
Cheers,
Mikael
[1] https://openjdk.org/bylaws#_6
[2] https://openjdk.org/projects/portola/
[3] https://openjdk.org/census#portola
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/portola-dev/attachments/20240507/cccf475b/attachment.htm>
More information about the portola-dev
mailing list