Differences between revisions 1 and 5 (spanning 4 versions)
Revision 1 as of 2006-11-07 13:46:48
Size: 745
Comment: Add web application to manage users and repos for hgwebdir
Revision 5 as of 2006-11-09 09:48:04
Size: 1564
Editor: ws
Comment: Bundle Digest + little fix above
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 * allow to create new branches from an existing one and let the admin choose which repos can be branched for each user or group of users.  * allow to create new branches from an existing one and let the admin choose which repos can be branched for each user or group of users. (a branch should be a clone from the master repo of the project, or any other specified repo)

 /!\ Please be sure to create a separate webapp for this so hgweb/hgwebdir would stay KISS. Some users (maybe most) will not want to use the web interface for managing repos... -- Radek Podgorny

== Greater flexibility for merge/export ==

Experience from several other systems suggests that the current approach to handling BinaryFiles is not adequate. mpm is absolutely right that the notion of a binary file is intrinsically confused. Unfortunately, that doesn't mean that we can avoid it. This needs some discussion, so I'm attempting to add a page for that: NewIdeas/FileTypes

== User friendly off-line synch of distributed repos using "Bundle Digest" ==

see [http://www.selenic.com/mercurial/bts/issue392]

New ideas and suggestions

1. Web application to manage users and repos using hgwebdir and ssh authentication

It would be very useful having an app that would:

  • allow a site admin to tweak the hgwebdir configuration
  • let users create an account providing a name, an email account and the server would generate a ssh key that gets sent to the user after admin approval.
  • add the relevant bits to the ssh configuration file for registered users
  • allow the admin to select which repos can be accessed by each user or group of users by checking and unchecking boxes in a list of repos.
  • allow to create new branches from an existing one and let the admin choose which repos can be branched for each user or group of users. (a branch should be a clone from the master repo of the project, or any other specified repo)

    /!\ Please be sure to create a separate webapp for this so hgweb/hgwebdir would stay KISS. Some users (maybe most) will not want to use the web interface for managing repos... -- Radek Podgorny

2. Greater flexibility for merge/export

Experience from several other systems suggests that the current approach to handling BinaryFiles is not adequate. mpm is absolutely right that the notion of a binary file is intrinsically confused. Unfortunately, that doesn't mean that we can avoid it. This needs some discussion, so I'm attempting to add a page for that: NewIdeas/FileTypes

3. User friendly off-line synch of distributed repos using "Bundle Digest"

see [http://www.selenic.com/mercurial/bts/issue392]

NewIdeas (last edited 2013-08-27 14:58:55 by AugieFackler)