[jira] Commented: (INFRA-391) Create a web application for creating and editing ~/.forward files

["Leo Simons (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/jira/browse/INFRA-391?page=comments#action_12329526 ] 

Leo Simons commented on INFRA-391:
----------------------------------

Jochen, you don't need permission to do anything! This is Apache! Please charge forward and build stuff!

When I said "integrate" I didn't mean that it *had* to be python, just that it'd be great to have something we can hook into it so the user experience is consistent. Sorry I wasn't very clear about that. Anyway, that shouldn't be impossible at all. For example, it should be easy call a commandline perl script from there, or to link back and forth to it from the output of a completely seperate CGI script, or call a perl CGI script from python and inline the results.

It's a shame that the apworkflow code isn't easy enough to understand, but that's valuable feedback for me too. Do you have some specific things that made you scratch your head?

My goals here are not to build something "pure" but to build something that's easy to use and easy to extend. Easy to extend means that developing in perl should be an option if you ask me.

As for suid, we're pretty paranoid about that. I think in the end we would want a little C program which updates the .htaccess file content (like we have for svnpasswd, which IIRC is at

  https://svn.apache.org/repos/asf/infrastructure/trunk/tools

). If you build your script with that in mind I'm sure we can get some security expert to write the setuid program.

> Create a web application for creating and editing ~/.forward files
> ------------------------------------------------------------------
>
>          Key: INFRA-391
>          URL: http://issues.apache.org/jira/browse/INFRA-391
>      Project: Infrastructure
>         Type: New Feature
>   Components: apworkflow
>     Reporter: Leo Simons
>     Priority: Minor

>
> We need a simple yet secure web application that allows our committers to log in using their SVN id and password that can be used to create or update their .forward file. Currently these files live on people.apache.org, but the webapp should be flexible to moving them around.
> Additionally, the info from the .forward files may end up in LDAP at some point, so the web application should be built with that in mind.
> This issue is related to the asf-workflow project in development as part of the google Summer of Code (http://wiki.apache.org/general/SummerOfCode2005), and may be tackled as part of that project.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira