📅 Original date posted:2011-09-19
🗒️ Summary of this message: Alex suggests maintaining an index similar to Python's PEPs for organizing Bitcoin development. He recommends continuing with the current system and considering alternative organization voting around the time of 0.5 release.
📝 Original message:http://www.python.org/dev/peps/ is a good reference if you're
interested in seeing how PEPs work in action. I would be more than
willing to maintain a similar index if that's what people want.
Something to note is that Python does not use Git or GitHub (AFAIK).
So we would need to update 001 to reflect the BEP involvement with
Git, or transition away from it completely (which I discourage).
My full-time experience as a project manager with Basecamp, Redmine,
Teamlab, Pivotal Tracker, SVN, and custom VC has taught me that it is
hard to find a good solution for the organization of the development
life cycle. Having examined Bitcoin for the past three weeks, it is
hard to discern the willingness to implement meta changes.
It looks like Git/GitHub is working, but not ideal for everyone. My
opinion is that there will always be a missing feature in VC systems.
My major gripes with GitHub are the lack of prioritization options,
voting system, and reporting/metrics.
Gavin has asked me to research various O/S projects, to see how they
are doing things. I have been focused mostly on organizing a pull
testing system, and learning the testing process - but I can spend
more time on meta organization if that is in demand. It would be
helpful to me if I could hear some feedback on what needs changing,
and how important it is.
My recommendation is that we continue with the current system, but
plan alternative organization voting around the time of 0.5 release.
This could be an alternative to GitHub, or a supplement, or neither.
Seeing as we are still in Beta, I don't believe there needs immense
structure until we approach 1.0. The PEP system is outstanding, and is
clearly a solid alternative/supplement to consider.
-Alex
Alex Waters [ARCHIVE] /
npub12t…vf5r2
2023-06-07 02:27:50
in reply to nevent1q…aspk
Author Public Key
npub12ttgf3crmvnayzst9clhmssu6z0mkvpgpznzjdjkn8kcqre9zkhqmvf5r2Seen on
wss://relay.nostr.bandPublished at
2023-06-07 02:27:50Event JSON
{
"id": "0d2e6fd80e3eb212ce38430569f5fab5b15b2efeb9f746b6886c55612790244e",
"pubkey": "52d684c703db27d20a0b2e3f7dc21cd09fbb302808a629365699ed800f2515ae",
"created_at": 1686104870,
"kind": 1,
"tags": [
[
"e",
"69c8edef88454bdc1998d9bc13760e0b225e8ae8a8951ba49d59572557634d62",
"",
"root"
],
[
"e",
"af2100c4d810efaeb86f62144c803b3a62819f8ac2c24a06bb3854d48e95b764",
"",
"reply"
],
[
"p",
"6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1"
]
],
"content": "📅 Original date posted:2011-09-19\n🗒️ Summary of this message: Alex suggests maintaining an index similar to Python's PEPs for organizing Bitcoin development. He recommends continuing with the current system and considering alternative organization voting around the time of 0.5 release.\n📝 Original message:http://www.python.org/dev/peps/ is a good reference if you're\ninterested in seeing how PEPs work in action. I would be more than\nwilling to maintain a similar index if that's what people want.\n\nSomething to note is that Python does not use Git or GitHub (AFAIK).\nSo we would need to update 001 to reflect the BEP involvement with\nGit, or transition away from it completely (which I discourage).\n\nMy full-time experience as a project manager with Basecamp, Redmine,\nTeamlab, Pivotal Tracker, SVN, and custom VC has taught me that it is\nhard to find a good solution for the organization of the development\nlife cycle. Having examined Bitcoin for the past three weeks, it is\nhard to discern the willingness to implement meta changes.\n\nIt looks like Git/GitHub is working, but not ideal for everyone. My\nopinion is that there will always be a missing feature in VC systems.\nMy major gripes with GitHub are the lack of prioritization options,\nvoting system, and reporting/metrics.\n\nGavin has asked me to research various O/S projects, to see how they\nare doing things. I have been focused mostly on organizing a pull\ntesting system, and learning the testing process - but I can spend\nmore time on meta organization if that is in demand. It would be\nhelpful to me if I could hear some feedback on what needs changing,\nand how important it is.\n\nMy recommendation is that we continue with the current system, but\nplan alternative organization voting around the time of 0.5 release.\nThis could be an alternative to GitHub, or a supplement, or neither.\nSeeing as we are still in Beta, I don't believe there needs immense\nstructure until we approach 1.0. The PEP system is outstanding, and is\nclearly a solid alternative/supplement to consider.\n\n-Alex",
"sig": "9cdba3ac32a11cc7d3000fda4979fac7ff95a258eaf099cd5251a8da80a350c58c012ded34f498cdf037dc0a53679be9f108d08aaa06e51300988466a221f5b4"
}