Except for
"- create working examples of "hello world" smart contracts and operations,"
that is exactly what I am doing already for quite some time
In your worker proposal you state very vaguely:
Lots of Documentation (e.g. docs.bitshares.eu), Whitepapers, BSIPs,
@xeroc , is there any place where I can find what areas you intend to address in the documentation covered by your worker proposal?
And also what areas you definitely don't intend to address?
This would help us greatly in avoiding overlapping.
There is nothing that I do NOT want to have in there .. (except maybe politics) ..
There is also a poll on what I should work on next:
https://bitsharestalk.org/index.php/topic,19967.new.html#new
I tackled some of them already
I know that ideally we would like to have everything united in one place.
However, please be more specific what your plans and capabilities are for the next 2-3 months, as otherwise it's hard for me to specify goals for a person attempting to create a Graphene development tutorial.
Telling him/her "just work with xeroc and fill in whatever you can" is not specific enough IMO.
My aim is to create a tutorial which will enable an experienced C++ developer to code, test and deploy something as complex as
BSIP #6What parts of this know-how will you cover? What areas are you not able to cover?
EDIT: Judging from
the poll, it looks to me that your documentation is aimed at those two use-cases:
- how to use BitShares
- how to create third-party apps that interface with BitShares (e.g. mobile wallets, gateways, bridges)
And what you don't seem to cover is anything that introduces changes affecting the BitShares protocol (i.e. requiring hard-forks).
Is it a fair definition of the scope of your docs?
(If so, how does your intention to write "hello world" contracts and operations fit into this?)