git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: git@vger.kernel.org
Subject: [ANNOUNCE] repo.or.cz does full-fledged hosting now, and more
Date: Wed, 11 Oct 2006 02:30:51 +0200	[thread overview]
Message-ID: <20061011003051.GS20017@pasky.or.cz> (raw)

  Hi,

  few weeks ago, I have announced repo.or.cz public mirroring service
which would snap repositories, mirror them and provide a gitweb
interface for them. While at it, it also aims to serve as a testbed
for various new cool gitweb-related enhancements.

  I have finally got around to enhance it some more. Here go the big
changes:


  (i) repo.or.cz now permits an alternative hosting model: instead of
mirroring a remote repository, you can push over SSH. This makes
repo.or.cz full-fledged public hosting service. Each developer can
create own account, and you can give push access to multiple developers
if you want to do the CVS-style development. Authentication is done
purely using SSH keys. Furthermore, _optional_ support for anonymous
pushing to a dedicated 'mob' branch is supported.


  (ii) Bunch of extra project fields have been added - you can now
customize short description, homepage URL, give a short README to be
shown at the project summary page, ...


  (iii) Reorganized and extended the online documentation; gitweb now
uses pathinfo URLs and is aliased to http://repo.or.cz/w/


  (iv) Select a project and click at the 'graphiclog' button; if you
have a javascript-capable browser, watch the fireworks. This gadget
(http://repo.or.cz/w/git-browser.git) is nearly year old now and
back then swooshed through the mailing list without much interest
(apart few "cool!" replies). And I positively *HATE* not having it
when I browse any project whose history is not totally linear.

  OTOH, I have almost zero javascript skills so I'm not gonna be able
to develop it much further. Will someone pick up the slack? It's pretty
nice but leaves much to be desired; more tight gitweb integration (make
it basically some kind of external gitweb plugin) would be great.


  (v) Basically all the infrastructure is available at

	http://repo.or.cz/w/repo.git

Please review the code, send patches, feel free to roll out your very
own...


  What now? Send me your ideas, or even patches! (Hey, the code is
public. ;-) It might be interesting to have some forking support: there
goes project X and anyone can setup project fork(X, foo) and push his
changes there. I currently think the best way to do it technically would
be to just set up a separate repository with alternate pointing to the
main repository's database, and only group the forks with the main
project in gitweb. Is there a demand for that?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)

             reply	other threads:[~2006-10-11  0:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11  0:30 Petr Baudis [this message]
2006-10-11  1:50 ` [ANNOUNCE] repo.or.cz does full-fledged hosting now, and more Martin Langhoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061011003051.GS20017@pasky.or.cz \
    --to=pasky@ucw.cz \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).