Bah, didn't read the whole email... it's too early... as soon as i clicked "send" :(
I'd say give it a new name, I doubt they'll hand it over. You might have more clout, but they wouldn't give me commit access when I asked. I'm pretty sure they want to remain in control of JLine. Sorry about the extra email. Joe On Tue, Feb 17, 2009 at 8:36 AM, Joe <qbpro...@gmail.com> wrote: > When forking a project, shouldn't you change the name of it? Linux > distributions seem likely to be annoyed if you fork and keep the same > name. > > Joe > > On Tue, Feb 17, 2009 at 2:45 AM, Charles Oliver Nutter > <charles.nut...@sun.com> wrote: >> I've forked Jline: >> >> http://github.com/headius/jline/tree/master >> >> I know the maintainer was friendly to us, but I think we really need to have >> more control over a few of these buggy libraries, so we can spin new >> releases as needed. >> >> I've never forked an OSS project before. Should we give it a new name or try >> to get the original maintainer to hand over control of the maven artifacts? >> I don't really care either way, but I'd like to get a bunch of patches into >> my fork and release that instead of vanilla jline with JRuby 1.2. >> >> Suggestions, patches, comments welcome. >> >> - Charlie >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
