[ 
https://issues.apache.org/jira/browse/WHIMSY-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902974#comment-14902974
 ] 

Sam Ruby commented on WHIMSY-15:
--------------------------------

bq. It looks like http://www.apache.org/index.html is now derived from 
https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/index.html 
rather than from 
https://svn.apache.org/repos/asf/infrastructure/site/trunk/templates/index.html

Thanks!  I've committed (but not yet deployed) the change.

bq. [It really would be easier if there were a single location that projects 
could update ...]

That's actually my goal, that I've been prototyping with tools for Craig.  The 
basic idea to replace the existing http://whimsy.apache.org/roster tool with 
one that is both read/write.  See something you don't like?  Double click on it 
and that part of the page is replaced with a form that you can use to update 
that data.  When done, the necessary svn and/or LDAP updates will be made for 
you.  Among other things, this will eliminate the need to ssh to 
people.apache.org and run perl scripts to update LDAP.

First step is to rewrite the roster tool to use a number of things I learned in 
the latest iteration of the board agenda tool.  

> Board meeting minutes - names of pages no longer agree with PMC name
> --------------------------------------------------------------------
>
>                 Key: WHIMSY-15
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-15
>             Project: Whimsy
>          Issue Type: Bug
>         Environment: https://whimsy.apache.org/board/minutes/
>            Reporter: Sebb
>            Assignee: Sam Ruby
>
> Since two PMCs were named, the pages for the minutes for APR and Logging 
> Services are no longer easily derivable.
> Ideally apps such as projects.a.o should be able to determine the URL without 
> needing to do any special processing.
> Logging.tml could easily be renamed and/or aliased to Logging_Services.html.
> Not sure it's possible (or a good idea) to include (APR) in the Portable 
> Runtime URL. So that may need additional processing.
> Or one could use the committee id such as apr/logging/httpd.
> If so, it might make sense to provide redirects for the current pages.
> For the time being, I have added a special check for APR/Logging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to