Quiet Period

[Will Pearson]

I'm going to be quiet for a while coding. Once I have a demo of the
tech, I'll post it here and see what people think of it. Then if it
meets with your approval, I'll post it on hackernews, to get a bit of
buzz going about it.

This doesn't mean you shouldn't be doing stuff! My general outlook on
things is that people can do whatever they want towards the creating
of this group. The general process that I have seen work (on a small
scale) is:

1) See a need
2) Find a solution
This might be doing it yourself or outsourcing it via mechanical turk,
rentacoder or similar service
3) Tell the list:
If it is big or affects the PR of the group (in an unusual way) this
is useful. If it is small (fixing a bug) then don't bother telling the
list but document it somewhere. Please avoid bikeshedding on small
problems: http://www.bikeshed.com/
4) Do it, with two funding options.
i) Pay for it out of your own pocket
ii) Set up a pledge. Basically say you are willing to put X towards
something, but Y is needed. We'll cross that bridge when we get to it.

We'll sort out a more formal structure when we have know where exactly
we are going.

I'm happy to pay for small scale servers for testing purposes out of
my own pocket.

Will