Benjamin Bädorf
a9e29279ea
Squash commit of storybook addition to aid design system documentation efforts. The older commit titles were: * Initial storybook commit * Fix documentation.json links * Don't track documentation.json in git * Enable sass in storybook * Initial version of a story that uses angular components * Remove example stories, clean up button story * More example stories * Fix sb build * Always use dev * Try without auth header * Update workflow name * More logs * Check if token set * Use release/storybook branch for testing * Send ref input to workflow * Escape input to curl call * Adding logging * Different type of escaping * Fix JOSN * Use dev branch for opf/design-system storybook publishing * Add plugin to message path to parent window * Remove extraneous story * Add a ton of docs * Update stories * Fix syntax error caused by multiple newlines inside of a JSX component * Add text-field story * Add basic html stories that don't work yet * Try to get plain HTML examples working * HTML Examples work, but slowly revert to components anyway * Fix HTML examples * Remove extraneous files * Put storybook eslint rules back in * Improve docs * Show docs tab by default * Add pullpreview for storybook * Use the same pullpreview tag for both storybook and normal deployments * Change name of second pullpreview workflow * Pin node version to 16.17.0 * Initial update to docs Added/updated: Foundation pages: - Colours (major update) - Shadows (minor) - Typography (new) Blocks - Checkbox (minor) - Action bar (major) - Buttons (new) - Link (major) - Modal Dialogue (new) - Selector Field (new) * Make sure all code is available during storybook pp build * Change storybook pullpreview file name * Add production target to docker-compose sb pp * Fix acme check for sb pp * Only run cd-storybook on dev branch * Run without https on 8080 * Added intro and new page - Introduction renamed to "Design System", page rewritten completely - Added page "Devices and Accessibility" * Remove domain from caddy * Add port to listen command * Remove double pullpreview workflows * Added Divider component * Change sorting of stories * Update section titles and order for styles and blocks * add extra action bar story * Updated organising + new page - Updated organisation into Styles, Components and Patterns. - Added page "Using Storybook" (mostly a skeleton for now) * Added note about colours not being implemented yet * Minor Co-authored-by: Parimal Satyal <88370597+psatyal@users.noreply.github.com>
sidebar_navigation
| sidebar_navigation | ||||
|---|---|---|---|---|
|
Develop OpenProject
We are pleased that you are thinking about contributing to OpenProject! This guide details how to contribute to OpenProject.
Get in touch
Please get in touch with us using our development forum or send us an email to info@openproject.org.
Issue tracking and coordination
We eat our own ice cream so we use OpenProject for roadmap planning and team collaboration. Please have a look at the following pages:
Development Environment
Take a look at the bottom under Additional resources to see how to setup your development environment.
Branching model and development flow
Please see this separate guide for the git branching model and core development.
Development concepts
We prepared a set of documentation concepts for an introduction into various backend and frontend related topics of OpenProject. Please see the concepts main page for more.
Translations
If you want to contribute to the localization of OpenProject and its plugins you can do so on the Crowdin OpenProject page. Once a day we fetch those locales and automatically them to GitHub. Contributing there will ensure your language will be up to date for the next release!
More on this topic can be found in our blog post.
Packaging process
Please see this separate guide for the process of building packages of OpenProject.
Testing
Please add tests to your code to verify functionality, especially if it is a new feature.
Pull requests will be verified by TravisCI as well, but please run them locally as well and make sure they are green before creating your pull request. We have a lot of pull requests coming in and it takes some time to run the complete suite for each one.
If you push to your branch in quick succession, please consider stopping the associated Travis builds, as Travis will run for each commit. This is especially true if you force push to the branch.
Please also use [ci skip] in your commit message to suppress builds which are not necessary (e.g. after fixing a typo in the README).
Inactive pull requests
We want to keep the Pull request list as cleaned up as possible - we will aim close pull requests after an inactivity period of 30 days (no comments, no further pushes) which are not labeled as work in progress by us.
Security
If you notice a security issue in OpenProject, please send us a GPG encrypted email to security@openproject.com and describe the issue you found. Download our public GPG key BDCF E01E DE84 EA19 9AE1 72CE 7D66 9C6D 4753 3958 here.
Please include a description on how to reproduce the issue if possible. Our security team will get your email and will attempt to reproduce and fix the issue as soon as possible.
Contributor code of conduct
As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, age, or religion.
Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. Project maintainers who do not follow the Code of Conduct may be removed from the project team.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.
This code of conduct is adapted from the Contributor Covenant, version 1.0.0, available at contributor-covenant.org/version/1/0/0/
OpenProject Contributor License Agreement (CLA)
If you want to contribute to OpenProject, please make sure to accept our Contributor License Agreement first. The contributor license agreement documents the rights granted by contributors to OpenProject.
Read and accept the Contributor License Agreement here.