Please find, for review, the debconf templates of gitolite.
This review will last from Thursday, July 01, 2010 to Sunday, July 11, 2010.
Please send reviews as unified diffs (diff -u) against the original
files. Comments about your proposed changes will be appreciated.
Your review should be sent as an answer to this mail.
When appropriate, I will send intermediate requests for review, with
"[RFRn]" (n>=2) as a subject tag.
When we will reach a consensus, I send a "Last Chance For
Comments" mail with "[LCFC]" as a subject tag.
Finally, the reviewed templates will be sent to the package maintainer
as a bug report, and a mail will be sent to this list with "[BTS]" as
a subject tag.
Rationale:
There are no changes to debian/control, although I'm not sure about the
section talking of "dedication"; I'm hoping somebody will give me some
ideas about that.
--- ../gitolite.old/debian/templates 2010-07-01 19:56:02.000000000 +0100
+++ debian/templates 2010-07-01 20:17:23.000000000 +0100
@@ -1,22 +1,24 @@
Template: gitolite/gituser
Type: string
Default: gitolite
-_Description: The name of the system user to create:
+_Description: System user to use:
It might already be created.
Please enter the name for the system user which should be used by
- gitolite.
+ gitolite. It will be created if necessary, and its home
+ directory will be used to store repositories.
Mention that gitolite/gitdir will be asking for the home directory *before*
the user makes a choice for this question. It might affect their choice of
system user.
Template: gitolite/gitdir
Type: string
Default: /var/lib/gitolite
-_Description: The directory to contain the repositories:
- Please enter the path for the directory in which you want to store the
- git repositories guarded by gitolite. This will also become the home
- of the former entered username.
+_Description: Repository path:
+ Please enter the path in which the gitolite repositories should be stored.
+ This will be set as the system user's home directory.
Shorten the title and simplify the question a little so it's clearer. Don't
make any chronological link between questions, because this isn't
guaranteed.
Keep the second person ("you") out of it entirely.
Template: gitolite/adminkey
Type: string
-_Description: The key for the admin user:
+_Description: Administrator's SSH key:
I'm taking an educated about the SSH part :) A key could be lots of things,
let's make it obvious.
Please specify the key of the user that will administer the access
- configuration of gitolite. You can either give the filename or paste
- the ssh public key. Leave empty if you do not want to set up gitolite
- in the directory specified earlier.
+ configuration of gitolite.
+ .
+ The installer can accept the SSH public key directly, or the path to a file
+ containing it. If blank, the installer will not configure gitolite and it
+ must be set up manually.
Keep the second person out again.
Template: gitolite/gituser Type: string Default: gitolite _Description: System user to use: Please enter the name for the system user which should be used by gitolite. It will be created if necessary, and its home directory will be used to store repositories. Template: gitolite/gitdir Type: string Default: /var/lib/gitolite _Description: Repository path: Please enter the path in which the gitolite repositories should be stored. This will be set as the system user's home directory. Template: gitolite/adminkey Type: string _Description: Administrator's SSH key: Please specify the key of the user that will administer the access configuration of gitolite. . The installer can accept the SSH public key directly, or the path to a file containing it. If blank, the installer will not configure gitolite and it must be set up manually.
--- ../gitolite.old/debian/templates 2010-07-01 19:56:02.000000000 +0100 +++ debian/templates 2010-07-01 20:17:23.000000000 +0100 @@ -1,22 +1,24 @@ Template: gitolite/gituser Type: string Default: gitolite -_Description: The name of the system user to create: +_Description: System user to use: Please enter the name for the system user which should be used by - gitolite. + gitolite. It will be created if necessary, and its home + directory will be used to store repositories. Template: gitolite/gitdir Type: string Default: /var/lib/gitolite -_Description: The directory to contain the repositories: - Please enter the path for the directory in which you want to store the - git repositories guarded by gitolite. This will also become the home - of the former entered username. +_Description: Repository path: + Please enter the path in which the gitolite repositories should be stored. + This will be set as the system user's home directory. Template: gitolite/adminkey Type: string -_Description: The key for the admin user: +_Description: Administrator's SSH key: Please specify the key of the user that will administer the access - configuration of gitolite. You can either give the filename or paste - the ssh public key. Leave empty if you do not want to set up gitolite - in the directory specified earlier. + configuration of gitolite. + . + The installer can accept the SSH public key directly, or the path to a file + containing it. If blank, the installer will not configure gitolite and it + must be set up manually.
Source: gitolite Section: vcs Priority: optional Maintainer: Gerfried Fuchs <rhonda@debian.at> Build-Depends: quilt Build-Depends-Indep: po-debconf Standards-Version: 3.8.4 Homepage: http://github.com/sitaramc/gitolite Vcs-Browser: http://git.deb.at/w/pkg/gitolite.git Vcs-Git: git://git.deb.at/pkg/gitolite.git Package: gitolite Architecture: all Depends: git (>= 1:1.7.0.4) | git-core (>= 1:1.6.2), perl (>= 5.6.0-16), openssh-server | ssh-server, debconf (>= 0.5) | debconf-2.0, adduser Suggests: git-daemon-run, gitweb Description: ssh-based gatekeeper for git repositories Gitolite is an ssh-based gatekeeper for a server that hosts many git repositories, and that needs access control of some sort. Without gitolite, each developer needing to push to one of the repositories hosted will need a (Unix) userid and password on that server; gitolite let you do that just using ssh public keys tied to a single, common, user that hosts all the repositories. . What makes gitolite unique is its dedication: Its primary target is corporate environments where the ability to restrict who can push to what branch is also important. It has grown beyond that initial motivation to write it and acquired several other neat features that you can find described in the main README.
Attachment:
signature.asc
Description: Digital signature