Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Software Freedom Conservancy sponsorship agreement #15

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

ethomson
Copy link
Member

@ethomson ethomson commented Mar 21, 2020

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:

  1. This codifies our leadership structure, after our prior discussions. We will have a five person Project Leadership Committee, comprised of:
  2. This sets the address of the organization as @ethomson's. This was chosen... well, because I'm the one updating the document. 😀

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.

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.
@ethomson ethomson assigned ethomson, carlosmn and pks-t and unassigned carlosmn, ethomson and pks-t Mar 21, 2020
@ethomson
Copy link
Member Author

The rendered version of this document is: sponsorship-agreement.pdf

Copy link
Member

@pks-t pks-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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!

sfc/application.txt Show resolved Hide resolved
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The patch application has been implemented already, so this is outdated, too.

sfc/application.txt Show resolved Hide resolved
sfc/application.txt Show resolved Hide resolved

Carlos Martín Nieto <[email protected]>
Edward Thomson <[email protected]>
Patrick Steinhardt <[email protected]>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Outdated by now.

sfc/application.txt Show resolved Hide resolved
sfc/application.txt Show resolved Hide resolved
sfc/sponsorship-agreement.tex Show resolved Hide resolved
@ethomson
Copy link
Member Author

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. 😰

@ethomson
Copy link
Member Author

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.
sponsorship-agreement.pdf

Copy link
Member

@pks-t pks-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix, looking good to me!

sfc/application.txt Show resolved Hide resolved
sfc/application.txt Show resolved Hide resolved
sfc/application.txt Show resolved Hide resolved
sfc/application.txt Show resolved Hide resolved
@implausible
Copy link
Collaborator

@ethomson You've requested my review again, but I don't see any changes having been pushed after my review.

@ethomson
Copy link
Member Author

@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. 😰

@implausible
Copy link
Collaborator

Understood, thanks!

Copy link
Collaborator

@implausible implausible left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been over the agreement. Looks good. Thanks!

@ethomson ethomson requested a review from carlosmn March 24, 2020 09:26
Copy link
Collaborator

@tiennou tiennou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for keeping through with this @ethomson. I just have one fixup though, for posterity 😉.

Employed by GitHub (2014)

- Etienne Samson <[email protected]>, active 2013 - present
Employed by Mediapart (2013 - present)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heh, that's an homonym, I've never worked at Mediapart myself 🤣. Employed by Kokopelli (2012 - 2019).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Sorry that we erred here.

Copy link
Collaborator

@implausible implausible left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving again since it looks like you missed my first approval 😄. Sometimes github caches the page funny.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants