diff --git a/main/404.html b/main/404.html index 1cef0822..9313e91d 100644 --- a/main/404.html +++ b/main/404.html @@ -39,12 +39,6 @@
This outlines how to propose a change to the aok package. For more detailed info about contributing to {oak}, and other pharmaverse packages, please see the development process guide as well as other Developer Guides in the Articles section of the {admiral} website
+This outlines how to propose a change to the aok package. For more detailed info about contributing to {oak}, and other pharmaverse packages, please see the development process guide as well as other Developer Guides in the Articles section of the {admiral} website
For each new contribution, the user creates an issue on the issue tab on GitHub to put it in our backlog. The issues can range from bug identification and/or fixes, enhancements to functions, documentation, tests or new features.
We advise you to contact us when an issue is created via Slack (If you don’t have access, use this link to join). We can discuss details or align expectations if you are not familiar with the {oak}
philosophy and programming strategy. The team will try to review the issues within the next backlog meeting and give some initial feedback. Since we are not a 100% fully resourced software development team it might be that some issues will take longer to respond to depending on the amount of overall issues.
Familiarize yourself with our programming strategy, guidance for GitHub usage and unit testing.
Familiarize yourself with our programming strategy, guidance for GitHub usage and unit testing.
All newly created issues will be reviewed within the next backlog meeting and the creator will receive an initial feedback via a comment. Someone from the core development team will then triage new issues by assigning the appropriate labels (such as “user request” so we can easily identify new requests).
Issues are meant to be taken on by users from the Pharma programming community.
Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the oak codebase remains robust and consistent.
+Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the oak codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel
branch until you have checked off each task.
styler::style_file()
to style R and Rmd filesdevtools::document()
so all .Rd
files in the man
folder and the NAMESPACE
file in the project root are updated appropriately