| Summary: | Statistics on the Project management Site looks odd | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Michael Jaeger <mcj> | ||||
| Component: | Project Management & Portal | Assignee: | Eclipse Web <webdev> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | lars.geyer-blaumeiser, wayne.beaton, webmaster | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Michael Jaeger
The existing implementation (which you've correctly interpreted includes the activity of the subproject) conforms to the original requirements. Unfortunately, if we change this, I will get requests to change it back; this is an example of how it is impossible to please everybody. I'll grant that many of the semantics around subprojects are just plain weird. It's not clear to me that Eclipse sw360 and an Eclipse SW360 Antenna benefit from the subproject relationship; perhaps the right solution is to make Antenna a direct Technology subproject. If you feel strongly about this, my recommendation is that you ask the project leads to consider this. Note that breaking the subproject relationship is primarily organizational and should have no impact on project resources or committers. We (Lars and I) are ambivalent and leave it for now. Having both being visible at the same time is a good thing. Thanks for your answer. Kind regards, Michael |