| Summary: | use data driven websites for sub-projects | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> |
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | mik.kersten |
| Version: | unspecified | ||
| Target Milestone: | 3.9 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 347548 | ||
|
Description
Steffen Pingel
So are you thinking that we make one slick top-level portal page and then any project that does not have a custom page gets the data-driven page? Sound good to me. Yes, exactly. For projects that don't require their own website since all information is available from the parent project or other sources (e.g. Wiki) could use the data driven page. Sounds great. I have added the required re-directs for all sub-project websites: http://eclipse.org/mylyn/builds/ http://eclipse.org/mylyn/commons/ http://eclipse.org/mylyn/context/ http://eclipse.org/mylyn/docs/ http://eclipse.org/mylyn/incubator/ http://eclipse.org/mylyn/tasks/ http://eclipse.org/mylyn/versions/ |