git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] Questions for "Git User's Survey 2011"

From
Jakub Narębski <jnareb@gmail.com>
Date
Sep 24, 2012, 16:11 UTC
Message-ID
<CANQwDwe1H3Va5T7uy6zUJ0oz_mk0=fW8hK_buky4x4hMThY9UQ@mail.gmail.com>
In-Reply-To
<vpqobkvxwhq.fsf@grenoble-inp.fr>

On Mon, Sep 24, 2012 at 5:37 PM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:

Show 17 quoted lines
> Jakub Narębski <jnareb@gmail.com> writes:
>
>> I have created short (well, at least shorter than previous ones)
>> "Git User's Survey 2012" on Survs.com.  The test channel is
>>
>>   https://www.survs.com/survey/J87I3PDBU4
>
> If it's still time, it would be nice to add a question on the kind of
> workflow people use. E.g.
>
> Which workflow do you use? (never / rarely / often / always)
>
> Centralized workflow (everyone pushes and pulls to the same shared
> repository).
>
> One-repository per developer (people push to their own public
> repository, and pull from other user's public repository)

You were not the only one to ask for question about workflows used; Junio also asked for something similar.

I have therefore added the following multiple-choice question:

#19. What git workflow(s) is used by projects in which development you participate? [ ] single developer, only private repository (no interaction) [ ] centralized workflow (push to common repository) [ ] branched centralized (push to different branches in common repository) [ ] peer-to-peer workflow (all repositories roughly equal) [ ] integration-manager workflow (maintainer pulls/applies patches to "blessed" repository)) [ ] dictator and lieutenants workflow (hierarchical workflow) [ ] using collaborative code review tool, e.g. Gerrit [ ] other workflow, please explai

I was also thinking about adding merge vs rebase question, but it is direction orthogonal to above, so maybe as separate question...

-- 
Jakub Narebski
Previous: Matthieu MoyNext: Matthieu Moy
Message 29 of 35 in “[RFC] Questions for "Git User's Survey 2011"”
  1. Jakub NarebskiJul 25, 2011
  2. Phil HordJul 25, 2011
  3. Jakub NarebskiJul 26, 2011
  4. Phil HordJul 26, 2011
  5. Felipe ContrerasJul 31, 2011
  6. Jakub NarebskiAug 1, 2011
  7. David AguilarSep 3, 2011
  8. Jakub NarebskiSep 3, 2011
  9. David AguilarSep 3, 2011
  10. Felipe ContrerasJul 31, 2011
  11. Jakub NarebskiAug 2, 2011
  12. Heiko VoigtAug 1, 2011
  13. Jakub NarebskiAug 2, 2011
  14. Jens LehmannAug 2, 2011
  15. Jakub NarebskiAug 3, 2011
  16. Ævar Arnfjörð BjarmasonAug 3, 2011
  17. Jakub NarębskiAug 3, 2011
  18. Felipe ContrerasSep 3, 2011
  19. Jakub NarebskiSep 3, 2011
  20. Felipe ContrerasSep 14, 2011
  21. Jakub NarebskiSep 14, 2011
  22. Felipe ContrerasSep 19, 2012
  23. Jakub NarębskiSep 22, 2012
  24. Junio C HamanoSep 23, 2012
  25. Jakub NarębskiSep 23, 2012
  26. Michael J GruberSep 24, 2012
  27. Jakub NarębskiSep 24, 2012
  28. Matthieu MoySep 24, 2012
  29. Jakub NarębskiSep 24, 2012
  30. Matthieu MoySep 24, 2012
  31. Jakub NarębskiSep 24, 2012
  32. Matthieu MoySep 24, 2012
  33. Jakub NarębskiSep 24, 2012
  34. Matthieu MoySep 25, 2012
  35. Jakub NarębskiSep 25, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.