This is to announce I made a bet with Bryce to the tune of EUR 20 that inkscape people are not able to reach 200 points of fixed bugs within a week, payable to the inkscape project if wrong.
The date is 2006-Jun-01 07:20 GMT.
ralf
On 5/25/06, Ralf Stephan <ralf@...748...> wrote:
This is to announce I made a bet with Bryce to the tune of EUR 20 that inkscape people are not able to reach 200 points of fixed bugs within a week, payable to the inkscape project if wrong.
Bryce, do we count only fixed bugs, or any closed ones?
By the way, to have any chance to win this bet, we need help from our users. Please report plenty of specific, reproducible, well-documented bugs to fix! :)
Aaron, and to help users with that, it's important to have pre0 out as early as possible.
On 5/25/06, Ralf Stephan <ralf@...748...> wrote:
This is to announce I made a bet with Bryce to the tune of EUR 20 that inkscape people are not able to reach 200 points of fixed bugs within a week, payable to the inkscape project if wrong.
Bryce, do we count only fixed bugs, or any closed ones?
To clear this up, here's the jabber log:
(09:15:55 AM) ^-: [bryce] I'd be willing to place a wager that we can do 200 points within a week, if you'd like. (09:16:32 AM) rwst: that we can or that we will? (09:16:40 AM) ^-: [bryce] that we will (09:18:05 AM) rwst: 20 € against that, with the amount payable to the project (09:18:16 AM) ^-: [bryce] ok deal
So this means points in general, but I'll increase to EUR 25 for fixed ones only.
ralf
Hi,
Aaron, and to help users with that, it's important to have pre0 out as early as possible.
Will we also have binary stuff? (I found that compiling from sources on a SUSE 10 system would require hacking the system to death, which I don't want to do - I would lose vendor security support for a lot of packages.)
Arpad Biro
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Thursday 25 May 2006 17:22, Arpad Biro wrote:
Aaron, and to help users with that, it's important to have pre0 out as early as possible.
Will we also have binary stuff? (I found that compiling from sources on a SUSE 10 system would require hacking the system to death, which I don't want to do - I would lose vendor security support for a lot of packages.)
I intend to make an RPM when pre0 is available, and since I will be building it on SUSE 10, you, at least, should have no problem running it :-)
JFL
On Thu, May 25, 2006 at 09:33:50AM -0400, bulia byak wrote:
On 5/25/06, Ralf Stephan <ralf@...748...> wrote:
This is to announce I made a bet with Bryce to the tune of EUR 20 that inkscape people are not able to reach 200 points of fixed bugs within a week, payable to the inkscape project if wrong.
Bryce, do we count only fixed bugs, or any closed ones?
Right, generally we don't count dupes, invalids, wontfixs, unreproducable, etc. only bugs that were actually fixed.
Bryce
On Thu, May 25, 2006 at 09:57:30AM -0500, Aaron Spike wrote:
bulia byak wrote:
Aaron, and to help users with that, it's important to have pre0 out as early as possible.
Can someone point me to a tome on gpg etiquette?
Here's a howto...
http://www.dewinter.com/gnupg_howto/english/GPGMiniHowto.html
But basically you just need to do this:
After installing gpg (usually called 'gnupg'), you can create a key like this:
To set up key:
$ gpg --gen-key Please select what kind of key you want: (1) DSA and Elgamal (default)
Your selection? 1 What keysize do you want? (2048)
Please specify how long the key should be valid. 0 = key does not expire
Key is valid for? (0)
Key does not expire at all
Is this correct? (y/N) y
Real name: myname Email address: Comment:
You selected this USER-ID: "myname"
You need a Passphrase to protect your secret key.
passphrase: myphrase again: myphrase
pub 1024D/48D293A1 2006-02-13 Key fingerprint = 6738 5CA3 514D 35D6 DB26 98CF B5B5 80D1 48D2 93A1 uid myname sub 2048g/2DA7C55C 2006-02-13
To encrypt FILE: $ gpg -r myname --encrypt FILE
To GPG sign a tarball, see http://wiki.inkscape.org/wiki/index.php/CreatingDists
HTH Bryce
On Thu, May 25, 2006 at 08:22:47AM -0700, Arpad Biro wrote:
Hi,
Aaron, and to help users with that, it's important to have pre0 out as early as possible.
Will we also have binary stuff? (I found that compiling from sources on a SUSE 10 system would require hacking the system to death, which I don't want to do - I would lose vendor security support for a lot of packages.)
Aaron will only be responsible for publishing the official tarballs, but hopefully packagers will pick those up and do the rest. It'll be good practice to check for any remaining packaging issues, and will make it that much easier for others to test.
Bryce
Everything Bryce said, but also you should upload your key to a keyserver. That way people can get your public key, which is important if they want to verify the binaries.
--Ted
On Thu, 25 May 2006, Bryce Harrington wrote:
On Thu, May 25, 2006 at 09:57:30AM -0500, Aaron Spike wrote:
bulia byak wrote:
Aaron, and to help users with that, it's important to have pre0 out as early as possible.
Can someone point me to a tome on gpg etiquette?
Here's a howto...
http://www.dewinter.com/gnupg_howto/english/GPGMiniHowto.html
But basically you just need to do this:
After installing gpg (usually called 'gnupg'), you can create a key like this:
To set up key:
$ gpg --gen-key Please select what kind of key you want: (1) DSA and Elgamal (default)
Your selection? 1 What keysize do you want? (2048)
Please specify how long the key should be valid. 0 = key does not expire
Key is valid for? (0)
Key does not expire at all
Is this correct? (y/N) y
Real name: myname Email address: Comment:
You selected this USER-ID: "myname"
You need a Passphrase to protect your secret key.
passphrase: myphrase again: myphrase
pub 1024D/48D293A1 2006-02-13 Key fingerprint = 6738 5CA3 514D 35D6 DB26 98CF B5B5 80D1 48D2 93A1 uid myname sub 2048g/2DA7C55C 2006-02-13
To encrypt FILE: $ gpg -r myname --encrypt FILE
To GPG sign a tarball, see http://wiki.inkscape.org/wiki/index.php/CreatingDists
HTH Bryce
All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&da... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, May 25, 2006 at 04:51:17PM +0200, Ralf Stephan wrote:
On 5/25/06, Ralf Stephan <ralf@...748...> wrote:
This is to announce I made a bet with Bryce to the tune of EUR 20 that inkscape people are not able to reach 200 points of fixed bugs within a week, payable to the inkscape project if wrong.
Bryce, do we count only fixed bugs, or any closed ones?
To clear this up, here's the jabber log:
(09:15:55 AM) ^-: [bryce] I'd be willing to place a wager that we can do 200 points within a week, if you'd like. (09:16:32 AM) rwst: that we can or that we will? (09:16:40 AM) ^-: [bryce] that we will (09:18:05 AM) rwst: 20 ??? against that, with the amount payable to the project (09:18:16 AM) ^-: [bryce] ok deal
So this means points in general, but I'll increase to EUR 25 for fixed ones only.
Sounds good, although I had assumed fixed bugs from the start. It'd be way too easy to win on closed invalid bugs. ;-)
I'm proud to see that the Inkscape team is already past 25% of the way to the goal after not quite 2 days. :-) And I've noticed at least a couple patches in the tracker that haven't been applied yet.
Bryce
participants (7)
-
unknown@example.com
-
Aaron Spike
-
Arpad Biro
-
Bryce Harrington
-
bulia byak
-
Jean-François Lemaire
-
Ralf Stephan