> Sure, it'd be nice if we had someone paid to work on this full time, but > that's not the case. I don't see anyone stepping forward, all I see are > complaints about the fact that people are saying they're busy.
Perhaps an existing contributor has extra cycles to be Next Release Wrangler if they saw *exactly* what should be addressed for the next release and could determine whether they can make the commitment. That's not to say this person is responsible for implementing all the fixes. Odds are probably against it though, but I see value in explicitly stating the v.next Fix List and seeing where things go. > There is a great history of real bugs in the rubyforge backlog, and quite a > few patches that need someone to read, think, and rewrite. >....[SNIP].... > There aren't any "must fix", the critical issues are that of integration > points and feature enhancements. Throw up a target by explicitly prioritizing the big issues in the backlog. What in your view are the 3-5 bugs currently in the rubyforge tracker that, if fixed, would cause you to green light a 1.3.8? > What you're asking is that I write down all my thoughts in great detail, > which takes much longer than writing the code or doing the due dilligence and > research, basically multiplying my workload by 4x. No, I only want to know the "official" top issues to resolve for a 1.3.8 release. > I'd agree with this if it would result in patches and better thinking from > people, indeed that's what I hoped when I put the details up on the wiki at > Eriks request. Thus far, that's proven to be a complete pipe dream. Unfortunately, I have to agree with you on this. That said, there are often non-immediate serendipities (?) that occur that always surprise me. For example, as part of the RubyInstaller project, the effort to make it easier for Windows users to build native extensions has recently led someone to work on porting Redis to Windows -> http://groups.google.com/group/rubyinstaller/browse_thread/thread/ba6bac3df60fefdb > You want more contributors, but are you going to step up? Are you willing to > pay for a CI system that has a VM for a few major linux platforms, BSD, OSX > and Windows? > >....[SNIP].... > > Step up please, because that's all that will really help. Sadly, I don't have the time to commit to doing any of these in a sustainable, value-add manner so I'm not going to lie to you, say I might, jump in and then disappear. What I currently have time to do is maintaining wiki documentation that might jump start others to help with these efforts and offer to help offload you on documentation stuff. Your expertise and limited time is best used solving the hard issues. I'm thinking of two key pages: Next Release Showstoppers (short-n-sweet listing and links back to the current 3-5 top rubyforge bugs), and RubyGems Project Needs (CI, OBS, etc). With the project needs clearly identified, shopping for project sponsors, starting a Pledgie for financing CI/VM needs, etc makes more sense. I admit these sound trivially underwhelming given all that you've identified, but if this micro-step-up could add any value, I'll do it. Jon _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
