Re: [Inkscape-devel] new booleans patch
The updated patch from the author and my hookup patch (which puts the new commands into the menu and as shortcuts - ugly, just for testing) are here:
http://sourceforge.net/tracker/index.php?func=detail&aid=857377&grou...
Bryce, can you give Fred developer access to the CVS so he could create a branch for testing the new functions? (Or maybe I can now do this too as an admin, but I don't know how :)
_________________________________________________________________ Get holiday tips for festive fun. http://special.msn.com/network/happyholidays.armx
On Wed, 10 Dec 2003, bulia byak wrote:
The updated patch from the author and my hookup patch (which puts the new commands into the menu and as shortcuts - ugly, just for testing) are here:
http://sourceforge.net/tracker/index.php?func=detail&aid=857377&grou...
Coolness!
Bryce, can you give Fred developer access to the CVS so he could create a branch for testing the new functions? (Or maybe I can now do this too as an admin, but I don't know how :)
Certainly, I'd be happy to, what's Fred's SF username? (I didn't find 'yafoyah' listed.)
And yep, I had given you full admin capabilities, so you too can add new members. The rule we've adopted is basically that we want to require that the candidate make some contributions (or one significant one, as Fred has nicely done), and have a need for the access. We want to make it easy for proven contributors, but not leave CVS open to just anyone. (We are attentive to the patch tracker, so random one-time contributors are welcome to make use of that.) The rule of thumb I've been using is on the order of a couple average-sized patches, plus an interest in continuing to contribute.
Bryce
On Wed, 10 Dec 2003, Bryce Harrington wrote:
On Wed, 10 Dec 2003, bulia byak wrote:
The updated patch from the author and my hookup patch (which puts the new commands into the menu and as shortcuts - ugly, just for testing) are here:
http://sourceforge.net/tracker/index.php?func=detail&aid=857377&grou...
Coolness!
Bryce, can you give Fred developer access to the CVS so he could create a branch for testing the new functions? (Or maybe I can now do this too as an admin, but I don't know how :)
Certainly, I'd be happy to, what's Fred's SF username? (I didn't find 'yafoyah' listed.)
Aha, it's 'yafosf'. I've added him. Welcome to the team, Fred!
And yep, I had given you full admin capabilities, so you too can add new members. The rule we've adopted is basically that we want to require that the candidate make some contributions (or one significant one, as Fred has nicely done), and have a need for the access. We want to make it easy for proven contributors, but not leave CVS open to just anyone. (We are attentive to the patch tracker, so random one-time contributors are welcome to make use of that.) The rule of thumb I've been using is on the order of a couple average-sized patches, plus an interest in continuing to contribute.
Forgot to mention that to add new members, go to Admin, then Members, and scroll to the bottom of the 'Add a Developer' page.
Bryce
participants (2)
-
Bryce Harrington -
bulia byak