Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
MIME-Version: 1.0
In-Reply-To: <44e4a396-8342-2974-27b0-ef9484185126@shanecurcuru.org>
References: <084abe18-ea3e-233a-39fb-83a2442830e5@rcbowen.com>
 <b7f58747-aca9-cd52-e4d0-d50e664e6649@rcbowen.com> <CAFG6u8Eh-yd4BKAM=eVaC4UaTQQKmFQEknt5P3Y9KWUAn-A9Yw@mail.gmail.com>
 <fd32e113-bdbe-7790-0ad3-e3c7cc41447c@rcbowen.com> <44e4a396-8342-2974-27b0-ef9484185126@shanecurcuru.org>
From: "Owen O'Malley" <owen.omalley@gmail.com>
Date: Wed, 21 Jun 2017 12:06:10 -0700
Message-ID: <CAHfHakHh5ovPB8XFzH7GC+K_E8QA9AmJaYPihoTWKCHqW6fCZw@mail.gmail.com>
Subject: Re: Where's the code?
To: dev@community.apache.org
Content-Type: multipart/alternative; boundary="001a113cf0feb1d23c05527d0f2d"
archived-at: Wed, 21 Jun 2017 19:06:23 -0000

--001a113cf0feb1d23c05527d0f2d
Content-Type: text/plain; charset="UTF-8"

Actually, I'd go the other way. It would be good if projects would set up a
standard set of redirects at the top level of the project.

foo.apache.org/bugs -> Bug database (eg. jira instance)
/src -> User browsable source repository (eg. github mirror)
/downloads -> Download page
/release -> Release notes for the current release
/web-src -> User browsable site source

On ORC, I did the equivalent, but I picked names using company trademarks,
which is sub-optimal:

http://orc.apache.org/jira -> https://issues.apache.org/jira/browse/orc
http://orc.apache.org/github -> https://github.com/apache/orc

.. Owen


On Wed, Jun 21, 2017 at 11:12 AM, Shane Curcuru <asf@shanecurcuru.org>
wrote:

> Rich Bowen wrote on 6/21/17 1:19 PM:
> >
> >
> > On 06/21/2017 05:29 PM, Sam Ruby wrote:
> >> On Wed, Jun 21, 2017 at 10:43 AM, Rich Bowen <rbowen@rcbowen.com>
> wrote:
> >>> FYI:
> >>> https://docs.google.com/spreadsheets/d/1BxQzPVnzyAUD8NpCNB1MIwvlglU1G
> 5lTXAvYGzkSlP0/edit#gid=0
> >>> if you want to play along.
> >> Is there any way that this can be integrated into
> >> https://whimsy.apache.org/site/ ?
> >>
> >> 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.
>
> If we're doing something new, why not use rel="" values?
>
> https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types
>
> We could even abuse the rel= attribute to add some of our own keys if we
> really wanted to.  This would make link checking super-easy for sites
> that use it.
>
>
> --
>
> - Shane
>   https://www.apache.org/foundation/marks/resources
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>
>

--001a113cf0feb1d23c05527d0f2d--