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 "Architecture Council/Open Issues"
(New page: Open Issues are Overflow items that have been proposed for a meeting, but that we ran out of time discussing. These items are pushed forward from meeting to meeting until we find time pick...) |
|||
| Line 1: | Line 1: | ||
Open Issues are Overflow items that have been proposed for a meeting, but that we ran out of time discussing. These items are pushed forward from meeting to meeting until we find time picking one up. | Open Issues are Overflow items that have been proposed for a meeting, but that we ran out of time discussing. These items are pushed forward from meeting to meeting until we find time picking one up. | ||
| − | = How to start Releng? = | + | = December 2008 = |
| + | * Martin: [[Architecture Council/F2F ESE 2008]] - thoughts in retrospect | ||
| + | * [https://www.eclipsecon.org/submissions/2009/view_talk.php?id=527 EclipseCon panel] | ||
| + | ** [[Architecture Council/Ask the AC]] ideas for questions to discuss | ||
| + | ** Who wants to participate on the panel, or be a moderator? - Bjorn, zx, Wayne, Mik, Markus, '''Jeff''', '''Ed''' | ||
| + | * [[Architecture Council/F2F EclipseCon 2009]] - Sunday afternoon - sign up and add to the agenda | ||
| + | * {{bug|256448}} API Tooling for extensions / How to treat propertyTester properties in ISV docs (best practice searched) | ||
| + | * {{bug|167144}} "eclipse.common" bundle -- Bundle / Project granularity? | ||
| + | * {{bug|253889}} JIRA vs bugzilla - just close it? | ||
| + | * {{bug|249371}} The new [http://www.eclipse.org Eclipse.org homepage] | ||
| + | * {{bug|249745}} Repository Best Practices (Subversive vs Subclipse); Mercurial, Git Bazaar -- {{bug|257706}} now requesting git specifically | ||
| + | * {{bug|246840}} Jobs and ISchedulingRules - discussion concluded? | ||
| + | * Items to move into IPZilla | ||
| + | ** {{bug|249959}} Copyright Header in checked-in generated artifacts | ||
| + | ** {{bug|246945}} Interfacing with Libs that are not EPL Compatible (mostly LGPL) | ||
| + | |||
| + | * EMO: {{bug|250317}} How to officially communicate Requirements (as per the board, dev process, IP policy...) to the PMCs, Project Leads, Committers? | ||
| + | * '''RC - Roadmap Process''': [[RequirementsCouncilThemesAndPriorities]] - are we happy with it? | ||
| + | * '''PC''' - Richard Gronback: '''New [[Galileo]] Requirements''' from the Planning Council? | ||
| + | ** Must do: Use only Published API by M6 | ||
| + | ** Must do: Provide basic Capability / Activity Definitions by M6 | ||
| + | ** Must do: Use Babel by M6 | ||
| + | |||
| + | = 2008 = | ||
| + | |||
| + | == How to start Releng? == | ||
* [http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg00578.html How to start a releng project for unattended builds] on the ML - PDE build docs are good but only half the story | * [http://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg00578.html How to start a releng project for unattended builds] on the ML - PDE build docs are good but only half the story | ||
** Bjorn, NickB & Denis CBI [[Build Workshop 3: Build Hard With A Purpose]] but is that an answer for now? Current status? | ** Bjorn, NickB & Denis CBI [[Build Workshop 3: Build Hard With A Purpose]] but is that an answer for now? Current status? | ||
| Line 7: | Line 32: | ||
** Refer people to clone existing projects' releng? Which ones are good? | ** Refer people to clone existing projects' releng? Which ones are good? | ||
| − | =Mentoring New Projects= | + | ==Mentoring New Projects== |
| − | + | * What could be improved? | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
** Webpage improvements: more pre-canned content for new projects (like Sourceforge)? | ** Webpage improvements: more pre-canned content for new projects (like Sourceforge)? | ||
| − | + | == Top Ten Recommendations == | |
| − | = Top Ten Recommendations = | + | |
* [[Architecture Council/Top Ten Recommendations]] - should we start sorting them? | * [[Architecture Council/Top Ten Recommendations]] - should we start sorting them? | ||
* [[Architecture Council/Links Collection]] - want more, more, more! | * [[Architecture Council/Links Collection]] - want more, more, more! | ||
| − | = Relationship to [[E4]] = | + | == Relationship to [[E4]] == |
* [[E4/Pervasive Themes]] - Performance, Memory Footprint, [http://borisoneclipse.blogspot.com/2008/10/avoiding-bloat.html Bloat (Boris' Blog)], Concurrency | * [[E4/Pervasive Themes]] - Performance, Memory Footprint, [http://borisoneclipse.blogspot.com/2008/10/avoiding-bloat.html Bloat (Boris' Blog)], Concurrency | ||
* Invite E4 to present to the EAC? | * Invite E4 to present to the EAC? | ||
* [[E4]] now has bi-weekly calls -- won't discuss E4 on the EAC unless asked / invited | * [[E4]] now has bi-weekly calls -- won't discuss E4 on the EAC unless asked / invited | ||
| − | = Concurrency = | + | == Concurrency == |
* Examples: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=245573#c12 bug 245573 comment 12] (Dali JPA Tools Deadlock, John CC'd to EAC); {{bug|246840}} discussion about ISchedulingRule (saving project preferences) | * Examples: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=245573#c12 bug 245573 comment 12] (Dali JPA Tools Deadlock, John CC'd to EAC); {{bug|246840}} discussion about ISchedulingRule (saving project preferences) | ||
* What is causing issues? | * What is causing issues? | ||
| Line 42: | Line 60: | ||
** Articles ? - John referenced the [http://www.eclipse.org/articles/Article-Resource-deltas/resource-deltas.html#1d resource-deltas] article | ** Articles ? - John referenced the [http://www.eclipse.org/articles/Article-Resource-deltas/resource-deltas.html#1d resource-deltas] article | ||
| − | = Eclipse Pain Points = | + | == Eclipse Pain Points == |
* '''Eclipse Pain Points''' | * '''Eclipse Pain Points''' | ||
** Performance & Memory Footprint, Bloat | ** Performance & Memory Footprint, Bloat | ||
| Line 52: | Line 70: | ||
*** Re-activate [[Architecture Council Discovery and Reuse Activity]] ? | *** Re-activate [[Architecture Council Discovery and Reuse Activity]] ? | ||
| − | = Other Ideas for Discussion = | + | == Other Ideas for Discussion == |
* '''Mentoring Galileo''': What could be improved? | * '''Mentoring Galileo''': What could be improved? | ||
** Running each project's unittests with full Galileo installed; especially interesting for Performance tests | ** Running each project's unittests with full Galileo installed; especially interesting for Performance tests | ||
| Line 58: | Line 76: | ||
** '''Integrated bug reporting''': Mylyn is providing a bug/error/enhancement reporting facility that will provide a flexible and product-configurable mapping between features, bundles and bug trackers {{bug|212209}} (Example: http://wiki.eclipse.org/images/8/86/Mylyn-Bug-Reporting-Example.jpg ). Do we want this for Galileo? | ** '''Integrated bug reporting''': Mylyn is providing a bug/error/enhancement reporting facility that will provide a flexible and product-configurable mapping between features, bundles and bug trackers {{bug|212209}} (Example: http://wiki.eclipse.org/images/8/86/Mylyn-Bug-Reporting-Example.jpg ). Do we want this for Galileo? | ||
| − | = | + | = 2007 = |
* '''Coordinated build''' (Ganymede) infrastructure - how to achieve continuous integration, unit tests covering the integration of all projects, and consistency across all projects | * '''Coordinated build''' (Ganymede) infrastructure - how to achieve continuous integration, unit tests covering the integration of all projects, and consistency across all projects | ||
** Early integration tests, [http://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg00808.html Automated JUnit API conformance tests] | ** Early integration tests, [http://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg00808.html Automated JUnit API conformance tests] | ||
Revision as of 13:20, 16 December 2008
Open Issues are Overflow items that have been proposed for a meeting, but that we ran out of time discussing. These items are pushed forward from meeting to meeting until we find time picking one up.
Contents
December 2008
- Martin: Architecture Council/F2F ESE 2008 - thoughts in retrospect
- EclipseCon panel
- Architecture Council/Ask the AC ideas for questions to discuss
- Who wants to participate on the panel, or be a moderator? - Bjorn, zx, Wayne, Mik, Markus, Jeff, Ed
- Architecture Council/F2F EclipseCon 2009 - Sunday afternoon - sign up and add to the agenda
- bug 256448 API Tooling for extensions / How to treat propertyTester properties in ISV docs (best practice searched)
- bug 167144 "eclipse.common" bundle -- Bundle / Project granularity?
- bug 253889 JIRA vs bugzilla - just close it?
- bug 249371 The new Eclipse.org homepage
- bug 249745 Repository Best Practices (Subversive vs Subclipse); Mercurial, Git Bazaar -- bug 257706 now requesting git specifically
- bug 246840 Jobs and ISchedulingRules - discussion concluded?
- Items to move into IPZilla
- bug 249959 Copyright Header in checked-in generated artifacts
- bug 246945 Interfacing with Libs that are not EPL Compatible (mostly LGPL)
- EMO: bug 250317 How to officially communicate Requirements (as per the board, dev process, IP policy...) to the PMCs, Project Leads, Committers?
- RC - Roadmap Process: RequirementsCouncilThemesAndPriorities - are we happy with it?
- PC - Richard Gronback: New Galileo Requirements from the Planning Council?
- Must do: Use only Published API by M6
- Must do: Provide basic Capability / Activity Definitions by M6
- Must do: Use Babel by M6
2008
How to start Releng?
- How to start a releng project for unattended builds on the ML - PDE build docs are good but only half the story
- Bjorn, NickB & Denis CBI Build Workshop 3: Build Hard With A Purpose but is that an answer for now? Current status?
- CBI being adopted by Paul Webster for e4
- Refer people to clone existing projects' releng? Which ones are good?
Mentoring New Projects
- What could be improved?
- Webpage improvements: more pre-canned content for new projects (like Sourceforge)?
Top Ten Recommendations
- Architecture Council/Top Ten Recommendations - should we start sorting them?
- Architecture Council/Links Collection - want more, more, more!
Relationship to E4
- E4/Pervasive Themes - Performance, Memory Footprint, Bloat (Boris' Blog), Concurrency
- Invite E4 to present to the EAC?
- E4 now has bi-weekly calls -- won't discuss E4 on the EAC unless asked / invited
Concurrency
- Examples: bug 245573 comment 12 (Dali JPA Tools Deadlock, John CC'd to EAC); bug 246840 discussion about ISchedulingRule (saving project preferences)
- What is causing issues?
- work performed during class loading (Activator.start()) - unknown context, can run at unpredictable times
- work performed in callbacks - unknown context, avoid synchronous callbacks
- General recommendations: (e.g. avoid synchronous callbacks, avoid in Activator.start(), static initializers or Singleton getters) - a general recommendation could be to avoid performing work at unpredictable times, but that would recommend against lazy initialization in general
- Does anybody have a well-working, consistent model on top of the current infrastructure?
- Totally new concurrency mechanism as part of E4 ?
- David Orme mentions DataBinding Realms and the Threads Considered Harmful blog which references Erlang message-based concurrence
- Would it help to become more asynchronous under the hood, even if old APIs need to remain for compatibility?
- Are there any other good known models for concurrency?
- Better Javadoc ?
- Example: ISchedulingRule.isConflicting() vs. ISchedulingRule.contains(), and how does it relate to RuleFactory and MultiRule?
- Articles ? - John referenced the resource-deltas article
Eclipse Pain Points
- Eclipse Pain Points
- Performance & Memory Footprint, Bloat
- Restrictions on Resource model (Maven)
- IP due diligence and the processes around it
- Lots of these issues are already worked on by E4, and/or Committer Representatives at the Board, and/or the Planning Council
- But the EAC's charter includes identifying and naming pain pionts... anything not yet being addressed?
- Re-activate Top Ten Architectural Problems in all of Eclipse ?
- Re-activate Architecture Council Discovery and Reuse Activity ?
Other Ideas for Discussion
- Mentoring Galileo: What could be improved?
- Running each project's unittests with full Galileo installed; especially interesting for Performance tests
- Don't duplicate work done by the Planning Council
- Integrated bug reporting: Mylyn is providing a bug/error/enhancement reporting facility that will provide a flexible and product-configurable mapping between features, bundles and bug trackers bug 212209 (Example: http://wiki.eclipse.org/images/8/86/Mylyn-Bug-Reporting-Example.jpg ). Do we want this for Galileo?
2007
- Coordinated build (Ganymede) infrastructure - how to achieve continuous integration, unit tests covering the integration of all projects, and consistency across all projects
- Early integration tests, Automated JUnit API conformance tests
- UI Consistency - when I'm not mistaken, the UI Guidelines are being reworked; how can we encourage projects to pick them up.
- Remote Development - Theoretically, EFS should be the foundation on which workspaces can be put on remote machines, and I do see a lot of interest in this -- but practically, there are some roadblocks. It's a pervasive topic since most projects are not really EFS-aware yet. How to improve the situation?
- Scripting, Macro Recording, DOMs - Another pervasive theme, if macro recording & playback is to be supported across an entire Eclipse based product, there need to be guidelines and APIs for projects to follow. It may be a multi-year multi-project effort but it may be worth getting it started.
- Security - With the number of plugins aver growing, is there a threat of trojans nesting themselves inside Eclipse? Getting a trojan or virus-like plugin into Eclipse can be extremely malicious - from spying to impersonation up to data destruction. Is it a real threat, and is there something that could / should be done?
- Project Model and Nested Projects - when developers lay out the directory structure on non-eclipse projects, they often use a tree where some directories represent projects. Those projects are "nested". This is also often related to the way the files are stored in a configuration management system. Unfortunately eclipse does not really support this real-world setup bug 35973, and this Blog by Alex Blewitt
- Integrated bug reporting: Mylyn is providing a bug/error/enhancement reporting facility that will provide a flexible and product-configurable mapping between features, bundles and bug trackers bug 212209. Once done it would be good to discuss how best for EPP and other products to consume this (Example: http://wiki.eclipse.org/images/8/86/Mylyn-Bug-Reporting-Example.jpg )
- Package visibility policies: New WTP Policy and bug 202711