# How we work ## Our repositories * Project management repositories: , we use a centralized project board (see ) * Code repositories : * Front end * UI code : * Our REST API Client: * Backend * API controllers/endpoints: * Backend models/services: * Our Graph ORM-alike to interact with RDF/SPARQL backends: * See the others here: * Administration command lines / jobs : * Services * O’FAIRE: * Annotators: * NCBO proxy: ## The way that we manage our issues and feature request General issues (not technical) are created in [the project-management repository](https://github.com/agroportal/project-management/issues), and the more specific ones (technical) are directly created in the related repository ( e.g if we know that the issue is directly and only related to the models, then the [ontologies_linked_data](https://github.com/ontoportal-lirmm/ontologies_linked_data) is the target) In all most all our repositories we have those issues labels (types) * **Feature request issues (with the labels: bug, feature request, enhancement)**: these issues are requirements/specifications of fixes or new features to implement. * **Support/documentation issues (with the labels: question, documentation)**: these issues will be subjects/questions to write and document in * **Project management issues (with the label Project management)**: these issues are just project management artifacts/helpers, one of the main use cases is to gather a group of related **feature request issues** in a unique parent issue that represents the project of implementing it. Those project issues will help us to follow the progression of the implementation. * **Content:** Are issues related to the content of the portal (e.g an Ontology can’t parse) ## Develop a feature / fix a bug :::info To build your local environment see ::: ![](https://wiki.agroportal.eu/api/files.get?sig=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJrZXkiOiJwdWJsaWMvOWI4NTM2MDMtYzI1My00NTA0LTk2NzgtZGM1OGUwZmM1MGZmL2M0NzQ5ODU3LWRjODEtNDZhMC1iNjgzLTZhZWMwMTIxMzU1Yy9ob3ctd2Utd29yay5wbmciLCJ0eXBlIjoiYXR0YWNobWVudCIsImlhdCI6MTc5Mzg5NDQwMCwiZXhwIjoxNzkzOTgwODAwfQ.0qGKFadMCdaXdfZkfAlooQikmvjOZZpnDKD1f2e3DSg "right-50")When we are assigned (or self-assigned) to an issue, we start by creating a pull request on the mode `draft` related to the issues concerned, to tell people that we started working on it. Each issue (or the same group of issues) needs to be associated with a new branch * If its a fix, the start of the branch would be `master` and need to follow this norm `fix/name-of-your-branch` * Else if its a feature the start would be `devlopment` and need to follow this norm `feature/name-of-your-branch` When your work is ready to be reviewed you put the pull request into `open` mode. A pull request is accepted and merged only if: * Is well described * Implement tests (if needed) * Pass all the tests * Have related documentation (if needed) * Got accepted by all the reviewers **Regarding the pull request formatting, here are some of our required best practices:** * **Naming**: If it's a feature, start with `Feature: your title`. If it's a fix, start with `Fix: your title`. * **Target branch**: For a feature or fix, open the pull request against the `development` branch. For a hotfix, open it against the `master` branch. * **PR description**: Include the link to the issue the PR resolves for context. Add a brief description if necessary, then list all the changes, along with screenshots of each change. --- **Documents** - [💁‍♂️ Acknowledgments](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/acknowledgments-15GdRXLQdm) - [📚Publications and references](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/publications-and-references-87tEoeoGKy) - [🗽Terms & Conditions](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/terms-conditions-naDsDo2Zxq) - [🧞‍♂️Metadata guidelines and recommendations](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/metadata-guidelines-and-recommendations-pOFbK9sIfp) - [📜 AgroPortal Release Notes](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/agroportal-release-notes-btKjZk5tU2) - [ 👩‍🚀 User Guide](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/user-guide-ZszoBwfjGF) - [📎 API Documentation](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/api-documentation-kMCurGKD97) - [🤖 Developer Documentation](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/developer-documentation-LhsrucqGTa) - [🗃External Documentation](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/external-documentation-vNPQCdArrr) - [AgroPortal infrastructure](https://wiki.agroportal.eu/s/e6158eda-c109-4385-852c-51a42de9a412/doc/agroportal-infrastructure-ietsAU4kPs)