Differences between revisions 13 and 18 (spanning 5 versions)
Revision 13 as of 2009-05-19 19:30:55
Size: 1943
Editor: localhost
Comment: converted to 1.6 markup
Revision 18 as of 2011-02-18 03:20:14
Size: 2029
Editor: ruby
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
Line 30: Line 29:
A good approximation of this idea is [[http://freehg.org/|freehg.org]]. The source hg repository is [[http://freehg.org/u/mmarshall/freehg/|here]] (by Matthew Marshall).
Line 31: Line 31:
A good approximation of this idea is [[http://freehg.org/|freehg.org]]. The source hg repository is [[http://freehg.org/u/mmarshall/freehg/|here]] (by Matthew Marshall).  . Currently unavailable or not functioning properly. -- PaulBoddie <<DateTime(2010-02-10T15:04:57+0100)>>
Line 35: Line 35:
 why are you not using edgewall trac, e.g.: == Discussion ==
why are you not using edgewall trac, e.g.:
Line 39: Line 41:
 * [[http://trac-hacks.org/wiki/BzrPlugin|trac bazaar plugin]], especially [[http://www.pkgcore.org/trac/wiki/Branches|bazaar plugin with branches]], [[http://www.pkgcore.org/trac/browser?rev=%3A100%3Amarienz%252Ftrac%25252Bbzr|source here]]
as a base?
 * [[http://trac-hacks.org/wiki/BzrPlugin|trac bazaar plugin]], especially [[http://www.pkgcore.org/trac/wiki/Branches|bazaar plugin with branches]], [[http://www.pkgcore.org/trac/browser?rev=:100:marienz/trac+bzr|source here]] as a base? -- SoloTurn
Line 42: Line 43:
 Because we're not building anything that looks remotely like a Trac site. -- mpm Because we're not building anything that looks remotely like a Trac site. -- mpm
Line 44: Line 45:
the idea was more in the sense of a "trac plugin" which looks like you design it. everything else is there. what problem do you have with trac as you try to reinvent the wheel here?
----
how about PublishingRepositoriesUsingCherryPy ?
----

CategoryWeb
the idea was more in the sense of a "trac plugin" which looks like you design it. everything else is there. what problem do you have with trac as you try to reinvent the wheel here? -- SoloTurn

CategoryProposedDeletion

Being able to manage a collection of repositories via the web is handy for both departmental servers and public ones.

Requirements

Features for a web interface:

  • ability to register user and passwords for htaccess
  • ability to reset passwords

User and admin capabilities:

  • initialize or clone new repositories
  • edit existing repositories
  • change password
  • change email address

Repo administration:

  • delete repo
  • verify
  • rollback
  • strip
  • set description
  • set notify addresses
  • set allowed users for push (default owner-only)
  • set default web encoding? (UTF-8)
  • set per-repo message of the day

Implementation

A good approximation of this idea is freehg.org. The source hg repository is here (by Matthew Marshall).

  • Currently unavailable or not functioning properly. -- PaulBoddie 2010-02-10 14:04:57


Discussion

why are you not using edgewall trac, e.g.:

Because we're not building anything that looks remotely like a Trac site. -- mpm

the idea was more in the sense of a "trac plugin" which looks like you design it. everything else is there. what problem do you have with trac as you try to reinvent the wheel here? -- SoloTurn

CategoryProposedDeletion

HostingDesign (last edited 2011-02-18 03:20:14 by ruby)