:: [unSYSTEM] Fwd: Bitnation Details
Top Pagina
Delete this message
Reply to this message
Auteur: Caleb James DeLisle
Datum:  
Aan: System undo crew
Onderwerp: [unSYSTEM] Fwd: Bitnation Details
Got some (vague) details about the project.
Looks like this means they don't have any coordination systems
yet (irc, bugtracker, wiki).

This has the organizational appearance of the typical:
"I gotta idea, lets crowdfund it and then we'll figure out if it's feasible!"
so the only remaining way to analyze it is by googling each of the members
to see if they've successfully run similar projects in the past.

For me, it's a bit more closed-cluture than my ideal but we'll see how it
pans out.

Pedantic note: He removed my mail from the reply so I re-pasted it below.


-------- Forwarded Message --------
Subject: Bitnation Details
Date: Thu, 9 Oct 2014 13:10:38 -0400
From: Matt McKibbin <matt.mckibbin@???>
To: cjd@???

Hey Caleb,

The white paper, biz plan, and dev plan will be forthcoming by the
crowdsale. We are updating our website and getting everything put
together. The crowdsale is 3 months so there will be plenty of time to
digest the information before making a decision on whether to invest or not.

All our code will be open source. We will be using counterparty and
putting all of the code to our decentralized applications up on the Github.


Best Regards,

Matt McKibbin
BitNation: Chief Marketing Officer
Skype: matt.mckibbin1
bitnation.co


------------------------------------------
original mail
------------------------------------------

Hi,

I just discovered the project and I'm very excited about it.
Perhaps I can be of some help in the project but first I want to hear
all of the details. I have 5 years of experience with open source programming,
both as my profession and my hobby. I am the founder of the cjdns project so
I have some experience with leadership and community consensus building.

Can you tell me:

1. Where is the watering hole?
AKA the mailing list or IRC channel where the bitnation software and policy
development is coordinated.

2. Where is the code, when can I see (even incomplete non-working) code?

3. How much code will be open source, what will the license be?

4. Can I have the most recent draft of the protocol design specs?
How about the old drafts?

5. Where is the wiki and where is the bugtracker for managing todo tasks? :D

Hope to hear back soon.

Thanks,
Caleb