Forum: all work is discussed and elevated during Tuesday Tech Meetings at 11:00am Eastern.
Any OpenTEAM members can create a "open" paired work session ticket in the OpenTEAM Technology GitLab Board.
"Open" issues are moved into "Triage / Evaluation" for discussion during Tuesday software meeting until they are approved or "Closed." If there is general interest and excitement in moving forward, work is elevated to a "Paired Session in Progress" or into "Secretariat and Community Ongoing Funded Work." Issues in "Triage/Evaluation" that cannot be moved to a paired work session due to poor timing, work capacity limitations, etc, can be moved to "Icebox."
Paired Sessions in Progress require:
- Clear outcomes
Link it to the gitlab issue for the corresponding paired work session.
Definition of Paired Work Session
Focused exploratory work package that has the goal of defining a broader scope of work. Paired work sessions are unfunded, with the expectation that they establish a plan for a funded work package. Paired work sessions inherently involves two or more OpenTEAM member organizations.
If a Paired Work Session gets to the end of its timeframe but is incomplete, it goes into the Icebox if it is still relevant. If it is identified as to be dropped, put it in "Closed" - tag as incomplete.
Once paired work sessions are completed, they are moved into "Report-out and Review." Once this is completed, the item moves to "OpenTEAM Secretariat Review."
Paired work sessions that have defined a broader scope of work can be expanded and defined as a work package.
Definition of a Community-Led Work Package
Each community-led work package should have a developed project proposal. This type of work package differs from existing contracts with OpenTEAM that fulfill specific deliverables under the FFAR grant.
Copy this tempate and write up a work package proposal. This work package proposal will support community and secretariat understanding of the following elements:
- Initial Post date: YYYY-MM-DD
- Description (Short description of the work package - developed as part of group process (2-3 sentences))
- Repository structure and location (Where will work be done and what will it be called?)
- Reference to past work (Existing git lab issues, paired work sessions, Kumu map, or external projects related to the proposed work)
- Teams Involved (List the different teams involved. Indicate one team (or specific person) as lead on the project.)
- Project Scope and Duration (number of potential development cycles and list potential milestones
- Problem statement
- Clear articulation of the problem being addressed. Is this need driven by end users? Application developers? Farmers? Verifiers?
- Outline the approach being proposed, what technical components will be built & by whom?
- Rationale (Articulate why this approach being prioritized at this time)
- Project Plan (How will it be managed and documented ? )
- Estimated Resourcing/level of effort (Are there explicit resourcing requirements from OpenTEAM? How many people will be working on this project from each participating organization? Part time or full time?)
- Start & end, amount of time expected from different teams over development cycles
- Expected Deliverables (Artifacts, expected format (e.g. open-source code, documentation, PDFs, research report, etc.)
Community Forum and Approval
What is the forum where this is discussed? Paired work sessions and work packages are discussed during our Tuesday stand-ups and go to review of the Secretariat during their regularly scheduled meetings.
How is this approved?
The Secretariat reviews proposed community work packages at their regularly scheduled meetings, and OpenTEAM staff report back to the community with any feedback and approval.
(Direct contracts are pre-established and lie outside the community process.)
Secretariat Approved Work
All OpenTEAM-funded work is approved by the Secretariat, whether it is an ongoing direct contract under specific deliverables of the FFAR grant or via a community-led process toward a developed paired work session or work package.
Paired work sessions, work packages, and direct contracts are all funded in different ways, depending on existing deliverables under the organizations and how it fulfills deliverables under FFAR budget or existing budgets under another organization's budget.
Financial visibility: (Finalizing for Year 2 this month)
- *OpenTEAM will provide budgetary information to each organization with existing contracts with OpenTEAM that fulfill specific deliverables under the FFAR grant.
- *OpenTEAM will provide a budget for community-funded projects and provide visibility into this work to support community-approved projects.
- *OpenTEAM sees opportunity for additional funding outside of the scope of these two budget streams to fund various community prioritized work that may lie just outside its FFAR grant deliverables. The goal with the process is to highlight the demand for community-led work packages and to fund them one way or another.