I totally want to work on this after the 3.0 release. Lets put down some notes on what's needed for most projects. This would help us figure out how to do a base template and what plugins to enable.
* News/release feed
* Project info page
* "Get involved"
* Links to communication channels (IRC, mailing list, bugzilla)
* Screenshot gallery.

I vote

* Screenshot gallery
* Links to communication channels (automatically pulled from doap files...)
* NEWS/release (maybe automatically pulled from NEWS diffs...)

I'd rather all projects looked similar, so if it means enforcing, via a custom plugin, a rather restricted project page then I am in support.

Maybe we could just extend the DOAP format, and those projects with the extra fields in the doap file get an autogenerated project page - but this is quite similar to what olav is doing for the project list.

John: That is what I am planning:
1. Autogenerated index.html
2. Autogenerated $PROJECT/doap.html

DirectoryIndex doap.html index.html

Meaning: All projects shortly listed on index.html. Then detailed information per project, but they can ignore the standard page and do their own thing.

Think someone should draw something up.

Only reason the autoregenerated index.html (not $PROJECT/doap.html; didn't do that yet) isn't setup atm is because we didn't have space on a RHEL6 VM. That was solved yesterday...

(In reply to comment #3)
> John: That is what I am planning:
> 1. Autogenerated index.html
> 2. Autogenerated $PROJECT/doap.html
> 
> DirectoryIndex doap.html index.html
> 
> Meaning: All projects shortly listed on index.html. Then detailed information
> per project, but they can ignore the standard page and do their own thing.
> 
> Think someone should draw something up.
> 
> Only reason the autoregenerated index.html (not $PROJECT/doap.html; didn't do
> that yet) isn't setup atm is because we didn't have space on a RHEL6 VM. That
> was solved yesterday...

Nice!

Any plans for screenshots? That's the really killer feature for me (and visual constancy with the rest of the GNOME website)

How about thisplan for screenshots;
1. List screenshots in doap. Perhaps the screenshots must live in some whitelisted location (l.g.o, people.gnome.org/~maintainer-username)
2. The autogenerate scripts scales the screenshots to be less than an allowed width
3. The screenshots are then shown on/referenced from doap.html

If we go the wordpress route - there is an LDAP plugin for wp that looks quite good

http://wordpress.org/extend/plugins/simple-ldap-login/

It might useful if it is decided to let project maintainers add their own custom homepages on gnome.org

Filed bug 652231 about the ldap plugin

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/Infrastructure/Websites/issues/51.