Re: [libxml-devel] Bug Day
On 1/6/07, Ross Bamford <[EMAIL PROTECTED]> wrote: > Hi, > > Okay, here's a little more on the upcoming bug day. This is all just my > thoughts, it'd be great to get any input on this at all. > > When > > I think we should hold the bug day in February, maybe around the 10-15th. > Pat recommends we announce at four weeks before, two weeks before, and a > week before, so that's what we should do. I'm giving advice, not commandments. Please make sure that whatever you do is right for the project. > > Activities > == > There've been a few bugs over the past week, a couple that are probably a > bit in-depth for a bug day, but at least one concerns poor test coverage. > We should make a start on getting as many (valid ;)) bugs into the > trackers as possible. I'm planning to comb through the tests and find weak > spots in coverage, which I'll then file bugs against. Which tools are you using? If you can find a way to do it, valgrind might be a good thing to add to your toolkit. > > As well as test coverage, we could also file bugs against documentation > (much of what's there is cursory, to say the least), and bad code that's > knocking around in there. > If the rubinius guys can get RNI done in time, getting libxml working on rubinius would be a fun project for a bug day too. > How > === > I think that, on the day, developers should be available on the list and > in an IRC channel somewhere, to help get people started and discuss > possible patches, etc. I'm happy to do this, of course - if anyone else > might be able to pitch in with that it'd be great. > I'd be happy to do what I can (mostly advertising and cheerleading). > Basically, people who want to get involved on the day will pick an issue, > maybe discuss a possible fix with us, and then send up a patch when > they're ready. We'd then check the patches, and commit them to CVS as > appropriate, or discuss them further with the submitter. Does anyone feel > like taking care of that side of things? > > That's it. As I say, any thoughts much appreciated. > > Cheers, > -- > Ross Bamford - [EMAIL PROTECTED] > ___ > libxml-devel mailing list > libxml-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/libxml-devel > -- thanks, -pate - http://on-ruby.blogspot.com ___ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
Re: [libxml-devel] A New LibXml
On 8/5/07, Charlie Savage <[EMAIL PROTECTED]> wrote: > > Thats the whole reason for a fork... No one can check in... > > Can't a ruby-forge administrator fix that? Imagine the confusion having > two libxml ruby bindings. There are legal reasons that prevent the admins from 'fixing' it. A fork is probably the only way to move forward. Whether or not the fork starts with a new code base or not is a question better left for the folks with the C/libXML chops that will enable them to make the decision. > > 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
Re: [libxml-devel] A New LibXml
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
Re: [libxml-devel] A New LibXml
On 8/6/07, TRANS <[EMAIL PROTECTED]> wrote: > On 8/6/07, Charlie Savage <[EMAIL PROTECTED]> wrote: > > > I think pat's right. rather than waste any more time, lets just fork > > > the dang thing. > > > > I agree its would be good to get going. But do we really need to fork > > just to get checkin privileges? Its just such an awful way of trying to > > reestablish checkin privileges. > > Unfortunately, without Sean Chittenden there's no way to get admin > privileges, and no one can get hold of Sean (again). So we're stuck in > the water without a paddle. I don't know what else to do but fork. > > Also, I should point out that this has happened twice before. In fact, > the last time I tried to move this project forward Sean appeared out > of NOWHERE to take admin control back. I wasn't happy about it. And > just as I suspected, here we are again w/o Sean. -- I don't want to > ever have to go through this again. I think that plenty of goodwill has been shown. It's time to start a new project with a couple of admins (both of whom should have a long history of hanging around). Whether or not the new project starts with libXML code is a decision for a different discussion (one held among the admins and coders). Trans, go ahead and start up a new project. Let me know what I can do to help. > > T. > ___ > 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
Re: [libxml-devel] Fwd: RubyForge Project Approved
On 8/6/07, Charlie Savage <[EMAIL PROTECTED]> wrote: > Ok, some questions: > > 1. Are we going to change to a new mailing list then? If so, maybe you > can send an email to this list Trans? If possible, it would be nice to continue to use this list as it will help to maintain some continuity and maybe catch some of the folks that miss the word of the fork/fresh start. Alternatively, this list should be monitored and people redirected to the new list. > > Charlie > -- 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
Re: [libxml-devel] libxml vs. libxml2
For consistency, stick to the original. On 8/17/07, TRANS <[EMAIL PROTECTED]> wrote: > Crazy, crazy. Sean appeared out the blue aether yesterday, and gave me > admin rights to the original libxml project. So I suppose the fork > isn't necessary after all. But I'll put it to the community just the > same to be sure. Should we stick to the old project or go forward with > the fork? > > T. > > > P.S. If we do stick with the original, I will still have the > repository converted to SVN and do some clean up. > ___ > 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
[libxml-devel] libxml and Rubinius
has anyone done any work getting libxml to work on/with Rubinius? -- 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
