Each member of the Ribbit Network Core Team is expected to take ownership of a primary project during their time as part of the Ribbit Network Core Team.
Core members are of course welcome and encouraged to take on lots of other little small tasks or efforts during their time on the core team, but they must always have one primary project.
Core Members are expected to take ownership of projects. This means that you are responsible for asking for direct help when you need it and proactively reporting progress. If no one else on the core team knows what to do, you are responsible for finding outside help.
This is a community driven project and we can only see success if the community drives efforts. The core team exists to demonstrate this.
Each project should be a SMART (Specific, Measurable, Attainable, Relevant, Timely).
Projects should be achievable within 3 months (1 quarter) or less. If you have an idea for something larger than that, feel free to document the large scope, but you will need to break the project down into a smaller scope for the task.
Ideally the core team projects are Big Chunk tasks, not little chunk tasks which push the project forward in a meaningful way.
Small chunk tasks are items that are quickly completable with little to no creative thought. Examples might be: “Make one social media post today” or “Fix typo in Github tomorrow”.
Big chunk tasks are tasks that are often decomposable into many smaller subtasks and generally require some creative effort. Examples might be: “Develop and execute a social media strategy for Ribbit for the next 2 months” or “Create a new Frog Sensor Registration Website by next month”
The image below shows an example of the template for a core-team project: