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

[TOPIC 0/12] Welcome / Conservancy Update

From
Taylor Blau <me@ttaylorr.com>
Date
Oct 2, 2023, 15:17 UTC
Message-ID
<ZRrfAdX0eNutTSOy@nand.local>
In-Reply-To
<ZRregi3JJXFs4Msb@nand.local>
(Presenter: Taylor Blau, Notetaker: Keanen Wold)
* Software Freedom Conservancy status report
* We have about $89k in the Git project account (up ~$20k from last year)
   * Biggest expense is Heroku - Fusion has been covering the bill
      * There's on and off work on porting from a Rails app to a static site:
        https://github.com/git/git-scm.com/issues/942
   * Dan Moore from FusionAuth has been providing donations
   * Ideally we are able to move away from using Heroku, but in the meantime
     we'll have coverage either from (a) FusionAuth, or (b) Heroku's new
     open-source credit system
* We have more money than we have plans for, we're looking for ideas[a] on how
  to spend this money such as funding people to visit our conferences and
  sponsoring students to learn more about Git
* Trademark considerations for people using "Git" in their product names
   * We do have general council and are trying to think more about what the Git
     trademark means
   * Question - are there other conservancy products who have trademark issues
      * They hold all trademarks for their projects
      * Git has had the most problems with people/products using Git in their
        name
      * They reach out with letters, etc. and have not had to take legal action
        in most cases
   * Question - how do we enforce the rules when we have GitHub and GitLab?
      * The trademark has exemptions for Hub and Lab
      * We need to hold the line for the trademark for new companies, etc. using
        the name otherwise we lose our leverage to protect the name
   * Question - have the trademark ‘offenses' been growing?
      * It's been pretty stable
      * We're looking to be fair
   * Additional questions can be sent to Pono
Previous: Taylor BlauNext: Taylor Blau
Message 2 of 14 in “Notes from the Git Contributor's Summit, 2023”
  1. Taylor BlauOct 2, 2023
  2. 0/12 Welcome / Conservancy UpdateTaylor Blau, Oct 2, 2023
  3. 1/12 Next-gen reference backendsTaylor Blau, Oct 2, 2023
  4. 02/12 Libification Goals and ProgressTaylor Blau, Oct 2, 2023
  5. 3/12 Designing a Makefile for multiple librariesTaylor Blau, Oct 2, 2023
  6. 4/12 Scaling Git from a forge's perspectiveTaylor Blau, Oct 2, 2023
  7. 5/12 Replacing Git LFS using multiple promisor remotesTaylor Blau, Oct 2, 2023
  8. 6/12 Clarifying backwards compatibility and when we break itTaylor Blau, Oct 2, 2023
  9. 7/12 Authentication to new hosts without setupTaylor Blau, Oct 2, 2023
  10. 8/12 Update on jj, including at GoogleTaylor Blau, Oct 2, 2023
  11. 9/12 Code churn and cleanupsTaylor Blau, Oct 2, 2023
  12. 10/12 Project management practicesTaylor Blau, Oct 2, 2023
  13. 11/12 Improving new contributor on-boardingTaylor Blau, Oct 2, 2023
  14. 12/12 Overflow discussionTaylor Blau, Oct 2, 2023

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.