From: steve <steve@mistfpga•net>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Development List <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Testing Project
Date: Wed, 03 Oct 2012 04:00:16 +0100 [thread overview]
Message-ID: <506BAA40.8060905@mistfpga.net> (raw)
In-Reply-To: <CAAS2fgQjHGHGomFWLoK2p-LZZHeJ8TcnYwHLo9Byv5tOo_eNsQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/10/2012 03:02, Gregory Maxwell wrote:
> On Tue, Oct 2, 2012 at 9:15 PM, steve <steve@mistfpga•net> wrote:
>> Im ready to go, more or less. Please check out the links in my
>> previous emails. I have over 400 testcases (8 platforms * 50
>> release tests) - Also I am not sure what you mean by bless, I
>> take it that is a euphemism for pay?
>
> Perhaps a bit bluntly here— but since you seem to be rather boldly
> insisting on getting paid:
that is not what i was getting at, nor what i meant at all.I am sorry
it came across this way. Im a bit drunk. (yeah that old excuse) I was
only trying to make an example of the quandary that exists, in what
happens to the current donations. There are far more deserving people
who have a claim on that coin rather than I.
I have stated on more than on occasion (written in public and verbal
with gavin) that I would be willing to work for free. But I would love
to be able to ditch the day job. (however i see that more as services
than mining/testing)
rereading what i wrote yeah, fair play i can see how you read my mail
like that. it wasnt meant to :/ i feel a bit of a turnip. the tone is
not what i meant. it does read pretty mercenary.
>
> With all of this testing where can I find the issues you've
> uncovered? Searching on your name/email in the issue tracker
> reports nothing, likewise I can't find anything in my email (beyond
> abstract discussion of testing).
>
This is a different issue. But I see why you have raised it and I
would like to address it. I personally believe you should earn
bitcoins for writing testcases, executing testcases, passing or
failing test cases. in that order (failing a testcase normally
generates a new one therefore encouraging indepth and recorded
testing.). QA should not be judged based solely on bug reports - this
is unfair and will result in race to report bugs. I have worked on a
few projects that have tried it.
This is one reason we need workflow and testcase software, so we can
measure and compensate people for their work.
As I have stated in previous emails I should have, but for various
excuses did not manage to run a single testcase for 0.7. but I did
setup a frame work, and I know some people did do some good work on
0.7 I believe these people should be compensated from the (limited)
funds the project received... something needs to happen with those coins.
I am sorry you find my emails abstract (and therefore meaningless?)
this is a really confusing time. i dont know if i am doing right from
wrong. I am trying to lead, without leading... i have always preferred
benevolent dictator. I know a number of bitcoin businesses that are
really keen to work with the project, but I have no authority, noone
seems to. Someone should be able to say, nice one, thanks for the
vm's. maybe use $200 worth of coin to get a technet licence, that
gives 10 installs of each ms OS. slipstreaming in the service packs
means you can have whatever era pc you want (and the vps providers
will allow various configuration of vm's...) then even if you do it by
hand you can still do 6 or 7 at once...
as for bug reports, give me 1 week from now (168hrs), lets see what i
can do. (priority, protocol, daemon, qt ref?) but still process is
more important...
I still think that writing and doing testcases should get more coin
than bug reports. but from what I have read, the big bounties will be
paid by the foundation. im not sure if that is true or where i read
it. (protocol level bugs)
it feels like I am wasting peoples time,and I should get back in my
box. so I will.
contact me off list if you want to have a look at the various workflow
stuff i have done.
cheers,
steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQa6pAAAoJEFvEB9dQFvtQ0H8H/jUjvzmsp61w1bmDnHR+KmF4
LNu7WwVLrTvrT8AHSNh3mClWvMM3muJJA7NMb2WthAgVe3jtrGimfreAlstDsObL
XNEcGvU6WN1YosH0MkN7hyDl8jnrDFoiH1P5qsMecuZIxwq7Z0vCOHEJ9DPmZilW
R+G8OmoGcpaeWs9VqXR6zR7Uyz69KaDAQpMRE1GTu3zQP9HSSolciy3ESeJRR9Sd
yO7EcCGdQot80rOG/VIZ0wkOmzGGm1thzYzayD6Zn2eW4Hw+ME1en9ksIbXJFpSv
IdgThEm7p5UuBo0jFkbX4Awrf9hfusZSEGWfhZqdASqqkSBnYqLmWF1sLprDRF8=
=Iv87
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-10-03 3:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 18:32 steve
2012-09-25 20:41 ` Matt Corallo
2012-09-26 5:49 ` Wladimir
2012-09-26 11:41 ` Daniel F
2012-09-26 12:00 ` Luke-Jr
2012-09-26 12:28 ` steve
2012-09-26 12:49 ` Wladimir
2012-09-26 13:22 ` steve
2012-09-26 16:06 ` Mark Friedenbach
2012-09-26 17:10 ` Jeff Garzik
2012-09-26 17:44 ` steve
2012-09-26 18:09 ` Gavin Andresen
2012-09-29 18:26 ` steve
2012-10-01 13:52 ` Arklan Uth Oslin
2012-10-01 14:28 ` steve
2012-10-01 16:52 ` Peter Vessenes
2012-10-03 1:15 ` steve
2012-10-03 2:02 ` Gregory Maxwell
2012-10-03 3:00 ` steve [this message]
[not found] ` <CAMGNxUu=LTZyAxKt3pAYSVxyhHBU9pyJPCiFs-tA_weYNNXbtw@mail.gmail.com>
[not found] ` <CAMGNxUuHRBkE_MbmY=A0vQvq=gMfzCFG8Us7SdBn-14KiKMaNg@mail.gmail.com>
2012-10-03 5:04 ` Peter Vessenes
2012-10-03 16:06 ` steve
2012-10-03 16:11 ` Arklan Uth Oslin
2012-10-03 16:15 ` [Bitcoin-development] Fwd: " steve
2012-10-03 17:09 ` Peter Vessenes
2012-10-03 17:30 ` Gavin Andresen
2012-09-27 0:53 ` [Bitcoin-development] " Matt Corallo
2012-09-27 2:29 ` Gregory Maxwell
2012-09-25 20:49 ` Daniel F
2012-09-25 21:25 ` Gary Rowe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=506BAA40.8060905@mistfpga.net \
--to=steve@mistfpga$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox