Hello, we are glad you're here! We need contributors to help PatternFly improve and grow. While code contributions are important, there are many ways that you can get involved and help out.
This page contains some tips and guidelines for contributing to PatternFly. These are just guidelines, not rules. Use your best judgment and feel free to propose changes to this document in a pull request.
PatternFly adheres to the Contributor Covenant Code of Conduct. As a PatternFly community member, you are expected to uphold this code of conduct, whether that be attending a community meeting, replying to the mail list or contributing.
By contacting the community you can get feedback on the contributions or ideas that you’re excited about. Here are the best ways to get in touch:
Join us in the #patternfly channel on freenode. If you don’t have an IRC client, you can use the web-based client.
Subscribe to our mailing list to participate or follow a variety of discussions on both technical and design topics. This is also a good place to ask questions, gather requirements, or join forces with other community members. Older threads are found in the archive.
PatternFly hosts a monthly community meeting to discuss upcoming sprint work as well as review ongoing or completed work. Check the Monthly Community Meeting page for details about upcoming meetings or to view prior recordings and slides. The community meetings are intended for the community. Reach out to us on the mailing list (patternfly@redhat.com) if you have suggestions on how we might improve the meeting format or want to add a topic for discussion on the agenda for an upcoming meeting.
Before creating a bug report, check the list of known bugs and open issues. Bugs are tracked as GitHub issues. When you create a bug report, include as many details as possible, use a clear and descriptive title, and remember that an image is worth a thousand words, so try to add images and links to rawgit when possible.
You may want to start by sharing your idea on the mailing list (patternfly@redhat.com) to kick off the discussion. A design proposal may have many forms, but it should answer these questions:
- What is the name of the design pattern or component?
- What problem does it solve?
- When do you use it or what are the use cases?
Once your design proposal is ready for review, send a pull request (PR) written in markdown to the Patternfly Design repo. The PR will be a way to discuss and refine the design with the goal of merging it as PatternFly documentation and making it viewable on patternfly.org. Design documents are living documents, therefore new PRs may be opened to add to or modify the documentation as necessary.
If you don’t know how to send a PR using GitHub, don’t worry! We are aware that GitHub was created by and for developers. That’s why we’ve created guides to get you up and running. If you need additional help, contact the community.
Check out our PatternFly Code Guide. If you are committing a new design or modifying an existing design, remember that both developers and designers will review the PR. Therefore, it’s important to add a link to rawgit or an image so that designers can preview the request.
PatternFly delivers design and code. If available, provide a link to the design documentation or spec. If you need help or guidance, contact the community.
The PR will be reviewed by the community and merged once two people from the team approve it.