1) Background and purpose
INAtrace is an open-source traceability software designed to lower the costs of inclusion of smallholder farmers in agricultural supply chains. The software has recently gone through changes in governance and in the interim a backlog of features enhancements and fixes has accumulated across multiple funded implementations and development efforts. An interim Code Administrator is needed to stabilize the core codebase help clear the backlog through a defined contribution workflow and establish repeatable processes while long-term technical governance is put into place.
2) Objective
Provide time-bound hands-on technical support to:
- Implement lightweight community-friendly processes for contribution review testing and merging INAtrace codeprimarily through GitHub-based workflows.
- Reduce the backlog of unmerged code and untriaged enhancements.
- Work hand in hand with the INAtrace Technical Steering Committee and ad hoc committee on code governance to list classify vet and merge existing commits made by the different INAtrace deployments to date.
3) Duration and level of effort
- Initial term: 3 months (extendable up to 6 months if needed).
- Expected effort: part-time (for example 1020 hours per week) with flexibility to surge during release windows.
4) Reporting and working relationships
- Reports to: Alliance Bioversity-CIAT project lead with input from the INAtrace Technical Steering Committee and ad hoc code governance committee.
- Works closely with: -The interim Product Owner function (including: guiding strategic direction of INAtrace prioritizing development tasks refining the product roadmap) -Implementers and funded development teams -Linux Foundation personnel as needed for technical review repository administration governance functions.
- Coordination: regular check-ins (for example biweekly) with the ad hoc code governance committee and monthly updates to the global community meeting.
5) Scope of work and responsibilities
A. Backlog stabilization and intake
- Establish a single source of truth intake on GitHub for: i) issues (bugs) ii) enhancements (features) iii) resolving technical debt such as: Unintegrated or partially integrated features developed under different projects Inconsistent architecture or coding patterns Limited or outdated documentation Insufficient testing.
- Propose a stabilization queue prioritizing developments for review and adoption by the INAtrace code governance committee.
B. Contribution and merging workflow
- Implement and enforce a lightweight workflow (documented in ) including: issue-to-branch linkage pull request templates required reviews required tests merge standards and rollback guidance.
- Serve as interim maintainer with merge authority ensuring consistent timely decisions in accordance with Linux Foundation norms (see: 1)
C. Quality assurance and testing
- Define a minimum testing standard that covers: automated tests (unit tests where feasible) regression checks for core workflows lightweight functional verification in a test environment prior to production release.
- Ensure each merged change has an auditable trail: what it changes how it was tested and any known limitations.
D. Repository and project structure
- Recommend (and if agreed implement) a clear repository structure including: a main project repository (or equivalent) to host shared documentation (README contributing guide governance pointers release notes) consistent branch naming conventions and tagging for releases a visible roadmap location (for example docs/).
E. Community enablement
- Run short working sessions (as needed) to help teams: submit clean pull requests resolve merge conflicts add or improve tests follow the agreed workflow.
6) Deliverables
By the end of the initial term the interim maintainer will deliver:
- Backlog inventory and stabilization plan (issues enhancements unmerged work redundancies).
- Published contribution workflow in GitHub (including templates and minimum quality gates).
- At least one stabilized release with release notes and a short what changed summary.
- Maintainer handover package for the longer-term governance body including: current backlog status recommended next priorities any known risks or architectural constraints a short list of candidates/process suggestions for long-term maintainer continuity.
Requirements
7) Required qualifications
- Demonstrated experience serving as a maintainer (or equivalent role) for a multi-contributor codebase (review merge release responsibility). (see: )
- Demonstrated GitHub-based collaboration skills (issues pull requests branches code review norms).
- Practical experience defining and enforcing minimum viable testing and release discipline.
- Experience operating with vendor-neutrally and communicating decisions transparently across regions and organizations.
8) Policies and compliance expectations
- Contributions must follow the projects inbound contribution requirements including Developer Certificate of Origin (DCO) sign-off where adopted for the project workflow. (See: 1)
- Must comply with Linux Foundation Europe project policies (including Code of Conduct and other published policies). (See:)
- Must operate in a way that protects licensing integrity and ensures changes can be distributed under the projects license model. (See: Linux Foundation)
9) Success indicators
- Backlog reduced and clearly triaged (accepted / in progress / deferred / rejected).
- Measurable improvement in cycle time from code submitted to merged and released.
- A working documented process that new contributors can follow without ad hoc guidance.
- At least one stable release that implementers can deploy with confidence.
Benefits
Place of assignment: Americas Region. This is an international search.
Duration of the consultancy: The estimated period for the consultancy is from the signing of the contract (February 2026) until May 2026.
Interested candidates should send the following information to
:
- A technical proposal including a brief statement of no more than two (2) pages of text.
- A Curriculum Vitae including two (2) references.
- A financial proposal that includes at a minimum hourly daily or deliverable-based rates travel expenses and other direct and indirect costs.
Application closing date: January 27 2025
Please note that only shortlisted candidates will be contacted.
Required Skills:
7) Required qualifications Demonstrated experience serving as a maintainer (or equivalent role) for a multi-contributor codebase (review merge release responsibility). (see: ) Demonstrated GitHub-based collaboration skills (issues pull requests branches code review norms). Practical experience defining and enforcing minimum viable testing and release discipline. Experience operating with vendor-neutrally and communicating decisions transparently across regions and organizations. 8) Policies and compliance expectations Contributions must follow the projects inbound contribution requirements including Developer Certificate of Origin (DCO) sign-off where adopted for the project workflow. (See: 1) Must comply with Linux Foundation Europe project policies (including Code of Conduct and other published policies). (See:) Must operate in a way that protects licensing integrity and ensures changes can be distributed under the projects license model. (See: Linux Foundation) 9) Success indicators Backlog reduced and clearly triaged (accepted / in progress / deferred / rejected). Measurable improvement in cycle time from code submitted to merged and released. A working documented process that new contributors can follow without ad hoc guidance. At least one stable release that implementers can deploy with confidence.
Required Education:
7) Required qualifications Demonstrated experience serving as a maintainer (or equivalent role) for a multi-contributor codebase (review merge release responsibility). (see: ) Demonstrated GitHub-based collaboration skills (issues pull requests branches code review norms). Practical experience defining and enforcing minimum viable testing and release discipline. Experience operating with vendor-neutrally and communicating decisions transparently across regi
1) Background and purpose INAtrace is an open-source traceability software designed to lower the costs of inclusion of smallholder farmers in agricultural supply chains. The software has recently gone through changes in governance and in the interim a backlog of features enhancements and fixes has a...
1) Background and purpose
INAtrace is an open-source traceability software designed to lower the costs of inclusion of smallholder farmers in agricultural supply chains. The software has recently gone through changes in governance and in the interim a backlog of features enhancements and fixes has accumulated across multiple funded implementations and development efforts. An interim Code Administrator is needed to stabilize the core codebase help clear the backlog through a defined contribution workflow and establish repeatable processes while long-term technical governance is put into place.
2) Objective
Provide time-bound hands-on technical support to:
- Implement lightweight community-friendly processes for contribution review testing and merging INAtrace codeprimarily through GitHub-based workflows.
- Reduce the backlog of unmerged code and untriaged enhancements.
- Work hand in hand with the INAtrace Technical Steering Committee and ad hoc committee on code governance to list classify vet and merge existing commits made by the different INAtrace deployments to date.
3) Duration and level of effort
- Initial term: 3 months (extendable up to 6 months if needed).
- Expected effort: part-time (for example 1020 hours per week) with flexibility to surge during release windows.
4) Reporting and working relationships
- Reports to: Alliance Bioversity-CIAT project lead with input from the INAtrace Technical Steering Committee and ad hoc code governance committee.
- Works closely with: -The interim Product Owner function (including: guiding strategic direction of INAtrace prioritizing development tasks refining the product roadmap) -Implementers and funded development teams -Linux Foundation personnel as needed for technical review repository administration governance functions.
- Coordination: regular check-ins (for example biweekly) with the ad hoc code governance committee and monthly updates to the global community meeting.
5) Scope of work and responsibilities
A. Backlog stabilization and intake
- Establish a single source of truth intake on GitHub for: i) issues (bugs) ii) enhancements (features) iii) resolving technical debt such as: Unintegrated or partially integrated features developed under different projects Inconsistent architecture or coding patterns Limited or outdated documentation Insufficient testing.
- Propose a stabilization queue prioritizing developments for review and adoption by the INAtrace code governance committee.
B. Contribution and merging workflow
- Implement and enforce a lightweight workflow (documented in ) including: issue-to-branch linkage pull request templates required reviews required tests merge standards and rollback guidance.
- Serve as interim maintainer with merge authority ensuring consistent timely decisions in accordance with Linux Foundation norms (see: 1)
C. Quality assurance and testing
- Define a minimum testing standard that covers: automated tests (unit tests where feasible) regression checks for core workflows lightweight functional verification in a test environment prior to production release.
- Ensure each merged change has an auditable trail: what it changes how it was tested and any known limitations.
D. Repository and project structure
- Recommend (and if agreed implement) a clear repository structure including: a main project repository (or equivalent) to host shared documentation (README contributing guide governance pointers release notes) consistent branch naming conventions and tagging for releases a visible roadmap location (for example docs/).
E. Community enablement
- Run short working sessions (as needed) to help teams: submit clean pull requests resolve merge conflicts add or improve tests follow the agreed workflow.
6) Deliverables
By the end of the initial term the interim maintainer will deliver:
- Backlog inventory and stabilization plan (issues enhancements unmerged work redundancies).
- Published contribution workflow in GitHub (including templates and minimum quality gates).
- At least one stabilized release with release notes and a short what changed summary.
- Maintainer handover package for the longer-term governance body including: current backlog status recommended next priorities any known risks or architectural constraints a short list of candidates/process suggestions for long-term maintainer continuity.
Requirements
7) Required qualifications
- Demonstrated experience serving as a maintainer (or equivalent role) for a multi-contributor codebase (review merge release responsibility). (see: )
- Demonstrated GitHub-based collaboration skills (issues pull requests branches code review norms).
- Practical experience defining and enforcing minimum viable testing and release discipline.
- Experience operating with vendor-neutrally and communicating decisions transparently across regions and organizations.
8) Policies and compliance expectations
- Contributions must follow the projects inbound contribution requirements including Developer Certificate of Origin (DCO) sign-off where adopted for the project workflow. (See: 1)
- Must comply with Linux Foundation Europe project policies (including Code of Conduct and other published policies). (See:)
- Must operate in a way that protects licensing integrity and ensures changes can be distributed under the projects license model. (See: Linux Foundation)
9) Success indicators
- Backlog reduced and clearly triaged (accepted / in progress / deferred / rejected).
- Measurable improvement in cycle time from code submitted to merged and released.
- A working documented process that new contributors can follow without ad hoc guidance.
- At least one stable release that implementers can deploy with confidence.
Benefits
Place of assignment: Americas Region. This is an international search.
Duration of the consultancy: The estimated period for the consultancy is from the signing of the contract (February 2026) until May 2026.
Interested candidates should send the following information to
:
- A technical proposal including a brief statement of no more than two (2) pages of text.
- A Curriculum Vitae including two (2) references.
- A financial proposal that includes at a minimum hourly daily or deliverable-based rates travel expenses and other direct and indirect costs.
Application closing date: January 27 2025
Please note that only shortlisted candidates will be contacted.
Required Skills:
7) Required qualifications Demonstrated experience serving as a maintainer (or equivalent role) for a multi-contributor codebase (review merge release responsibility). (see: ) Demonstrated GitHub-based collaboration skills (issues pull requests branches code review norms). Practical experience defining and enforcing minimum viable testing and release discipline. Experience operating with vendor-neutrally and communicating decisions transparently across regions and organizations. 8) Policies and compliance expectations Contributions must follow the projects inbound contribution requirements including Developer Certificate of Origin (DCO) sign-off where adopted for the project workflow. (See: 1) Must comply with Linux Foundation Europe project policies (including Code of Conduct and other published policies). (See:) Must operate in a way that protects licensing integrity and ensures changes can be distributed under the projects license model. (See: Linux Foundation) 9) Success indicators Backlog reduced and clearly triaged (accepted / in progress / deferred / rejected). Measurable improvement in cycle time from code submitted to merged and released. A working documented process that new contributors can follow without ad hoc guidance. At least one stable release that implementers can deploy with confidence.
Required Education:
7) Required qualifications Demonstrated experience serving as a maintainer (or equivalent role) for a multi-contributor codebase (review merge release responsibility). (see: ) Demonstrated GitHub-based collaboration skills (issues pull requests branches code review norms). Practical experience defining and enforcing minimum viable testing and release discipline. Experience operating with vendor-neutrally and communicating decisions transparently across regi
View more
View less
Job Location:
Monthly Salary:
Experience Required:
Posted on:
Yesterday
Vacancies:
1 Vacancy
