On 21 June 2017 at 09:57, Rich Bowen <rbo...@rcbowen.com> wrote: > 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.
Other items that can be difficult to find: - download page for (source) releases (yes, really, some sites make it difficult even though that is the primary purpose of the ASF) - release notes for recent release so one can find out what changed - link to issue tracker, mailing lists > Anyone interested in working on a cross-project effort like this with me? > > -- > Rich Bowen - rbo...@rcbowen.com - @rbowen > http://apachecon.com/ - @apachecon > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
