Namecoin Forum

• Continuous integration server.
• Automated builds with code signing and pushing to Archive.org mirror.
• Maintainer for distro repositories.
• Reproducible builds based on Bitcoin's setup.
• Unit tests (not sure how to break this up).
• Abstract description of the code (basic overview of all the moving parts and how it interacts with the Bitcoin internals).
• Automatic documentation generation from code comments.
• Value encryption.
• Miner for Libcoin.
• Wallet code for Libcoin.
• RPC calls for Libcoin.
• Value encryption for Libcoin.
• Json-RPC calls for all CLI commands.
• Getting all Facebook/Twitter accounts under one roof.
• Setup planet feed of all dev blogs as well as news stories on Namecoin.
• Theme(s) for drupal, mediawiki, and phpBB.

indolering wrote:

• Json-RPC calls for all CLI commands.

domob wrote:These are very nice ideas, thanks for compiling them!

indolering wrote:

• Json-RPC calls for all CLI commands.

Can you clarify what you mean with that? I presume that everything available with "namecoind" on the command-line can be done via JSON-RPC, too. Or is this not yet the case?

indolering wrote:

domob wrote:These are very nice ideas, thanks for compiling them!

indolering wrote:

• Json-RPC calls for all CLI commands.

Can you clarify what you mean with that? I presume that everything available with "namecoind" on the command-line can be done via JSON-RPC, too. Or is this not yet the case?

I was referring to the concerns raised on yanking the GUI client, apparently some API calls would need to be added to the RPC API for a functional client. I assumed that the CLI exposed those calls but I could be wrong.