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

Re: OT: mail-based interfaces and web-based interfaces (Re: Extract

From
EWEric Wong <normalperson@yhbt.net>
Date
Jul 26, 2012, 03:10 UTC
Message-ID
<20120726031048.GA8034@dcvr.yhbt.net>
In-Reply-To
<5010AC7B.6020805@pobox.com>
Michael G Schwern <schwern@pobox.com> wrote:
Show 14 quoted lines
> On 2012.7.25 4:48 PM, Eric Wong wrote:
> > We need to use something.  Right now our choice of mailer is the best
> > choice for _existing_ contributors.
> 
> I believe this entire discussion can be reduced to that right there.
> 
> If your process is optimized for existing contributors, it will work well for
> existing contributors, who will want to optimize it for themselves.  Repeat.
> If the main way you evaluate your process is asking "is this more convenient
> for me" then you're probably in that spiral.
> 
> This creates a process very well tuned to the existing contributors, and its
> very convenient for them.  But the consequence is it becomes more and more
> work for a new contributor to join.

The process is _not_ a lot of work. At least no more than any other project: observe the regulars -> imitate the regulars

Many/most regular git contributors are not Linux kernel developers, yet were able to quickly able to get up-to-speed with git. AFAIK, the Linux kernel gets plenty of new contributors every year, too.

> Before talking about anything else, the existing contributors have to ask
> themselves a simple question:  Do we care about getting new contributors?

Yes, if contributors are willing to learn/respect existing conventions. We do take time to help new contributors out :)

For me, it's certainly "no" if there's any endorsement of non-Free Software or centralized/commercial services involved.

> The answer can be "no" ("yes, but not if I'm inconvenienced" is a no).  Maybe
> you're happy with the people you've got.  But there's no point in getting into
> detail until that's settled.
Previous: Jonathan Nieder
Message 34 of 34 in “Fix git-svn tests for SVN 1.7.5.”
  1. Michael G SchwernJul 17, 2012
  2. Jonathan NiederJul 17, 2012
  3. Michael G SchwernJul 17, 2012
  4. Extract Git classes from git-svn (4/10) (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  5. Extract Git classes from git-svn (5/10) (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  6. Find .pm files automatically (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  7. Jonathan NiederJul 18, 2012
  8. Michael G SchwernJul 18, 2012
  9. Jonathan NiederJul 18, 2012
  10. Extract Git classes from git-svn (2/10) (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  11. Jonathan NiederJul 18, 2012
  12. Eric WongJul 18, 2012
  13. Michael G SchwernJul 19, 2012
  14. Extract Git classes from git-svn (3/10) (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  15. Jonathan NiederJul 18, 2012
  16. Extract Git classes from git-svn (6/10) (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  17. Extract Git classes from git-svn (7/10) (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  18. Extract Git classes from git-svn (8/10) (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  19. Extract Git classes from git-svn (9/10) (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  20. Extract Git classes from git-svn (10/10) (was Re: Fix git-svn tests for SVN 1.7.5.)Michael G Schwern, Jul 17, 2012
  21. Ben WaltonJul 21, 2012
  22. Jonathan NiederJul 17, 2012
  23. Junio C HamanoJul 18, 2012
  24. Thiago FarinaJul 19, 2012
  25. Michael G SchwernJul 24, 2012
  26. Jonathan NiederJul 24, 2012
  27. Eric WongJul 25, 2012
  28. Michael G SchwernJul 25, 2012
  29. OT: mail-based interfaces and web-based interfaces (Re: Extract Git classes from git-svn (1/10))Jonathan Nieder, Jul 25, 2012
  30. Michael G SchwernJul 25, 2012
  31. Eric WongJul 25, 2012
  32. Michael G SchwernJul 26, 2012
  33. Jonathan NiederJul 26, 2012
  34. Eric WongJul 26, 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.