One of the "low hanging fruit" that I believe would increase contributions to our projects is telling people where the code is. It's astonishingly hard to find out, for most of our projects.
For the example of how to do it, see https://commons.apache.org/ Note that in the navigation, it says SOURCE REPOSITORIES. The first link there - "General Information" - tells you exactly how to get the code, as well as providing links to browse the code. This should be part of the site nav for every project. This isn't mandated by our site policy, nor should it be, IMHO. I have no desire to create policy here. What I do want to do, however, is organize an effort to go through every one of our projects, find the relevant code locations, and submit patches to these projects to provide this information on their websites. Obviously, I should start with my own project. Finding the code for httpd is possible, but not obvious. I'll go fix that. After that, I'm going to start tracking this information in a doc somewhere as I work through the other projects. Anyone interested in working on a cross-project effort like this with me? -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
signature.asc
Description: OpenPGP digital signature
