Bug 308117 - "About this project" link
Summary: "About this project" link
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Process (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Management Organization CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-05 16:36 EDT by Chris Aniszczyk CLA
Modified: 2011-10-24 15:48 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Aniszczyk CLA 2010-04-05 16:36:29 EDT
After moving to the new fancy template... we got this ping from the Foundation.

> Matthias, Shawn,
> Projects are required to keep meta data up to date using the MyFoundation
> Portal (http://portal.eclipse.org/).  The following problems were found
> with this project's meta-data:
>
> * Project home page (projecturl = http://www.eclipse.org/egit/) does not
> have an "About <project>","About This Project" or "Information about
> <project>" link. Projects are required to provide that standard link on
> their home page (see
> http://www.eclipse.org/projects/standard-link-on-home-page.php) .

Is this really required? If so, anyone using the new template is violating this and it should be included in the new template so people don't violate it.

Or is this just too much process?
Comment 1 Denis Roy CLA 2010-04-05 17:05:51 EDT
I think the new template does a better job of guiding committers in the right direction (with regards to what content they should put on the home page, and how to lay it all out) than a bunch of meta-data checks.  "About us" is clearly defined in the first paragraph of your page.
Comment 2 Wayne Beaton CLA 2011-10-24 15:48:39 EDT
The template does include an "About This Project" link. I don't like the current template because I think it's a little too complex for projects just starting out; but that's not the focus of this bug. I've opened Bug 361859 for that discussion.

Since I believe that the original issue has been addressed, I'm marking as FIXED.