community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rich Bowen <>
Subject Re: Where's the code?
Date Wed, 21 Jun 2017 17:19:53 GMT

On 06/21/2017 05:29 PM, Sam Ruby wrote:
> On Wed, Jun 21, 2017 at 10:43 AM, Rich Bowen <> wrote:
>> FYI:
>> if you want to play along.
> Is there any way that this can be integrated into
> ?
> Advantages: individual projects can do self discovery, and the list
> would be updated automatically.
> What we would need is some sort of rules as to what you are expecting
> to see for every site.

That would be awesome. I presume that what we'd want to do is start with
the phrase "Source Repositories" and then add more as we discover them.
Sites that lack them at present, we'd just add "Source Repositories" and
they'd match.

That would also make tracking easier going forward, rather than having
to continually update the spreadsheet.

So, what we're looking for, at the moment (feel free to add more columns
to the spreadsheet while we're brainstorming) is:

* A link to a page which describes how to get the source code. This is
hard to auto-detect as it's going to be named something different
everywhere. Ideas?

* Something labeled "Download" (or similar) on the front page of the site

* A link to some kind of release notes for the latest release

* A link to one of our issue trackers. This should be easy if they're
using ASF issue trackers.

* A link to a page that lists their mailing lists, and describes their
purposes. I presume that such a page is likely to match
/mail(ing)?-?lists?/ or something similar?

Rich Bowen - - @rbowen - @apachecon

View raw message