From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Subject: [TOPIC 0/12] Welcome / Conservancy Update
Date: Mon, 2 Oct 2023 11:17:21 -0400 [thread overview]
Message-ID: <ZRrfAdX0eNutTSOy@nand.local> (raw)
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
next prev parent reply other threads:[~2023-10-02 15:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 15:15 Notes from the Git Contributor's Summit, 2023 Taylor Blau
2023-10-02 15:17 ` Taylor Blau [this message]
2023-10-02 15:17 ` [TOPIC 1/12] Next-gen reference backends Taylor Blau
2023-10-02 15:18 ` [TOPIC 02/12] Libification Goals and Progress Taylor Blau
2023-10-02 15:18 ` [TOPIC 3/12] Designing a Makefile for multiple libraries Taylor Blau
2023-10-02 15:19 ` [TOPIC 4/12] Scaling Git from a forge's perspective Taylor Blau
2023-10-02 15:19 ` [TOPIC 5/12] Replacing Git LFS using multiple promisor remotes Taylor Blau
2023-10-02 15:20 ` [TOPIC 6/12] Clarifying backwards compatibility and when we break it Taylor Blau
2023-10-02 15:21 ` [TOPIC 7/12] Authentication to new hosts without setup Taylor Blau
2023-10-02 15:21 ` [TOPIC 8/12] Update on jj, including at Google Taylor Blau
2023-10-02 15:21 ` [TOPIC 9/12] Code churn and cleanups Taylor Blau
2023-10-02 15:22 ` [TOPIC 10/12] Project management practices Taylor Blau
2023-10-02 15:22 ` [TOPIC 11/12] Improving new contributor on-boarding Taylor Blau
2023-10-02 15:22 ` [TOPIC 12/12] Overflow discussion Taylor Blau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZRrfAdX0eNutTSOy@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.