community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shane Curcuru <>
Subject Re: Where's the code?
Date Wed, 21 Jun 2017 15:35:42 GMT
Sweet!  I definitely agree that adding a link to the *website* sources
is important too - that's a key way to make it simple for newcomers to
submit documentation updates.

Is there any interest in coming up with a list of suggested titles for
these links?  Having some consistency - where it makes sense - in how
projects expose this data on their homepages would be nice for many
users.  As Rich notes: not policy, just a few suggestions for wording
for these links.

Separately, if we do have any similar text for these links or even
rel="source" flags on the links, we could consider scanning these as an
additional Whimsy best practices checker like the required policy links
works (but obviously a separate URL):

- Shane

Rich Bowen wrote on 6/21/17 10:43 AM:
> FYI:
> if you want to play along.
> On 06/21/2017 10:57 AM, Rich Bowen 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
>> 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?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message