On Jan 17, 2008 7:59 PM, Bruce Markham <[EMAIL PROTECTED]> wrote: > That sounds like *way* too much work in the wrong direction. If we really > wanted to vote on stuff, I'm sure we could find something pre-packaged for > the need.
Agreed here. Other people do this stuff, and it doesn't need to be redmine-integrated necessarily. > Unfortunately, the reality of it is, anything controversial enough needing a > vote, is up to the board. And the board is small enough that the lot of us > can handle voting by e-mail. Now now. Let's not pull the board card. Personally I like the idea of having community-driven adoption, but a dev still needs to put in the code in any case. In any such case, counting everyone's vote is silly for this, when it makes much more sense to have a peer-review driven model (IE, such a system would have 'endorsements', and a threshold of endorsements would have to be met before it would be integrated. Endorsements would be for developers only, and users would 'request' the patch instead. In that way, devs could view the most popular patches and work on those first, or choose to review the earlist patch posted if they were nice. Likewise devs could add a negative mark on a patch too. ) I'm not sure if there is such a system, I googled around but I'm not sure what to call it. In any case, the creation of such a system is out of the scope of our project. However, I'd probably be willing to help out on such a project if it were PHP (.... or MAYBE I'll think about learning ruby). If you're committed and cannot find another solution that does what we need you could start a SF.net project to create it, throw it in the SVN and you've got a side project. We'd definitely use it if there is not a better solution. But this begs the question if something so formal were to be necessary. I think that a rule of thumb should be sufficient for patches of unknown/unsure functionality/quality. Basically, if it's not code that you completely understand (and thus see any hidden consequences). find another dev who can and ask some questions. Doing so will help us all to better understand the code that we distribute as well. -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
