Re: svn management, git, etc
On Tue, Aug 08, 2006 at 07:15:21PM +0000, David Nusinow wrote:
[...]
> > So David, do what you want, I have no strong opinion on anything related to
> > SCM, but please let us have fun. This is surely what you want too, I hope
> > it will happen soon.
>
> I'm truly sorry you feel that way. I had no idea. Please give me some
> feedback on what you want to make things more fun.
Here are some things that annoy me:
* Flood of SVN commits to debian-x.
I can use a procmail rule to filter them, but I often browse web
archives. See for instance current archive:
http://lists.debian.org/debian-x/2006/08/threads.html
Dak messages are also annoying, but there is not much we can do
if we want the Maintainer field to be debian-x. IMO commit messages
could be sent to another list, maybe at teams.debian.net?
This is especially true when there is an experimental branch, see
* Web SVN interface:
I do not know if there is a good SVN web interface, svn.debian.org
is not better than XSF. http://git.freedesktop.org/ looks much more
usable.
* SVN layout:
This one is really minor, but there are some strange things, like
/tags which contains monolith/, or the contents of /tags/debian/{,xorg/}
* Lack of documentation:
Documentation is never where I am looking for, this is bad ;)
For instance, I read Branden's message
http://lists.debian.org/debian-x/2006/08/msg00055.html
about his tutorial on svn when coming back from vacation. As it did
not contain an URL, I did not go to the wiki and after reading
hundreds of mails I forgot about Branden's post. I found his (very good)
tutorial[0] yesterday when browsing XSF docs on the wiki. IMO sending
this tutorial to the list with a link to the wiki would be much better,
people could read it easily and send comments.
Enough rants, since anyone can contribute to this one without any
particular knowledge, I hereby volunteer to work on improving current
documentation. Not sure if it will be fun, but definitely useful ;)
Denis
[0] http://wiki.debian.org/XStrikeForce/svn-usage
Reply to: