{"thread":{"id":"58427","subject":"Git / Software Freedom Conservancy status report (2022)","startedAt":"2022-09-13T23:04:00Z","lastAt":"2022-09-13T23:04:00Z","messageCount":1,"participants":["Taylor Blau"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"463006","messageId":"YyELnLai0jXsnt3W@nand.local","threadId":"58427","inReplyTo":null,"subject":"Git / Software Freedom Conservancy status report (2022)","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2022-09-13T23:00:44Z","receivedAt":"2022-09-13T23:04:00Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"It's been a few years since we had the last big update on the Git\nproject's activities at Software Freedom Conservancy. So, we're long\noverdue for an update.\n\nThis email will serve as a report on the project's activities at\nConservancy for the year 2022.\n\nThe previous report (from 2018, whose format I'll try to stick to here)\ncan be found at:\n\n\thttps://lore.kernel.org/git/20180306231609.GA1632@sigill.intra.peff.net/\n\n# Background\n\nGit is a member project of the Software Freedom Conservancy. The Git\nproject joined Conservancy in 2010 so Conservancy could help us manage\nour money and other assets, and provide legal representation for\ntrademark matters. Conservancy doesn't hold any copyright on any of the\nproject's code. Similarly, being a member project at Conservancy does\nnot grant Conservancy any influence in the project's development. The\ntechnical direction that Git takes is up to us.\n\nInterested readers can take a look at a more full picture of what\nConservancy does for the Git project at:\n\n  https://sfconservancy.org/projects/services/\n\nA \"Project Leadership Committee\" (PLC) represents the Git project at\nConservancy. The PLC currently consists of Junio C Hamano, Christian\nCouder, Ævar Arnfjörð Bjarmason, and myself.\n\n# Financials\n\nThe most recent data that I have a copy of is from the end of March,\n2022. So the numbers below aren't totally up-to-date, but they should be\ngood enough to get a rough picture from.\n\nWe have ~70k USD in our account, up ~40k from where we were at in 2018.\nHere are some top-level ledger numbers gathered since 2018-03-07 (the\ndate of the last report). Note that this is all double-entry, so\nnegative numbers are good.\n\n           $-45,962.81 Income:Git\n           $-43,590.05   Donations\n            $-2,332.22   Royalties\n               $-40.54   Currency Conversion\n             $5,512.23 Expenses:Git\n               $134.97   Bad Debt\n               $514.43   Banking Fees\n             $3,852.63   Conferences:Travel\n               $113.22     Per Diem\n                $12.88   Currency Conversion\n               $825.00   Filing Fees\n                $59.10   Hosting\n  --------------------\n           $-40,450.58\n\nMost of our money comes from donations. About 5% of it comes from\nroyalties, most of which are from Amazon affiliate links on git-scm.com.\nOur royalty program with Packt Publishing (who publish Git-related\nbooks) ended in 2019, which accounts for the \"Bad Debt\" expenses. We\ngive 10% of all incoming money to Conservancy's general fund (these\nnumbers are after that 10%).\n\nWe spent some money in 2019 and 2020 on sponsoring travel for to the\nContributor Summit and Git Merge ($3,852.63, to be exact), but spent $0\nin 2021, since no Git Merge was held. This year we sponsored one GSoC\nstudent's travel to Git Merge, and I expect to continue this trend in\nthe future.\n\n# Trademark\n\nWe hold a trademark on the term \"Git\" in the space of software and\nversion control. The report from 2017 has a good overview of the details\nthere:\n\n\thttps://public-inbox.org/git/20170202024501.57hrw4657tsqerqq@sigill.intra.peff.net/\n\nIn response to some discussions we had with folks at Conservancy,\nChristian brought a discussion to the list about rethinking the way we\ntreat our trademark in the future, particularly with respect to\nenforcement.\n\nSee his recent email to the list for more details there:\n\n\thttps://lore.kernel.org/git/CAP8UFD3WQ64FuXarugF+CJ_-5sFNBCnqPE0AEBK-Ka78ituKTg@mail.gmail.com/\n\n# Travel Budget Allocation\n\nLike I mentioned above, we sponsored travel for one GSoC student to\nattend Git Merge and the Contributor's Summit this year. The process has\nbeen somewhat ad-hoc, at least in the past, but the PLC formalized this\nprocess a little bit more rigidly in 2018. The report from that year has\na good overview of the details.\n\nSimilarly, that whole procedure is (still) open for comments and\nsuggestions. Our main focus is to make it possible for new contributors\n(particularly ones who have participated in programs like GSoC and\nOutreachy) to attend Git Merge (and, specifically, the Contributor's\nSummit) where it wouldn't otherwise be possible.\n\n# Conclusion\n\nThat's all for this year. I'm hoping to make this a somewhat more\nregular thing, or at least do it once a year (probably around the time\nof the Contributor's Summit, when most of the folks who will be\ninterested in the details here will all be in the same room).\n\nI'm happy to answer any questions on the list, and I'll propose a\nsession on it at the Contributor's Summit tomorrow, in case folks want\nto discuss this further in person.\n\nThanks,\nTaylor\n"}]}