📅 Original date posted:2011-08-10
🗒️ Summary of this message: Developers want to work on new features, not just bug fixes. A development branch could help relieve pressure and encourage personal investment in the project.
📝 Original message:On Wed, Aug 10, 2011 at 3:32 PM, Andy Parkins <andyparkins at gmail.com> wrote:
> People get itches and they want to scratch them. They aren't paid, so they
> don't necessarilly want to turn up and be told which part they _should_ be
> working on. The choice is not "bug fix that Gavin wants" or "new feature
> that New Developer wants", it is "New Feature" or nothing.
This is true -- though there is value to having a list of "things we
think people should focus on" for the motivated, and for new people
interested in tackling a project, but not sure what project to tackle.
>> there would be less pressure to help with the boring bug-fixing and
>> testing of the bug-fix branch, which I think would be bad.
>
> That pressure might be relieved if the community were able to grow a bit,
> and people felt they had a personal investment. That means loosening the
> reigns a bit; and perhaps a development branch would be the way to do that
> while not compromising code quality.
A centrally managed development branch on bitcoin/bitcoin.git is not
the way to do it, however. See the description of linux-next, in my
previous email, for a more distributed method which can easily be
layered on top of the existing bitcoin dev structure by any motivated
volunteer(s).
Think distributed. :) The community does not need Linus's help
(linux-next) or Gavin's help (bitcoin-next) to do this. linux-next
became so widely used and useful that Linus requires almost all
changes to be first staged in linux-next.
--
Jeff Garzik
exMULTI, Inc.
jgarzik at exmulti.com
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 02:14:09
in reply to nevent1q…kcdt
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Seen on
wss://relay.noswhere.comPublished at
2023-06-07 02:14:09Event JSON
{
"id": "63a3ab94986b6f7a18ced2dbe0dbf29b727ae8e5e377e796bbd08b156d589d5e",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686104049,
"kind": 1,
"tags": [
[
"e",
"fe8ae56772ad6135ef8f3cc5e223de1011f21616a51d5302085d2b9ebf339345",
"",
"root"
],
[
"e",
"b0d9e40831b62c1ac885199079fb70734c8a9cc16b3f166deece24e7676e357e",
"",
"reply"
],
[
"p",
"99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59"
]
],
"content": "📅 Original date posted:2011-08-10\n🗒️ Summary of this message: Developers want to work on new features, not just bug fixes. A development branch could help relieve pressure and encourage personal investment in the project.\n📝 Original message:On Wed, Aug 10, 2011 at 3:32 PM, Andy Parkins \u003candyparkins at gmail.com\u003e wrote:\n\u003e People get itches and they want to scratch them. They aren't paid, so they\n\u003e don't necessarilly want to turn up and be told which part they _should_ be\n\u003e working on. The choice is not \"bug fix that Gavin wants\" or \"new feature\n\u003e that New Developer wants\", it is \"New Feature\" or nothing.\n\nThis is true -- though there is value to having a list of \"things we\nthink people should focus on\" for the motivated, and for new people\ninterested in tackling a project, but not sure what project to tackle.\n\n\u003e\u003e there would be less pressure to help with the boring bug-fixing and\n\u003e\u003e testing of the bug-fix branch, which I think would be bad.\n\u003e\n\u003e That pressure might be relieved if the community were able to grow a bit,\n\u003e and people felt they had a personal investment. That means loosening the\n\u003e reigns a bit; and perhaps a development branch would be the way to do that\n\u003e while not compromising code quality.\n\nA centrally managed development branch on bitcoin/bitcoin.git is not\nthe way to do it, however. See the description of linux-next, in my\nprevious email, for a more distributed method which can easily be\nlayered on top of the existing bitcoin dev structure by any motivated\nvolunteer(s).\n\nThink distributed. :) The community does not need Linus's help\n(linux-next) or Gavin's help (bitcoin-next) to do this. linux-next\nbecame so widely used and useful that Linus requires almost all\nchanges to be first staged in linux-next.\n\n-- \nJeff Garzik\nexMULTI, Inc.\njgarzik at exmulti.com",
"sig": "274227859ffecca63a079800a60e104bff456414452103397db5469c484984889f1c828b82cb66dcad1ccd5808c555fc08679ab039501185bee19ddbc88460b3"
}