Thanks Mike for this opportunity to work on improving bitcoinj.org . I'm glad to read positive feedback so far. bitcoinj is a very valuable project for the Bitcoin universe  . |
|
|
|
|
Cyrus / gwb3 : That's awesome, many thanks!!
|
|
|
|
The website is purely static and for security reasons I think it should stay that way. If there is a third party commenting platform that lets us just drop something in via Javascript, I think that'd be OK but not if we need to run some kind of php/ruby thing on the bitcoin.org server itself.
Agreed, no server-side scripting for now. |
|
|
|
Unfortunately, I'm still catching up so I'm afraid I cannot add much to this project yet.
Actually, reviews would be very useful at this point. If you can spot any confusing text, inaccuracies, typos, etc, please make a pull req or report them as an issue. That'll be very much appreciated. Few suggestions:
- For new developers, maybe it makes sense to have a bit more general information. For example, using bitcoin-cli, RPC or using bitcoind as border router.
- Would it be an idea to have 'user contributed notes' under each section?
Thanks! Actually if you want to work on the API reference page, that should probably be it. As for the "user contributed notes", can you further explain your idea? |
|
|
|
|
Latest update: The first draft for the Transaction subsection is there:
(Merged)
Reviews are appreciated (only errors, omissions, confusions, and other issues at this point, writing style improvements can be done later ).
|
|
|
|
The content on bitcoin.org is already under MIT (see the copyright notice at the bottom), which is a very permissive license (AFAIK, I'm no expert with licensing). |
|
|
|
We definitely need a section on the payment protocol, which merges together all the BIPs and best practices into a living document. BIPs are great but they are written as "delta to previous behaviour" which can make figuring out the systems final state harder than it should be.
Yup, I called this subsection "Payment requests". Just let me know if you feel anything is missing (or isn't relevant enough to be mentionned). I just updated the initial thread to provide clearer procedures and instructions for anyone to take part in discussions, submit work and see assigned tasks. |
|
|
|
I will probably leave this to more technical hands but I might be able to find some good points here and there so reporting in
PM'd, thanks! |
|
|
|
Update: Developer documentation has been merged on bitcoin.org: https://bitcoin.org/en/developer-documentation-- The goals of this project is to improve access to good quality documentation for developers. A lot of useful information is spread accross wiki pages, BIPS GitHub pages and BitcoinTalk threads. It would be nice to gather all this information in a single place with a consistent structure or a set of pages with a single table of content. A good "API Reference" page with code snippets would be useful too. Good writers are needed to make this project happen. If you can help with this project, please PM me or comment on this thread. Some of this work can be paid work as the Foundation is providing a 2000$ monthly bounty ( some of it is already assigned to server and translation expenses ). Work is already ongoing but needs more contributors to be completed. Not just writers, actually a lot of work will be to review, discuss, edit and organize all of this information. Live previewYou can preview current work in progress here: (Merged) General DiscussionsYou can join general discussions on this Google group: https://groups.google.com/forum/#!forum/bitcoin-documentationStyle GuideGeneral writing guidelines are discussed and edited here: https://github.com/bitcoin/bitcoin.org/wiki/Documentation-Style-Guide
|
|
|
|
|
Latest update: Spanish translations have been published (thanks to gwd3 and Spanish translators) and Hungarian translations should follow soon.
|
|
|
|
|
There has been some discussion about sponsoring bitcoin.org and the Foundation has been willing to offer a 6 month sponsorship as a part of their grant process before March 1st. This idea sounds good to me, so I'm starting this thread to see if anybody wants to share some thoughts on this matter.
This sponsorship would be used to pay for server expenses, translation bounties, or any other significant work done on bitcoin.org, and could potentially be renewed over time. Sponsorship link would look as follow: (edit, now live) . Commercial sponsorship is also another option which could be considered in the future.
For the record, the Foundation is not gaining any control or influence over the domain, server or content of the website. And as far as I'm concerned, I think bitcoin.org should remain independent and open-source.
Any thoughts?
|
|
|
|
Many of the regulators who will soon be issuing regulation and even new law don't fully understand the potential of the protocol and you know where they are getting their info: From the press whose main mission is selling enough eyeballs to their advertisers ( with sensational 'link-baiting' headlines) in an effort to keep their operations afloat. The community needs to reach out and EDUCATE or as we have seen it will be done for us! Write a letter to your state legislator, write a letter your federal legislator. Explain to them simply how the protocol works, explain to them the benefits it can offer to society, explain to them how you use it. Then explain to them how we as a community are being criminalized by the illicit activity of the bad actors. The fact is decentralized virtual currency like bitcoin with an open, public ledger is the LAST place a criminal would want to launder money - which is the MAIN concern of government. Refer them to the many academics like Sarah Meiklejohn and her team who are doing studies of the blockchain: "A Fistful of Bitcoins: Characterizing Payments Among Men with No Names" http://cseweb.ucsd.edu/~smeiklejohn/files/login13.pdfThis is a DECENTRALIZED community. You can't rely on the bitcoin foundation or the bitcoin center or the bitcoin embassy etc to do it for you. We must each do our part and make an effort engage the decision makes to help then allay their fears and increase their understanding of this truly revolutionary technology. Couldn't agree more with this. |
|
|
|
|
it seems the FAQ is taking longer to translate for a lot of translators. So I just added instructions to allow translations to be published faster without the FAQ:
"It is possible to ignore the FAQ in order to publish translations faster. Just search for the "nofaq" tag in the Transifex search bar to translate/review everything except the FAQ. The FAQ is a very useful piece of texts but it is a very long page, it can be completed and published at a later time."
--
Is there a good Spanish speaker who would like to review translations? Spanish translations is a special case, translated by a large number of people, it would be nice to make sure these texts are consistent and properly reviewed before publishing them.
|
|
|
|
Hi guys, I took the info from the above posts and combined them into this wiki page. 1. Please make sure your conference is there, and add any missing details. If you need wiki access, this is how you get it. 2. New posters - please update on the wiki as well as here. Thanks for this! |
|
|
|
140 strings translated
Cool! Perhaps @kain35m can help you with Norwegian translation? |
|
|
|
|
Show Posts
