Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse/PMC"
< Eclipse
(→Archive) |
(→Meeting Minutes) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
= Meeting Minutes = | = Meeting Minutes = | ||
| + | |||
| + | March 30, 2022 - Alex, Tom, Lars | ||
| + | * Discussion about simplification of the Github repo structure | ||
| + | * Currently no plan to provide a Github for user to report issues, we rather | ||
| + | * For pull request there should no need to open a bug report / GH issue, all present PMC members agreed, to be discussed next week with Jay and MQ. | ||
| + | |||
| + | February 16, 2022 - Alex, Tom, Jay, Lars, McQ | ||
| + | * IP log done for 2022-03, process might be removed by the foundation in the future | ||
| + | * Auto-closed policy can now be decided by project, project committer can vote on it | ||
| + | * Support of additional architecture LoongArch and FreeBSD was discussed, for now we expect the builds outside of Eclipse.org for these architures | ||
| + | ** building Eclipse might get easier with planned enhancements in Tycho | ||
| + | * Bug reports from Bugzilla are not planned to be moved to Github, will continue to exist in Bugzilla | ||
| + | |||
| + | |||
| + | '''January 19, 2022''' - Alex, Tom, Jay, Lars, McQ | ||
| + | * Eclipse aggregator build is currently migrated to Github | ||
| + | * Github migration work of the aggregator is documented in https://bugs.eclipse.org/bugs/show_bug.cgi?id=577323 | ||
| + | * The most important PGP work items are done with the help of Ed Merks, some secondary issues are still missing, e.g. such features are shown as unsigned | ||
| + | * JFR Event are discussed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=578055, PMC members should check so that we can discuss it next week | ||
'''January 12, 2022''' - Alex, Tom, Jay, McQ | '''January 12, 2022''' - Alex, Tom, Jay, McQ | ||
Revision as of 11:07, 30 March 2022
Documents
Some documents written and/or used by the PMC:
Meeting Schedule
The Eclipse Project PMC has a weekly phone meeting every Tuesday at 11.00am EST.
Meeting Minutes
March 30, 2022 - Alex, Tom, Lars
- Discussion about simplification of the Github repo structure
- Currently no plan to provide a Github for user to report issues, we rather
- For pull request there should no need to open a bug report / GH issue, all present PMC members agreed, to be discussed next week with Jay and MQ.
February 16, 2022 - Alex, Tom, Jay, Lars, McQ
- IP log done for 2022-03, process might be removed by the foundation in the future
- Auto-closed policy can now be decided by project, project committer can vote on it
- Support of additional architecture LoongArch and FreeBSD was discussed, for now we expect the builds outside of Eclipse.org for these architures
- building Eclipse might get easier with planned enhancements in Tycho
- Bug reports from Bugzilla are not planned to be moved to Github, will continue to exist in Bugzilla
January 19, 2022 - Alex, Tom, Jay, Lars, McQ
- Eclipse aggregator build is currently migrated to Github
- Github migration work of the aggregator is documented in https://bugs.eclipse.org/bugs/show_bug.cgi?id=577323
- The most important PGP work items are done with the help of Ed Merks, some secondary issues are still missing, e.g. such features are shown as unsigned
- JFR Event are discussed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=578055, PMC members should check so that we can discuss it next week
January 12, 2022 - Alex, Tom, Jay, McQ
- Move to PGP signed content news to IDE WG and Planning Council
- Well received so far
- 2022-03 to has the implementation, 2022-06 to do full switch
- we use PGP for content not delivered to Simrel
- Ed helps with implementation/bug fixes
- only concern is critical CVE - that would require either help or PGP signed content being pushed to 2022-03
- To be further discussed if such an issue happens
- ECF relation
- Project is heavily under resourced
- No one knows good reason to still be using Apache Httpclient, Java HttpClient is not tried out and the previous JVM Http code had severe limitations
- Development falling out on Platform releng for updates to Apache Httpclient, Windows proxy support and etc. is a no-go
- Possible plan
- Create Java Httpclient based connector for ECF or enhance the current default one to use Httpclient and not Httpconnection - removes need to update Apache Httpclient dependency, take care of windows specific bundles with JNA dependency and so on
- If previous doesn't uncover limitation in Java's Httpclient stop shipping Apache Httpclient connector
- Assuming 2 previous complete - look if it makes sense to not have ECF as a dependency at all to skip one cyclic dependency
Archive
- Archive of Meeting Minutes from 2021
- Archive of Meeting Minutes from 2020
- Archive of Meeting Minutes from 2019
- Archive of Meeting Minutes from 2018
- Archive of Meeting Minutes from 2017
- Archive of Meeting Minutes from 2016
- Archive of Meeting Minutes from 2015
- Archive of Meeting Minutes from 2014
- Archive of Meeting Minutes from 2013
- Archive of Meeting Minutes from 2012
- Archive of Meeting Minutes from 2011
- Archive of Meeting Minutes from 2010
- Archive of Meeting Minutes from 2009