Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.175 as permitted sender)
	client-ip=209.85.217.175; envelope-from=laanwj@gmail.com;
	helo=mail-lb0-f175.google.com; 
MIME-Version: 1.0
In-Reply-To: <1348605677.2284.2.camel@localhost.localdomain>
References: <5061F8CC.9070906@mistfpga.net>
	<1348605677.2284.2.camel@localhost.localdomain>
Date: Wed, 26 Sep 2012 07:49:13 +0200
Message-ID: <CA+s+GJCO7_TXCPh1P33HS-wNHpL7DbZcimUxE3wR9Y=XfrfBrA@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Matt Corallo <bitcoin-list@bluematt.me>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Development List <bitcoin-development@lists.sourceforge.net>,
	Bill Hees <billhees@gmail.com>
Subject: Re: [Bitcoin-development] Bitcoin Testing Project
Precedence: list

I think it's a great initiative Steve,

On Tue, Sep 25, 2012 at 10:41 PM, Matt Corallo <bitcoin-list@bluematt.me> wrote:

> They both run the same set of scripts, namely those at
> https://github.com/TheBlueMatt/test-scripts (its pretty basic right now,
> but since it is on github, I was hoping someone would find the
> inspiration to add to it).

The pulltester and Jenkins are really useful, I think it's best to
keep these and improve them if needed.

> I dont really care if we keep using jenkins, but I figure we might as
> well keep all the tests in one place?

Which brings me to another issue: we desperately need a page that
links all the developer resources for bitcoin dev:

- link to my doxygen docs (https://dev.visucore.com/bitcoin/doxygen/)
- bluematt's pulltester and jenkins
- any testing dashboards Steve is going to add

But also:

- how to check out the source code, how to find the build instructions
for your platform
- contribution guidelines
- where to ask w/ development problems (this mailing list, #bitcoin-dev)
- where to begin, which bugs to solve first
...

Maybe on bitcoin.org, but at least easy to find for people that want
to contribute, not just some deeply nested wiki page. Ie, something
like

https://www.mozilla.org/en-US/contribute/
http://www.ogre3d.org/developers
...

I'm willing to write this. But I know these kinds of proposals always
end in a big discussion about what should be and what should not be on
bitcoin.org, however we should be a bit pragmatic here.

Wladimir