You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2012/06/03 10:05:22 UTC
[jira] [Created] (INFRA-4877) Form for creating a new Git
repository
Jukka Zitting created INFRA-4877:
------------------------------------
Summary: 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
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 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
Re: [jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Jukka Zitting (JIRA) wrote on Fri, Jun 08, 2012 at 22:46:23 +0000:
> > Ideally, who should be able to request a first git repository for the httpd PMC?
>
> A git admin from infra.
>
I'd allow any httpd PMC member to do this. (Yes in svn.a.o/repos/asf
you can't do that, but _that_ could be changed via the mythical
'[asf:/] @committers=rw' authz file setting)
[jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443426#comment-13443426 ]
#asfinfra IRC Bot commented on INFRA-4877:
------------------------------------------
<danielsh> Sam, if you're not working on this can you unassign please?
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by "Sam Ruby (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292329#comment-13292329 ]
Sam Ruby commented on INFRA-4877:
---------------------------------
> gitadmins group as defined in conf/auth.cfg inside asfgit-admin.git
Before this is complete, I'll need to be able to automate pull requests from that, but I've been assured that that will be doable.
> Currently only in http://incubator.apache.org/projects/
Those files vary in format a lot. Initially I would rather go with granting 'anyone in the "incubator" group access to all the "incubator-NNN.git" repositories'
> 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
[jira] [Assigned] (INFRA-4877) Form for creating a new Git
repository
Posted by "Sam Ruby (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292135#comment-13292135 ]
Jukka Zitting commented on INFRA-4877:
--------------------------------------
> Where are these two lists kept?
git admin: Currently the gitadmins group as defined in conf/auth.cfg inside asfgit-admin.git (and deployed to /usr/local/etc/asfgit-admin/conf on tyr). I guess we could migrate this group to LDAP or use some other existing group if doing so makes things easier.
cordova PPMC: Currently only in http://incubator.apache.org/projects/callback.html. In svn such information would be encoded in an extra group in asf-authorization-template that grants podling committers access to the relevant repos/asf/incubator subtree, but in git we've for now simply granted anyone in the "incubator" group access to all the "incubator-NNN.git" repositories. Thus I'd be fine with using the "incubator" LDAP group as a close enough approximation.
> 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
[jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by "Sam Ruby (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291931#comment-13291931 ]
Sam Ruby commented on INFRA-4877:
---------------------------------
Can we walk through a few authentication scenarios?
Ideally, who should be able to request another git repository for the cordova PPMC?
Ideally, who should be able to request a first git repository for the openoffice.org PPMC?
Ideally, who should be able to request another git repository for the trafficserver PMC?
Ideally, who should be able to request a first git repository for the httpd PMC?
> 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
[jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by "Sam Ruby (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292374#comment-13292374 ]
Sam Ruby commented on INFRA-4877:
---------------------------------
Looks like an optional repository to clone would be a worthwhile addition:
https://issues.apache.org/jira/browse/INFRA-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292312#comment-13292312
> 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
[jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by "Sam Ruby (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292119#comment-13292119 ]
Sam Ruby commented on INFRA-4877:
---------------------------------
> A git admin from infra or anyone on the cordova PPMC
Where are these two lists kept?
> 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
[jira] [Updated] (INFRA-4877) Form for creating a new Git
repository
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot updated INFRA-4877:
-------------------------------------
Assignee: (was: 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
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292380#comment-13292380 ]
Jukka Zitting commented on INFRA-4877:
--------------------------------------
> Initially I would rather go with granting 'anyone in the "incubator" group access to all the "incubator-NNN.git" repositories'
+1 as mentioned earlier.
> Looks like an optional repository to clone would be a worthwhile addition:
If we simply provide an empty repository, the committers of the project can then take care of migrating any existing code simply by pushing the relevant version histories to the new Apache repository. If done that way, the entire migration operation will be covered by our existing push audit trail and we don't need to worry about an alternative path through which code can enter our repositories. See for example INFRA-4612 for an example.
> 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
[jira] [Updated] (INFRA-4877) Form for creating a new Git
repository
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated INFRA-4877:
---------------------------------
Description:
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.
was:
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 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.
> 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
>
> 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
[jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292057#comment-13292057 ]
Jukka Zitting commented on INFRA-4877:
--------------------------------------
> Ideally, who should be able to request another git repository for the cordova PPMC?
A git admin from infra or anyone on the cordova PPMC or the IPMC.
> Ideally, who should be able to request a first git repository for the openoffice.org PPMC?
A git admin from infra or anyone on the IPMC.
> Ideally, who should be able to request another git repository for the trafficserver PMC?
A git admin from infra or anyone on the trafficserver PMC.
> Ideally, who should be able to request a first git repository for the httpd PMC?
A git admin from infra.
Personally I don't see much trouble with answering any of the above questions with just "anyone" (nobody can push code to a repository without proper access), but the above are in line with current practice in svn.
> 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
[jira] [Commented] (INFRA-4877) Form for creating a new Git
repository
Posted by "Michael Brooks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424124#comment-13424124 ]
Michael Brooks commented on INFRA-4877:
---------------------------------------
Great discussion guys! Everyone on the Cordova project is excited to see this form come to life.
Any estimate on the implementation timeframe?
We've already got another pending Git repo request (INFRA-5078) [1] and Infra doesn't seem too interested in dealing with the issue before this form comes about. We'd like to see this repo created in the next week or two (before the next Cordova tag).
Michael
[1] https://issues.apache.org/jira/browse/INFRA-5078
> 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