I would say we may want to be a bit looser on the requirements
I’ve seen dev teams get really opinionated about tabs vs. spaces → Github actions vs. Argo → and so on. With that in mind, I’d suggest our “tooling” is free to them but not required. Otherwise I can seriously see promising projects deciding not to join because “github sucks” and because they really really want to use Jira for planning (for example )
I would also like to suggest that we request that there is a commitment from Sandbox projects to contribute back to the ODC based on whatever revenues or grants that they receive. Perhaps we could have this be a non binding public commitment of some sort at least for now. Wdyt?
Just surfacing this one. My take would be that we want to be open at the top of the funnel - we have paved paths that are not requirements. That said, each project is held accountable for outcomes in that either they progress, or they don’t. So we should not be too prescriptive and actually we don’t need to be.
That said → I do think we need to be explicit in our expectations that somehow projects we nurture and support will give back to us. I personally do not think we need this to be on chain quite yet (others may disagree and show us how easy it could be) - however it should at least be public.
I am in synch with you on the specific tooling not being required rather that there is some evidence of the group using tooling to make the effort into something organized enough that we want it to be considered an official project. I will update the language and repost.
Project is ready for broad collaboration and adoption
Benefits
Project gains access to ODC business development mentoring
Project is published in the project section of the ODC website
Project repository is forked into the OpenDataforWeb3 GitHub organization. The original Sandbox Team repository is archived (read only)
Requirements
Product must maintain minimum project requirements and alignment with ODC mission, values
Sandbox team sponsored as a Project
ODC member proposes Sandbox team as a Project through the Discourse forum as a Project Proposal
Requirements
ODC member must sponsor the Project proposal
ODC Jedi reviews Project application for minimum requirements and alignment with ODC mission, values
Team elects a project lead and maintainers group
Project must use the ODC tooling or project management tooling that is similar, e.g. Gitlab CI instead of Github Actions, Atlassian Jira instead of Github Issues. Ideally we would be able to integrate our community management tooling Orbit and Govrn. Without that, the Sandbox team could simply provide some reporting output for the ODC Jedi Knights to review as part of the Project Proposal.
Project contributors must be ODC members
Team provides regular updates to ODC Jedi and community
Team practices basics of agile software development
Sandbox Team
Any individual or team that wants to self organize
Requirements
Sandbox maintains minimum sandbox team requirements
Benefits
ODC Sandbox repository to hold your code and documentation
ODC Discord channel for communications
Mentoring on agile software development practices, Github CICD, Github project management tools, and how to use Git with Github repositories. If the Sandbox team opts to use other project management tooling, the mentoring options are best effort depending on the community experience and availability.
Ability to build on top of the ODC community of open data
Near future access to public chain ETL data sets
Near future access to ODC node stack used for development and hackathons
Member applies to be a Sandbox team
ODC member requests to be a Sandbox team through the Discourse forum as a Sandbox Team Proposal
Requirements
Be an ODC member in good standing
Have a great idea for a project that is aligned with the ODC mission and values
Indication of intent and capabilities
ODC Jedi reviews Sandbox application for minimum requirements
)