Namecoin Forum

Okay, we can't have both a branch AND a different repo, it's really confusing. If Phelix/Domob really wants a new repo, I'm fine with that but we can't have both. Can someone either rename the namecore repo "namecoin-core" and remove the branch on namecoin/namecoin or remove the namecore repo and pu...

I'd like to make several changes to build-osx.md . What changes do you want to make Cassini? I personally don't think it's worth altering the build notes just for small changes (like using "namecoin" instead of "bitcoin") ... users who would get confused by small stuff probably shouldn't be using t...

Ah cool, I didn't know about that. So you are talking about a guide to the additional APIs and name scripts? I thought it was about the actual code and internal database structure of Namecoin Core - which seems to be not the subject of the Bitcoin guide. Well, I think we should have a developer ori...

cassini wrote:

indolering wrote:Bitcoin has a very nice developers guide

Is it this the official version? https://bitcoin.org/en/developer-reference

Yes.

Discussion from an email correspondence with Domob: Sounds like a noble project, as long as you have time to spend on that. If you have any questions, feel free to ask me. I was going to contribute a description of how name registration works and stub out the rest. FWIW, I would be happy to spend an...

... but we would have to use submodules or subtrees for any auto-generated API documentation. So I guess the main advantage is the ability to use Github's static site hosting.

FWIW, I was thinking we would stub out most of the documentation at first.

Jekyll is better for this. That way anyone can contribute, but an ACK from a developer is needed. You can submit a pull request for a wiki, but I'm open to having a developer guide repo as well. I would just make it a subdirectory (or maybe a Git Submodule) of the main Jekyll site. Easier to deal w...

biolizard89 wrote: Jekyll is better for this. That way anyone can contribute, but an ACK from a developer is needed.

You can submit a pull request for a wiki, but I'm open to having a developer guide repo as well.

Congratulations Domob!

I think the Jekyll port is very important because it fits with the Github workflow and it makes it easier to contribute new content.