I find this a particularly good example of presenting developer related information: http://www.mediawiki.org/wiki/Developer_hub
On Monday, 18 May 2015 21:17:47 UTC+1, figaro wrote: > > I wanted to gather some feedback as to how to reorganise the Roadmap type > wiki pages on trac.edgewall.org. These are the pages that profess to > collect information on the future direction of Trac: > http://trac.edgewall.org/wiki/TracDev > http://trac.edgewall.org/wiki/TracDev/ToDo > http://trac.edgewall.org/wiki/SeaChange > http://trac.edgewall.org/wiki/TracIdeas > > However, each of these pages convey more or less the same information, are > not particularly inviting for new contributors because of their link-farm > nature and reflect the state of the program when there were more core > developers actively involved. > > I therefore like to propose that these pages are treated as follows: > - start with a fresh page called TracDev, that has the core information > copied from each of the pages above and fits on roughly two pages > - the focus will be on narrative supported by stats, as opposed to the > other way around > - archive pages that have their information copied elsewhere > - information that is rationalised should be turned into tickets, if they > aren't already > - there should still be a place to reach each of the underlying links, so > the same rules apply (rationalise where possible, else mark as archived) > and still have a coherent whole > > I like to hear any suggestions you may have. > -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
