Bitcoin Forum
October 10, 2024, 07:48:39 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: List of people who have had commit access to Bitcoin Core  (Read 2530 times)
achow101 (OP)
Moderator
Legendary
*
expert
Offline Offline

Activity: 3514
Merit: 6856


Just writing some code


View Profile WWW
February 01, 2017, 10:19:06 PM
Last edit: July 07, 2022, 08:05:39 PM by achow101
Merited by DdmrDdmr (3), Husna QA (1), nullius (1)
 #1

I am creating this thread in response to the discussion occurring at https://bitcointalk.org/index.php?topic=1773558.msg17697805#msg17697805. This list will contain the names (or pseudonyms) of everyone who I can find evidence for ever having commit access to Bitcoin Core, the dates during which they had commit access, sources for all of this information, and reasoning for the access. Those who currently have commit access are in bold.

  • Satoshi Nakamoto (satoshi, s_nakamoto): 2009-01-03 - 2011-09-13[1] Creator, first Lead Maintainer
  • Martti Malmi (Sirius, sirius_m): 2009-08-30 - 2011-09-13[1][2]    Creator of first SVN repo
  • Laszlo (laszloh) 2010-08-04 - 2011-09-131[1]    Original OSX Builds and support
  • Gavin Andresen (gavinandresen): 2010-10-11 - 2016-05-02[3]    Frequent contributor; later Lead Maintainer
  • Chris Moore (dooglus): 2011-01-21 - 2011-03-31    Frequent contributor for some time; Still occasionally contributes
  • Pieter Wuille (sipa): 2011-05-01 - 2022-07-07    Frequent contributor
  • Jeff Garzik (jgarzik): 2011-05-06 - July/Aug 2016 [4]    Frequent Contributor
  • Wladimir J. van der Laan (laanwj, wumpus): 2011-06-05 - present[5]    Frequent contributor; later Lead Maintainer
  • Nils Schneider (tcatm): 2011-09-19 - 5/31/12    Frequent contributor for some time
  • Greg Maxwell (gmaxwell): 2012-02-11 - 2015-12-17    Frequent contributor; Gave up commit access due to toxicity and drama from the community
  • Jonas Schnelli (jonasschnelli): 2015-11-13 - 2021-10-21[6]    Frequent contributor; given access after becoming GUI Maintainer; Stepped down for personal reasons
  • Marco Falke (marcofalke): 2016-04-13 - present[7]    Frequent Contributor; given access after becoming QA/Testing Maintainer
  • Samuel Dobson (MeshCollider): 2018-12-06 - 2021-09-12[8]    Frequent Contributor; given access after volunteering to be the wallet maintainer; Stepped down to focus on his PhD
  • Michael Ford (fanquake): 2019-06-08 - present[9]    Frequent Contributor; given access after being nominated by several other frequent contributors and maintainers to become a maintainer.
  • Hennadii Stepanov (hebasto): 2021-04-19 - present  Frequent Contributor; given access after volunteering to help maintain the GUI
  • Andrew Chow (achow101): 2021-12-20 - present[10]     Frequent Contributor; given access after volunteering to be the wallet maintainer.
  • Gloria Zhao (glozow): 2022-07-07 - presentt[11]    Frequent contributor, given access after being nominated by several frequent contributors and maintainers to become a maintainer.

Footnotes:
  • [1] The move to Github occurred before the last SourceForge commit, but the last SourceForge commit declares sourceforge as dead. Presumably those who only committed to SourceForge no longer had commit access after the move
  • [2] Sirius was the one who created the original SVN repo on SourceForge.
  • [3] Gavin was the Lead Maintainer from 2011-02-23 until 2014-04-07
  • [4] I cannot find anything that suggests that Jeff Garzik has given up his commit access or has had it revoked I was informed via IRC PM by some of the Core devs that Jeff's commit access was revoked some time around August 2016 after several months of inactivity.
  • [5] Wladimir is the current Lead Maintainer. After participating in that role for a long time, he was officially given the position by Gavin on 2014-04-07
  • [6] Jonas is currently the GUI Maintainer. After participating in that role for a long time, he was officially given the position by Wladimir on 2015-11-13. He stepped down for personal reasons.
  • [7] Marco is currently the QA/Testing Maintainer. After participating in that role for a long time, he was officially given the position by Wladimir on 2016-04-13
  • [8] MeshCollider was the Wallet Maintainer. He had been contributing for a while, particularly to wallet related things. When laanwj asked if anyone would like to be the role of Wallet Maintainer, MeshCollider volunteered. He url=https://twitter.com/meshcollider/status/1469024214535393282]stepped down[/url] to focus on his PhD.
  • [9] fanquake is currently the Build System Maintainer as well as a general maintainer. He had been contributing for a while, particularly with updating dependency versions and build system related things. He also had been doing a lot of janitorial things in the repo such as tagging issues, closing old issues and PRs, nominating things to be merged, etc. At the CoreDev event in Amsterdam which several maintainers and contributors attended, he was nominated to be a maintainer by the entire group.
  • [10] achow101 has contributed to the project for many years, especially in wallet and PSBT-related areas. After meshcollider stepped down from the Wallet Maintainer role, achow101 volunteered to taked up the role.
  • [11] glozow has contributed to the project for a few years, particularly in the mempool and node policy areas. She was nominated by fanquake to be a maintainer with focus in those areas.

