GCC museum?

[Rich Churcher]

Gerald Pfeifer writes:
 > 
 > It would be great if you could have a close look at those pages linked to
 > under the "Development" heading of our main page, especially contribute.html,
 > cvs.html, cvswrite.html, and checkin.html.
 > 
 >  . Can we compress the information there a bit?

I've had a chance to look over these pages.  Actually, everything
seems solid and well-organised, so any changes will be incremental.

 > 
 >  . Should we add further information?

This is perhaps not the best question for me to answer.  I qualify for 
the "non-expert" point of view, as referenced below :o)  However, I
promise faithfully to add anything others consider relevant into any
patch I submit.  It looks complete to my untrained eyes.

 
 >  . Do we need a couple of further cross-links between these pages?

Maybe.  A link to cvs.html under the Submitting Patches heading in
contribute.html wouldn't hurt.  If you're going to merge the cvs
pages, you don't need much else.


 >  . Should we unify some of these pages? For example, cvs.html and
 >    cvswrite.html?

I think it would be a good idea to merge cvswrite.html and
contribute.html, which cover similar territory.  cvs.html is sort of
different, in that you could have read access purely as a matter of
interest, without needing to know about write access and procedures.


 >  . Is the information there clear for a non-expert?

That's me :o)  I find it easy enough to follow.  One thing I did find
a wee bit excessive was the description of a cvs check-in under
"Example check-in session" in checkin.html.  While this was very useful, I 
suggest providing a separate page and linking to it.  But then, my
preference for web pages is bite-sized pieces rather than lots of
scrolling - YMMV.


 >    Is it easy enough for an expert to find relevant information
 > quickly?

Again, how would I know?  Ok, I'm being obtuse.  Let me put it another 
way - I suspect that experts will already know the logistics, and just 
need a few details.  If you like, I can put those at the top and
further explanations further down on each page.  Is that the kind of
structure that would make sense to a community like GCC?  Or a link at 
the top of the page marked "Essential details", or some such.

A general comment on presentation: I think it would make sense for
these pages to move towards white backgrounds, black text.  Some are,
some aren't, and it looks wierd.  I presume some may have been
automatically generated from .texi, or whatever.  Still - compare
projects.html with cvs.html, for example.

Finally - should I be discussing this on gcc-patches?  Sorry, it's
been awhile...

Cheers,

-- 
Rich
churchmouse@mpx.com.au