-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2024.06.05-Transition_to_Apereo_Foundation as_Fiscal_Sponsor/PROPOSAL.md #122
base: main
Are you sure you want to change the base?
Conversation
Fix some typos and slightly improve some phrasing
Sorry for the delay; I just saw your "toot." I sent a reply via our previous email thread as well. Let me know if you get it. Also, feel free to just use [email protected] if you like. Looking forward to chatting - patrick |
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/PROPOSAL.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/PROPOSAL.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/PROPOSAL.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/PROPOSAL.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/PROPOSAL.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/PROPOSAL.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/PROPOSAL.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/PROPOSAL.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/PROPOSAL.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/answers.md
Outdated
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/answers.md
Outdated
Show resolved
Hide resolved
… as_Fiscal_Sponsor/PROPOSAL.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/PROPOSAL.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/PROPOSAL.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/PROPOSAL.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/PROPOSAL.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/PROPOSAL.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/PROPOSAL.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/PROPOSAL.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/PROPOSAL.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/answers.md Co-authored-by: Diego <[email protected]>
… as_Fiscal_Sponsor/answers.md Co-authored-by: Diego <[email protected]>
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/answers.md
Show resolved
Hide resolved
consortium/decisions/2024.06.05-Transition_to_Apero_Foundation as_Fiscal_Sponsor/answers.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I left some suggestions/tweaks.
Hi all, I am back from my conference and campus visits and clawing my way out from under my backlog. I have reached idat's fiscal sponsorship inquiry. While I was traveling, I had Apereo's Controller look over your information, and we have a few initial concerns that I think will impact your interest in joining Apereo. First, Apereo does not have a mechanism to accept crypto donations, and we have decided to specifically exclude crypto-currencies from our acceptable funds options because they are too risky for us and require a burdensome level of paperwork/compliance here in the U.S. Thus, we would need to liquidate the crypto donation at, I believe, Code for Science and Society. Next, in order to join Apereo, dat would need to close out any other fiscal sponsorship relations. This means that no funds may be managed/maintained by another organization. In a previous email (3/15/24), you note, "we are hoping to find a new one [fiscal sponsor] which would consider supporting us through https://opencollective.com/dat." Looking at https://opencollective.com/, is this only an accounting, fundraising platform--offered by Open Collective the company, and independent of Open Collective, the non-profit? We would need to completely separate dat from OpenCollective as a fiscal sponsor; however, if OpenCollective is offering a service as a company that dat chooses to use (no different than CiviCRM for community management, Drupal for website management, etc.), then you may be able to continue its use. We simply are not familiar with where OpenCollective the company and platform end and where OpenCollective the organization and fiscal sponsor start. There are a couple other issues as well: we'd also have to discuss moving any IP dat has with OpenCollective to Apereo (do you know how dat's IP is currently managed?) and dat's fiscal sponsorship analysis would have to be migrated off of Github to our accounting services so we have unified books for our reporting requirements with the US Internal Revenue Service. I'm not sure if one (or all) of these is going to be a deal breaker, so maybe we should set up a time to review your status. I've sent this same message to Alexander via email and attached a questionnaire that we can start the review with and discuss any issues we discover. Hope we didn't scare you off, |
Hi, Patrick, very sorry for the late response. @serapath and I are very busy with one grant application and will most likely be free towards the end of next week. But I quickly checked the open questions and it seem to me all are solvable, so hopefully we can address them next week and then see how to proceed. Thanks for your understanding and have a nice weekend! |
@Masson-Apereo Thank you for reaching out here.
|
Hi all, I just replied and suggested a call to review the application, resolve any issues, and hopefully finalize things. I suggested this Weds. July 10 at 1 PM ET. If that works, let me know, and I will send over an agenda reflecting our review of the application, open issues, and next steps. Thanks- Patrick |
Update: I just sent Alexander and Nina an invite--initially for 1:30, but updated to 1:00 PM ET with an agenda as I just wanted to get this on the calendar. Please accept if this works, but understand if it does not, and feel free to send over some times that work better for you all. Also, feel free to share with others who may want to participate. I also started an agenda--feel free to add any topics you like; we might too :-) Dat Ecosystem Application Review and Discussion General
Open Issues
Dat-Ecosystem questions
|
@dat-ecosystem/consortium
@cblgh
@dpaez
@Frando
@ninabreznik
@serapath
@zootella
According to our dat-ecosystem manifesto, I'm submitting this Proposal for everyone to review. If nobody objects it will be considered accepted in 2 weeks from now (2024.06.05).
If everyone approves actively we can speed up the process and proceed faster, which would be important, so I hope all of you can find the time to do that or share requests for improvement you think are required.
Thank you everyone :-)