{"thread":{"id":"26740","subject":"Question about used Workflows.","startedAt":"2011-03-15T13:43:31Z","lastAt":"2011-03-15T17:57:13Z","messageCount":3,"participants":["Valentin Haenel","Andreas Ericsson","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"163390","messageId":"20110315134331.GA5165@kudu.in-berlin.de","threadId":"26740","inReplyTo":null,"subject":"Question about used Workflows.","fromName":"Valentin Haenel","fromEmail":"valentin@fsfe.org","sentAt":"2011-03-15T13:43:31Z","receivedAt":"2011-03-15T13:43:31Z","isPatch":false,"sender":{"key":"valentin@fsfe.org","avatar":null},"body":"Dear Git developers and contributors,\n\nI was wondering what kind of workflow the Git project itself uses. From\nwhat I gather much of the development takes place using the list, and\npatches sent by mail. Do any of the core contributers maintain public\ndeveloper repos? And how many developers on average have push privileges\nto http://git.kernel.org/?p=git/git.git;a=summary?\n\nthanks\n\nValentin\n"},{"id":"163391","messageId":"4D7F7465.8000307@op5.se","threadId":"26740","inReplyTo":"20110315134331.GA5165@kudu.in-berlin.de","subject":"Re: Question about used Workflows.","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2011-03-15T14:15:01Z","receivedAt":"2011-03-15T14:15:01Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"On 03/15/2011 02:43 PM, Valentin Haenel wrote:\n> Dear Git developers and contributors,\n> \n> I was wondering what kind of workflow the Git project itself uses. From\n> what I gather much of the development takes place using the list, and\n> patches sent by mail.\n\nThat's correct.\n\n> Do any of the core contributers maintain public\n> developer repos?\n\nSome do, although most contributions are still sent as patches for\npublic discussion and then taken from there by Junio who has some\nnifty routine for that already.\n\nSubpart maintainers, such as the gitk author Paul Mackerras (spelling?)\nhave repos of their own from which Junio pulls on request. Normally\nthat's in parts where Junio feels his knowledge lacking and he trusts\nthe subpart maintainer. From what I've gathered, Tcl isn't Junio's\nstrong point.\n\n> And how many developers on average have push privileges\n> to http://git.kernel.org/?p=git/git.git;a=summary?\n> \n\nThere's no \"average\" to it. Linus probably still has push access as\nhe's the founding father and first maintainer. Junio ofcourse has it\nas the current maintainer. Shawn Pearce has taken over maintenance\na few times when Junio has been absent for one reason or another. I\ndoubt push privileges have been revoked in between absences. Oh, and\nofcourse the kernel.org admin team have more or less implicit access\nto push, although the git community would certainly frown quite hard\nif they ever (ab)used their admin powers to do that.\n\nAll that aside; By peer etiquette and for simplicity reasons, only\nthe current maintainer ever pushes anything to kernel.org. Noone\nbecomes maintainer (or kernel.org admin) without having invested a\nlot of time and shown a lot of devotion to the project.\n\nFor some public credit, Junio's doing a great job both maintaining\nand choosing interim maintainers. I've rarely seen an opensource\nproject where the maintainer so rarely (ever?) get annoyed at\nanything and keeps everything running smoothly.\n\n-- \nAndreas Ericsson                   andreas.ericsson@op5.se\nOP5 AB                             www.op5.se\nTel: +46 8-230225                  Fax: +46 8-230231\n\nConsidering the successes of the wars on alcohol, poverty, drugs and\nterror, I think we should give some serious thought to declaring war\non peace.\n"},{"id":"163402","messageId":"7voc5c9shy.fsf@alter.siamese.dyndns.org","threadId":"26740","inReplyTo":"20110315134331.GA5165@kudu.in-berlin.de","subject":"Re: Question about used Workflows.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2011-03-15T17:57:13Z","receivedAt":"2011-03-15T17:57:13Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Valentin Haenel <valentin@fsfe.org> writes:\n\n> I was wondering what kind of workflow the Git project itself uses. From\n> what I gather much of the development takes place using the list, and\n> patches sent by mail. Do any of the core contributers maintain public\n> developer repos? And how many developers on average have push privileges\n> to http://git.kernel.org/?p=git/git.git;a=summary?\n\nOnly I push into that repository, but first of all, everybody should stop\nthinking \"push\" as a privilege.  That repository is like \"my\" home, and\nthe statement \"I have a privilege to enter my home\" does not have much\nmeaning.  It may be technically correct, but other people have the same\nprivilege to enter their homes (i.e. have their own public repositories\nthat only they can push into, and others can pull their work from there),\nso it is not noteworthy.\n\nChanges are reviewed on the list in patch form, and most of the time I've\nbeen applying these changes to my tree and pushing the results out to my\npublic repository, but from time to time, other people do give me a pull\nrequest, and I pull from them to integrate their work. The result again is\npublished by pushing it out to my public repository.\n\nIn a distributed world, the \"primary\" repository exists only by social\nconvention. My repository happens to be the primary one for now, but if\nsomebody wants to fork git and starts making a lot of good changes at a\nrapid pace that neither I nor the current list reviewers can keep up with,\nthe repository of that person may become a more popular source of the\ncutting-edge version of git, and if that continues, it may become the\n\"primary\" one, at which point the list (including me) may decide that it\nis a good idea to turn the maintainership to that new person.\n\nWhen I had to leave the net for extended period of time (which happened a\nfew times in the past), I don't give the key to my home (\"push privilege\")\nto an interim maintainer. Instead, the interim maintainer keeps his own\npublic repository (\"his home\"), and pushes to that repository by playing\nexactly the same role as I do, picking up well-reviewed patches from the\nmailing list and responding to pull requests. In the meantime, people work\noff of his repository. When I come back, I can pull from the interim\nmaintainer and the continuity of the end-result history is maintained.\n"}]}