Difference between revisions of "Developers"
| Line 1: | Line 1: | ||
| − | ''' | + | '''Join the CC Developer Community!!!''' |
| − | + | ||
| − | + | Join our [http://slack-signup.creativecommons.org/ Slack], IRC, or [cc-developers+subscribe@creativecommons.org mailing list] communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the [https://opensource.creativecommons.org/blog CC Open Source Blog] or via [https://twitter.com/cc_opensource Twitter]. | |
| − | + | ||
| + | Know more about our [https://opensource.creativecommons.org/community/ communication channels] | ||
== Get Involved == | == Get Involved == | ||
| − | + | We really appreciate community contributions and feedback (we're a small team and spread thin) and we especially love seeing what you build using CC's tools. | |
| − | + | ||
| − | + | We do all of our development on GitHub and are generally open to pull requests and proposals for new community-maintained projects. | |
| − | + | We would especially like help with reviving projects that CC's engineering team does not have the time to actively work on (such as [https://github.com/creativecommons/creativecommons-wordpress-plugin our WordPress plugin] and [https://github.com/creativecommons/cc-license-chooser license chooser widget]). We're also looking to improve our documentation and increase our automated test coverage across pretty much all our projects, so help with that would be greatly appreciated. | |
| + | Please follow [https://opensource.creativecommons.org/contributing-code/pr-guidelines our pull request guidelines] when submitting code. If you are not familiar with GitHub or pull requests, [https://guides.github.com/activities/hello-world/ here is an excellent guide to get started]. | ||
| − | + | Know more about [https://opensource.creativecommons.org/contributing-code/ how to contribute on existing projects or proposing new ones]! | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ; [[ | + | ; Mailing list |
| − | + | : [cc-developers+subscribe@creativecommons.org CC Developers] or [usability-announce+subscribe@creativecommons.org CC Usability Announcements] | |
| − | ; [ | + | ; IRC #creativecommons-dev channel on [https://freenode.net/ Freenode] |
| − | : | + | : This channel is mirrored to the #cc-developers channel on Slack |
| − | ; [ | + | ; Slack |
| − | : | + | : [http://slack-signup.creativecommons.org/ Sign up] and join our sub-communities for tech/developers |
| − | == | + | == Other forms of contribution == |
| − | ; [ | + | ; [https://opensource.creativecommons.org/gsoc-2019/ Google Summer of Code] |
| − | : | + | : See CC participation on GSoC since 2006 |
| − | ; [ | + | ; [https://opensource.creativecommons.org/community/#mailing-lists Usability Testing] |
| − | : | + | : Participate in one of our regular usability tests for CC tools that we're actively working on (we'll give you a gift card!) |
| − | ; [ | + | ; [https://wiki.creativecommons.org/wiki/Translate Translate our Content] |
| − | : | + | : Find out how to help the Creative Commons community with translations |
| − | ; [ | + | ; [https://github.com/creativecommons/cc-vocabulary Contribute Design] |
| − | : | + | : Contribute to our brand new set of standard UI components and help us apply it to all existing projects |
<br clear="all"/> | <br clear="all"/> | ||
Revision as of 19:58, 3 October 2019
Join the CC Developer Community!!!
Join our Slack, IRC, or [cc-developers+subscribe@creativecommons.org mailing list] communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the CC Open Source Blog or via Twitter.
Know more about our communication channels
Get Involved
We really appreciate community contributions and feedback (we're a small team and spread thin) and we especially love seeing what you build using CC's tools.
We do all of our development on GitHub and are generally open to pull requests and proposals for new community-maintained projects. We would especially like help with reviving projects that CC's engineering team does not have the time to actively work on (such as our WordPress plugin and license chooser widget). We're also looking to improve our documentation and increase our automated test coverage across pretty much all our projects, so help with that would be greatly appreciated. Please follow our pull request guidelines when submitting code. If you are not familiar with GitHub or pull requests, here is an excellent guide to get started.
Know more about how to contribute on existing projects or proposing new ones!
- Mailing list
- [cc-developers+subscribe@creativecommons.org CC Developers] or [usability-announce+subscribe@creativecommons.org CC Usability Announcements]
- IRC #creativecommons-dev channel on Freenode
- This channel is mirrored to the #cc-developers channel on Slack
- Slack
- Sign up and join our sub-communities for tech/developers
Other forms of contribution
- Google Summer of Code
- See CC participation on GSoC since 2006
- Usability Testing
- Participate in one of our regular usability tests for CC tools that we're actively working on (we'll give you a gift card!)
- Translate our Content
- Find out how to help the Creative Commons community with translations
- Contribute Design
- Contribute to our brand new set of standard UI components and help us apply it to all existing projects
