"Stefan Monnier" <firstname.lastname@example.org> writes:
> That's the rub: they need to sign papers to make sure the FSF has
> the copyright over the file. Once that's done, getting write access
> is easy: get a savannah.gnu.org account (can be done online) and then
> ask one of the administrators of the Emacs project to add them
> to the people who get write-access.
I hope Kalle doesn't mind doing that (I've done it, never regretted
> In the mean time I intend to keep an eye on Subversion's vc-svn.el
> to try and keep Emacs' own version uptodate.
Stefan, I think you're going about things in the wrong order, and it
will cause much confusion.
You've made a fork. Now every time we see a vc-svn.el bug report,
we'll have to figure out whether the two are interfering with each
other, or whether the bug report is even for the right one. You'll
have the same problem in mirror image.
A better course would be to get papers from Kalle, make sure that
everyone who maintains vc-svn.el here will be able to do it there, and
then *move* the thing over. After all, there's no reason for a fork
here, because there aren't any technical disagreements about what the
code should do, nor even about where it should live in the long run.
Everyone wants to see it distributed with Emacs; but an orderly
transition would be much more helpful than a dual-maintenance
> Back in December 2001, I did a first attempt at getting VC working
> with Subversion. I never distributed it and I later on learned that
> Jim Blandy had made one of his own (not sure when he did it, tho).
> The vc-svn.el I installed in Emacs has no code taken from Subversion's
> vc-svn.el, although it does have a few ideas taken from there.
Okay, look at it this way: you created a package named vc-svn.el, even
though there was already a publically distributed package called
`vc-svn.el' by someone else. Why do it that way? Why not either a)
name your package something else, so as not to cause confusion, or
better yet, b) join the maintenance team of the one in the Subversion
tree, and help get it moved into Emacs?
I really think some more careful thought & planning is necessary here.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu May 8 07:14:56 2003