| Summary: | Remove "Requirements Council" from Councils page | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> | ||||
| Component: | Website | Assignee: | phoenix.ui <phoenix.ui-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | mike.milinkovich | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| URL: | http://eclipse.org/org/foundation/council.php | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Wayne Beaton
No... not Architecture Council. Website... Grrr... Reassigning. There is some content on the page that should be moved. e.g. meeting minutes. I believe that we can just leave the documents where they are and provide links on the wiki page [1]. We should also update the wiki page to indicate that the requirements concil is defunct. Should we include any comment about the requirement council on the Councils page? [1] http://wiki.eclipse.org/Requirements_Council I have deleted all the requirements council entries in the foundation database. The links to the meeting minutes have been moved to the wiki (the PDF documents remain in their original location); I also added a notice to the top of the wiki page to indicate that the requirements council is now defunct. The councils page has been updated to exclude the requirements council. While I was at it, I updated the page to use the $App->foundation_sql method instead of managing the database connection directly. I also did some minor cosmetic work on the mentored project lists under the architecture council members (I added a little padding on the left to make it a little less visually cluttered). I probably should have opened a new bug :-( Committed. Marking as FIXED. Created attachment 204515 [details]
mylyn/context/zip
|