On 8/6/07, Charlie Savage <[EMAIL PROTECTED]> wrote: > Hi Pat, > > > There are legal reasons that prevent the admins from 'fixing' it. > > A fork is probably the only way to move forward. > > Can you explain the legal reasons? And can they be worked around by > adding another administrator to the project, say Trans, as opposed to > changing anyone's existing passwords?
The problem is that the current administrator of the project is the legal owner of the code under copyright, and adding new administrators without consent violates his/her rights as the owner. I've tried to work out an 'advance directive' statement that would allow project owners/admins to protect against this (and tried to engage some serious legal folks), but have been unable to come up with anything satisfactory. :( > > Forking just to get checkin privileges seems like a really, really ugly > thing to to. Its just going to confuse everyone - the libxml gem gets > downloaded a fair bit and how exactly are we going to explain to > everyone that it is no longer valid? > The same way that apache supplanted ncsa httpd. Through track record of producing and supporting good stuff. > Charlie > > _______________________________________________ > libxml-devel mailing list > libxml-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/libxml-devel > > -- thanks, -pate ------------------------- Duty makes us do things, Love make us do things well. http://on-ruby.blogspot.com http://on-erlang.blogspot.com http://on-soccer.blogspot.com _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
