Revisit moving to OpenCollective.
Closed this issue · 6 comments
I am currently at the NumFOCUS summit – things are doing great. And there is a number of time where open-collective was brought in small discussion From what I have been told and understand, Jupyter is one of the few 60+ projects which is not using Open collective. The total number of project not using OC being counted in less than the finger of a hand.
It is our right to not use EC though:
- This mean Jupyter is a special case for NF. And I think we can all be aware that special case are annoying and giving more work to NF.
- It's starting to feel weird to be singled out in discussion, I think it does not reflects well on the Jupyter.
Thus even if this was discussed a few month ago by the EC I believe, may I request the EC to reconsider the possibility of moving to Open-Collective ?
Hello, I wanted to know if there was any discussion, or at least if this was put on an agenda ?
HI there - it may have been discussed while I was out on PTO but I'm returning today and have put this item on the agenda for the next EC meeting. Many thanks for this flag and follow up.
Thanks, hope you enjoyed your PTO, it was great seeing you at the NF summit.
Quick update after chatting with the other folks on the team I can share that we are actively working with NF on the current state of our finances. This has been ongoing for months now. There is a gap in reporting and processes and we're trying to resolve this. A move to Open Collective is not on the table at this time.
Thanks for the update. Should this be closed ?
Yes, I'll go ahead and close and we can revisit in the future as appropriate.