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

Re: [DISCUSSION] Growing the Git community

From
Philip Oakley <philipoakley@iee.email>
Date
Sep 25, 2019, 14:14 UTC
Message-ID
<b6835484-62a4-6f89-b6b1-f43afe794272@iee.email>
In-Reply-To
<CAJ+soVcmMwy7GgLcV-m1kNEsHYirHMQQeFuEYZanbCNUK4_zHg@mail.gmail.com>
Hi Pierre,
On 25/09/2019 14:36, Pierre Tardy wrote:
Show 17 quoted lines
>>> As a community, our number one goal is for Git to continue to be the best
>>> distributed version control system. At minimum, it should continue to be
>>> the most widely-used DVCS.
>> I'd rather we stated our goal in terms of what problems we are trying
>> to address rather than accolades we want sent our way.  E.g. "Our goal
>> is to make developers more productive by providing them increasingly
>> useful version control software".
>>
> Agreed.
> And why restrict on DVCS?
> Isn't it admitted that the distributed version control is nowadays
> much better in term of software productivity?
> Is there some use cases that "traditional" centralized VCS are better
> on, and on which we gave up as a goal?
>
> Regards,
> Pierre

As an old engineer, I do remember and still see the vast range of areas where the Git DVCS is probably never going to help because it doesn't solve the engineering issues that regular VCS (e.g. Mil-Std-498) have solved for generations...

What modern computing, Linux style, has is:
- Perfect replication, at near zero cost or time.
- Line oriented, Source code based basis.
- Computational efficiency, at near zero cost or time.
- Crypto-algorithms at strength.

If we go outside those areas we are less and less likely to manage. (digital video? Every binary to be serialised? bit rot resilience? traceability?).

We do have some Elephants in the room regarding What the community is about (limits and goals), as distinct from How we conduct ourselves (CoC), but that probably should be separated out.

Previous: Jakub NarebskiNext: Jakub Narebski
Message 26 of 45 in “[DISCUSSION] Growing the Git community”
  1. Derrick StoleeSep 19, 2019
  2. Denton LiuSep 19, 2019
  3. Emily ShafferSep 19, 2019
  4. Jeff KingSep 19, 2019
  5. Junio C HamanoSep 20, 2019
  6. Garima SinghSep 20, 2019
  7. Junio C HamanoSep 20, 2019
  8. Klaus SembritzkiSep 19, 2019
  9. Klaus SembritzkiSep 19, 2019
  10. Klaus SembritzkiSep 19, 2019
  11. Klaus SembritzkiSep 20, 2019
  12. Klaus SembritzkiSep 20, 2019
  13. Klaus SembritzkiSep 20, 2019
  14. Klaus SembritzkiSep 20, 2019
  15. Klaus SembritzkiSep 20, 2019
  16. Mike HommeySep 19, 2019
  17. Johannes SchindelinSep 23, 2019
  18. Jakub NarebskiOct 1, 2019
  19. Jeff KingSep 19, 2019
  20. Derrick StoleeSep 20, 2019
  21. Jeff KingSep 20, 2019
  22. Elijah NewrenSep 19, 2019
  23. Pierre TardySep 25, 2019
  24. Derrick StoleeSep 25, 2019
  25. Jakub NarebskiOct 4, 2019
  26. Philip OakleySep 25, 2019
  27. Jakub NarebskiOct 4, 2019
  28. Emily ShafferNov 12, 2019
  29. Johannes SchindelinNov 12, 2019
  30. Christian CouderNov 13, 2019
  31. Thomas GummererNov 13, 2019
  32. Emily ShafferNov 14, 2019
  33. Jeff KingNov 14, 2019
  34. Junio C HamanoNov 15, 2019
  35. Pratyush YadavNov 14, 2019
  36. Thomas GummererNov 14, 2019
  37. Philip OakleySep 20, 2019
  38. brian m. carlsonSep 20, 2019
  39. Randall S. BeckerSep 20, 2019
  40. Jakub NarebskiOct 4, 2019
  41. Garima SinghSep 20, 2019
  42. Junio C HamanoSep 20, 2019
  43. Junio C HamanoSep 20, 2019
  44. Derrick StoleeSep 23, 2019
  45. Johannes SchindelinSep 23, 2019

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.