Software Freedom Conservancy sponsorship agreement#15
Software Freedom Conservancy sponsorship agreement#15
Conversation
This is the original document that the libgit2 project used to apply to the Software Freedom Conservancy.
This is the template fiscal sponsorship agreement, provided by the SFC.
Add the project name, define the name of the leadership body and the name of the signatories.
We will have a 5-person committee, with no more than 2 persons employed by the same employer.
Add the signatories of Tyler Ang-Wanek, Carlos Martín Nieto, Etienne Samson, Patrick Steinhardt, and Edward Thomson as decided at https://github.com/libgit2/discussions/issues/9
(It's Ed's.) We will add the proper address in communication with the Software Freedom Conservancy.
|
The rendered version of this document is: sponsorship-agreement.pdf |
pks-t
left a comment
There was a problem hiding this comment.
There's a bunch of outdated information present in our application. As we've sent that one out already I'm not sure whether we need to update it. I've noticed one inconsistency in the agreement, otherwise the docs look fine to me.
Thanks a lot for handling this!
| features to keep up with the development that Git itself is doing. | ||
| We're a bit behind in feature parity - some of the top features | ||
| that we're interested in are patch application, complete rebase | ||
| functionality and performance improvements. |
There was a problem hiding this comment.
The patch application has been implemented already, so this is outdated, too.
|
|
||
| Carlos Martín Nieto <cmn@dwim.me> | ||
| Edward Thomson <ethomson@edwardthomson.com> | ||
| Patrick Steinhardt <ps@pks.im> |
|
Sorry, I should have been more clear. The It's included here for historical purposes. We should not make changes to it, as it should document the communications that we've had. We should be focusing on the FSA, which is the next thing that is due. Apologies for not communicating that clearly. 😰 |
|
Oops, sorry, I saw your review comments before I saw your overall comment. My bad. 😰 In any case - yes, thanks for catching the error in the FSA. Pushed a new change. Here's the (rendered) update. |
pks-t
left a comment
There was a problem hiding this comment.
Thanks for the fix, looking good to me!
|
@ethomson You've requested my review again, but I don't see any changes having been pushed after my review. |
|
@implausible - Sorry, I should have been more clear. The application.txt file is what we already sent them. It was the document that signaled our intent to join, and our request was approved. It's included here for historical purposes. We should not make changes to it, as it should document the communications that we've had. We should be focusing on the FSA, which is the next thing that is due. Apologies for not communicating that clearly. 😰 |
|
Understood, thanks! |
implausible
left a comment
There was a problem hiding this comment.
I've been over the agreement. Looks good. Thanks!
| Employed by GitHub (2014) | ||
|
|
||
| - Etienne Samson <samson.etienne@gmail.com>, active 2013 - present | ||
| Employed by Mediapart (2013 - present) |
There was a problem hiding this comment.
Heh, that's an homonym, I've never worked at Mediapart myself 🤣. Employed by Kokopelli (2012 - 2019).
There was a problem hiding this comment.
Thanks! Sorry that we erred here.
implausible
left a comment
There was a problem hiding this comment.
Approving again since it looks like you missed my first approval 😄. Sometimes github caches the page funny.
We've applied to join the Software Freedom Conservancy. (The application that we sent them is included.) We were approved!
I've included the original application that we sent them, some time ago, in
application.txt. You're welcome to read over this for context, but I won't be making any changes to it. I wanted to capture it for archival purposes.Now, we need to enter into a sponsorship agreement with them. I propose that we use the included sponsorship agreement as a first draft of our agreement. (It comes from their template.)
Please do review the sponsorship agreement.
Notably:
I'll inform the SFC that we're discussing this. Once we have approval from every member of the Project Leadership Committee, I'll send it to the SFC.