Jonathan Locke wrote:
what about burying it all on a separate page linked to by some kind of "Team" link?
most people using wicket don't care about any of the dev stuff anyway... they just
want to get rocking and rolling.
This is what I want to do with the daily build reports. Mere normal men don't want to be bothered by this kind of stuff, like checkstyle reports, etc.
However, personally I tend to take a peek at the XYZ development section (of product XYZ) in case I want either to contribute, or to see how the quality of the product is: are there unit tests, do they run, how's the coverage, etc. For a release this is essential IMO. Since we are a rather anonymous group of developers, you don't have my blue eyes to believe in (pardon my poor english translation of a dutch saying), so you need some comforting.
So I see the dev menu as follows:
Developing Wicket (or any other non-misguiding label)
--------------------
o Developers
o CVS access
o Contributing
o Building Wicket (how to build wicket)
o Releasing Wicket (new document laying out the procedure to release Wicket)
o Code conventions?
o etc.
o Cruisecontrol -> takes you to the latest cruisecontrol generated site with more build reports than the home site
o Build reports -> the reports created when performing the release, but could be removed if there's a 75% majority ;-)
Not very minimalistic, I presume >-)
Martijn
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Wicket-develop mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
