www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Ruby (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (INFRA-4877) Form for creating a new Git repository
Date Fri, 08 Jun 2012 19:09:23 GMT

     [ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sam Ruby reassigned INFRA-4877:
-------------------------------

    Assignee: Sam Ruby
    
> Form for creating a new Git repository
> --------------------------------------
>
>                 Key: INFRA-4877
>                 URL: https://issues.apache.org/jira/browse/INFRA-4877
>             Project: Infrastructure
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Jukka Zitting
>            Assignee: Sam Ruby
>
> As a followup to INFRA-4470, we indeed need a web form or some other easy-to-use tool
for creating new Git repositories.
> The form should take (at least) the following inputs:
> * Name of the repository ("couchdb", "tapestry-5", "incubator-cordova-android", etc.)
> * Description of the repository ("Apache CouchDB", "Apache Tapestry 5", etc.)
> * Address of a relevant commit mailing list ("commits@couchdb.apache.org", etc.)
> The repository name should follow the "$tlp(-$podling)(-$name)" pattern as seen on https://git-wip-us.apache.org/repos/asf
with the $podling and $name bits being optional. It would be nice if a similar mechanism as
on the account request form was used to fill in the $tlp and (if "incubator") $podling parts
of the name.
> Based on this information the form should create a a new empty repository under https://git-wip-us.apache.org/repos/asf.
The project can then take care of pushing any existing history from a git-svn mirror or some
other source to the new repository.
> It would be nice if the form was available to all (P)PMC members of the relevant project,
though even keeping it restricted to just the Git admins should be fine for now.
> PS. There should be a mechanism to prevent something like a CSRF attack from using such
a form.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message