📅 Original date posted:2014-03-02
📝 Original message:Peter Todd <pete at petertodd.org> wrote:
>> I proof-read rc1 and simply submitted my changes via pull-req:
>>
>> https://github.com/bitcoin/bitcoin/pull/3642
Drak responded:
> Actually, this is unnecessary since github allows editing of files directly on the site and the it will submit as a pull request. You can even update by visiting your fork (it creates this automatically and a topic branch) and make more edits and it will add to your PR. There is basically no barrier for non techy people to contribute.
Ooo, I like this. I *can* use git, but would love to be able to avoid it -- as would most non-technical contributors.
Anyway, this particular solution doesn't appear to be possible in this case, as the file isn't at https://github.com/bitcoin/bitcoin/tree/0.9.0/doc/release-notes , and I don't believe I could copy it to the repository without going the whole git route. Suggestions welcome, here or privately.
Peter writes:
> MtGox does host the bitcoin wiki, so yes, the funds probably do go to a wallet held by MtGox in some fashion.
The foolishness of sending a payment to a Mt. Gox-held wallet -- which is required to edit the wiki -- strikes me as a pressing issue. If I understand it correctly, this is a hard blocker that'll stop *all* new contributors. Further, I registered for the wiki and never got my confirmation email. Methinks the whole thing is broken. :(
Again, please to redirect me if this is inappropriate for this list. (I'm new here.) Cheers,
---
Tom Geller * Oberlin, Ohio * 415-317-1805
Writer/Presenter * http://www.tomgeller.com
articles, marketing, videos, user guides, books
Tom Geller [ARCHIVE] /
npub1us…v8dt9
2023-06-07 15:14:33
in reply to nevent1q…qvqn
Author Public Key
npub1ustl56qmqkwx5zmwqysqcjy88tg6tuyf9uld7pzylxrgvy9arajs6v8dt9Seen on
wss://relay.nostr.bandPublished at
2023-06-07 15:14:33Event JSON
{
"id": "fde922640b5e4e953cb501957b0a9c8275c6bd9cee22e1bd6ef20be402ced8fd",
"pubkey": "e417fa681b059c6a0b6e01200c48873ad1a5f0892f3edf0444f9868610bd1f65",
"created_at": 1686150873,
"kind": 1,
"tags": [
[
"e",
"599962b390e9fe2a4a394e6cc897ab4471841535babb7dd55e4bef0e2fa0dd47",
"",
"root"
],
[
"e",
"9a6b01c8702d426b94663ce047b938f0fbad32e4731fccf48e79a6dcb04bbd41",
"",
"reply"
],
[
"p",
"50ece7cbb2dc316af1cd5da0d62e0e1fec40f20919242c8fbedd53702fba95db"
]
],
"content": "📅 Original date posted:2014-03-02\n📝 Original message:Peter Todd \u003cpete at petertodd.org\u003e wrote:\n\u003e\u003e I proof-read rc1 and simply submitted my changes via pull-req:\n\u003e\u003e \n\u003e\u003e https://github.com/bitcoin/bitcoin/pull/3642\n\nDrak responded:\n\u003e Actually, this is unnecessary since github allows editing of files directly on the site and the it will submit as a pull request. You can even update by visiting your fork (it creates this automatically and a topic branch) and make more edits and it will add to your PR. There is basically no barrier for non techy people to contribute.\n\nOoo, I like this. I *can* use git, but would love to be able to avoid it -- as would most non-technical contributors.\n\nAnyway, this particular solution doesn't appear to be possible in this case, as the file isn't at https://github.com/bitcoin/bitcoin/tree/0.9.0/doc/release-notes , and I don't believe I could copy it to the repository without going the whole git route. Suggestions welcome, here or privately.\n\nPeter writes:\n\u003e MtGox does host the bitcoin wiki, so yes, the funds probably do go to a wallet held by MtGox in some fashion.\n\nThe foolishness of sending a payment to a Mt. Gox-held wallet -- which is required to edit the wiki -- strikes me as a pressing issue. If I understand it correctly, this is a hard blocker that'll stop *all* new contributors. Further, I registered for the wiki and never got my confirmation email. Methinks the whole thing is broken. :(\n\nAgain, please to redirect me if this is inappropriate for this list. (I'm new here.) Cheers,\n\n---\n Tom Geller * Oberlin, Ohio * 415-317-1805\n Writer/Presenter * http://www.tomgeller.com\n articles, marketing, videos, user guides, books",
"sig": "0a16c8e174054edcf6e9e18cb5b83255c55ad94c42ac9d380f5f27c5c7bb680e9ae5c8358d4da1c2375f2234b1a82de4e2dcb75b4edcff6974cd45f0bfd62752"
}