On Fri, Jul 16, 2010 at 08:50:53AM +0200, Gerfried Fuchs wrote: > Some comments on the patch for the templates and the package I haven't had any comments back from my suggest changes to address your concerns, so please find them attached with a patch. In accordance with your wishes, I will not issue a call for translations unless you explicitly ask for it. Thanks, -- Jonathan Wiltshire 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
--- /home/jona/debian/rewrite/gitolite/gitolite.old/debian/templates 2010-07-01 19:56:02.000000000 +0100 +++ /home/jona/debian/rewrite/gitolite/gitolite/debian/templates 2010-07-25 19:33:39.000000000 +0100 @@ -1,22 +1,33 @@ +# These templates have been reviewed by the debian-l10n-english +# team +# +# If modifications/additions/rewording are needed, please ask +# debian-l10n-english@lists.debian.org for advice. +# +# Even minor modifications require translation updates and such +# changes should be coordinated with translators and reviewers. + Template: gitolite/gituser Type: string Default: gitolite -_Description: The name of the system user to create: +_Description: System username for gitolite: Please enter the name for the system user which should be used by - gitolite. + gitolite to access repositories. It will be created if necessary. 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 become the gitolite 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. + . + This can be either the SSH public key itself, or the path to a file + containing it. If it is blank, gitolite will be left unconfigured and + must be set up manually. + --- /home/jona/debian/rewrite/gitolite/gitolite.old/debian/control 2010-07-01 19:56:02.000000000 +0100 +++ /home/jona/debian/rewrite/gitolite/gitolite/debian/control 2010-07-05 13:03:36.000000000 +0100 @@ -14,16 +14,21 @@ 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 +Description: SSH-based gatekeeper for git repositories + Gitolite is an SSH-based gatekeeper providing access control for a server that + hosts many git repositories. Without gitolite, + each developer needing to push to one of the repositories hosted would need a + user account on that server; gitolite lets 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. + Gitolite can restrict who can read (clone/fetch) from or write + (push) to a repository, and who can push to what branch or tag - an + important issue in corporate environments. Other features include: + * access control by branch-name or by modified file/directory; + * per-developer "personal namespace" prefixes; + * simple but powerful configuration file syntax (with validation); + * config files (and authority for maintaining them) can be split; + * easy integration with gitweb; + * comprehensive logging; + * easy migration from gitosis.
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 providing access control for a server that hosts many git repositories. Without gitolite, each developer needing to push to one of the repositories hosted would need a user account on that server; gitolite lets you do that just using SSH public keys tied to a single, common, user that hosts all the repositories. . Gitolite can restrict who can read (clone/fetch) from or write (push) to a repository, and who can push to what branch or tag - an important issue in corporate environments. Other features include: * access control by branch-name or by modified file/directory; * per-developer "personal namespace" prefixes; * simple but powerful configuration file syntax (with validation); * config files (and authority for maintaining them) can be split; * easy integration with gitweb; * comprehensive logging; * easy migration from gitosis.
# These templates have been reviewed by the debian-l10n-english # team # # If modifications/additions/rewording are needed, please ask # debian-l10n-english@lists.debian.org for advice. # # Even minor modifications require translation updates and such # changes should be coordinated with translators and reviewers. Template: gitolite/gituser Type: string Default: gitolite _Description: System username for gitolite: Please enter the name for the system user which should be used by gitolite to access repositories. It will be created if necessary. 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 become the gitolite 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. . This can be either the SSH public key itself, or the path to a file containing it. If it is blank, gitolite will be left unconfigured and must be set up manually.
Attachment:
signature.asc
Description: Digital signature