The thought that we're doing all this stuff in .htaccess files makes me die a little inside.
Yes, I suppose we could do this. But we still need to add it to the sitenav as well or we're still just counting on people to magically know. On Jun 21, 2017 21:24, "Owen O'Malley" <owen.omal...@gmail.com> wrote: > Ok, I made the change to ORC's site as a demo. > > http://orc.apache.org/bugs > http://orc.apache.org/downloads > http://orc.apache.org/releases > http://orc.apache.org/src > http://orc.apache.org/web-src > > All redirect to the appropriate urls. The patch is > https://github.com/apache/orc/commit/96a4ea96896d6bfbe5c372820228f4 > b48aa9f055 > . > > .. Owen > > > > On Wed, Jun 21, 2017 at 12:06 PM, Owen O'Malley <owen.omal...@gmail.com> > wrote: > > > 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 <a...@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 <rbo...@rcbowen.com> > >> wrote: > >> >>> FYI: > >> >>> https://docs.google.com/spreadsheets/d/1BxQzPVnzyAUD8NpCNB1M > >> IwvlglU1G5lTXAvYGzkSlP0/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-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> > >> > > >