Other Notes:
  • Dates are Year-Month-Day
  • There may be people missing and dates may be slightly incorrect. These are all that I can determine by looking at old emails and the commit history. Please let me know if anything is incorrect
  • The start date is determined by the first merge commit made by that person. The end date is determined by the date of the last merge commit made by that person or other announcements of commit access revocation.



After scrolling through nearly the entire git merges history, I have found a couple of interesting things.

Satoshi did not use a Version Control System originally. The releases and source code were originally in a rar file that was uploaded to bitcoin.org. Sirius had to setup the original SVN repository on SourceForge for him. This was then later migrated to GitHub by Gavin. Originally patches were authored by developers and then emailed to Satoshi, Sirius, or Gavin who then committed the changes to the source tree with the commit message containing the attribution, but not the actual commit itself.

Another interesting fact is that the giving out of commit access has become more strict. It is now a privilege held by those given maintainer positions and those whose privilege was grandfathered in (i.e. they had it previously and kept it, until otherwise revoked). Previously it was simply given out to those who contributed frequently and revoked after they stopped contributing. This appears to be no longer the case, although there are still multiple people who can commit to the repository so that there is not any reliance on one person. The maintainers are still given to frequent contributors as the maintainers are frequent contributors to the set of functionality for which they are maintainers of. They received the positions because of frequent contributions to those functionalities. Of those whose commit access was grandfathered, only Pieter Wuille remains - the rest were revoked eventually primarily for the lack of contributions (see each individual for their specific reason).

Lastly, I could not find any evidence for Satoshi ever publicly announcing that Gavin was to be the Lead Maintainer after him. It seems that Gavin was already a frequent contributor and already had commit access for a while before Satoshi disappeared. After Satoshi disappeared and Sirius stopped contributing as much, Gavin simply took over the role as lead maintainer as he was the only frequent contributor with commit access.



Edits: This has been posted to reddit where the people on this list are more active.
This list has been posted on Bitcoin stackexchange as well
Dooglus -> dooglus
Jeff's commit access was revoked a while ago
Bolded active contributors
Clarified how maintainers got their roles

Carlton Banks
Legendary
*
Offline Offline

Activity: 3430
Merit: 3080



View Profile
February 01, 2017, 10:21:53 PM
 #2

You were also asked to provide reasons why the commit keys were given to each person. Still researching that? Cheesy

Vires in numeris
achow101 (OP)
Moderator
Legendary
*
expert
Offline Offline

Activity: 3514
Merit: 6856


Just writing some code


View Profile WWW
February 01, 2017, 10:33:15 PM
 #3

You were also asked to provide reasons why the commit keys were given to each person. Still researching that? Cheesy
Fixed that. Really the only reason is "frequent contributor". Now, if you are a frequent contributor to a specific set of functionality, you become the maintainer for that stuff and get commit access. But still, it is for being a frequent contributor.

Carlton Banks
Legendary
*
Offline Offline

Activity: 3430
Merit: 3080



View Profile
February 01, 2017, 10:42:48 PM
 #4

Presumably you discovered this when you asked the question to every person who has generated a key for someone else? In other words, you can't really do anything except make a prosaic supposition, the real intentions are not really knowable information.

Vires in numeris
gmaxwell
Moderator
Legendary
*
expert
Offline Offline

Activity: 4242
Merit: 8702



View Profile WWW
February 02, 2017, 06:21:08 AM
 #5

Quote
having been given the position

I think it would be more correct to say that it was recognized that he was already doing it.  Appointed positions often don't make sense in Open Source, because it matters a lot more what people do than some kind of title. 
Karartma1
Legendary
*
Offline Offline

Activity: 2310
Merit: 1422



View Profile
February 02, 2017, 07:17:49 AM
 #6

Quote
having been given the position

I think it would be more correct to say that it was recognized that he was already doing it.  Appointed positions often don't make sense in Open Source, because it matters a lot more what people do than some kind of title. 
I would like it to be framed somewhere as it is the only thing that matters, really.
RocketSingh
Legendary
*
Offline Offline

Activity: 1662
Merit: 1050


View Profile
November 26, 2017, 10:36:08 PM
 #7

Has there been any formal announcement about revoking Gavin & Jeff's commit access?

achow101 (OP)
Moderator
Legendary
*
expert
Offline Offline

Activity: 3514
Merit: 6856


Just writing some code


View Profile WWW
November 27, 2017, 12:12:00 AM
 #8

Has there been any formal announcement about revoking Gavin & Jeff's commit access?
No.

gmaxwell
Moderator
Legendary
*
expert
Offline Offline

Activity: 4242
Merit: 8702



View Profile WWW
November 27, 2017, 05:15:41 AM
Merited by ABCbits (1)
 #9

Has there been any formal announcement about revoking Gavin & Jeff's commit access?
No.
Not so, WRT Gavin: http://laanwj.github.io/2016/05/06/hostility-scams-and-moving-forward.html   AFAIK similar applies to Jgarzik. (Too bad, I wish it hadn't been removed years ago so that it could be removed now with a public condemnation of his ICO scam)
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!