Difference between revisions of "Developers"

From Creative Commons
Jump to: navigation, search
(Get Involved)
 
(30 intermediate revisions by 17 users not shown)
Line 1: Line 1:
'''Welcome to the CC Developer Community!''' This is where you'll find all
+
'''Join the CC Developer Community'''  
about the technologies and software products that CC uses to push
+
 
forward our mission to maximize digital creativity, sharing, and
+
Join our [http://slack-signup.creativecommons.org/ Slack] community to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time technology 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].
innovation.
+
 
 +
Know more about our [https://opensource.creativecommons.org/community/ communication channels]
  
 
== Get Involved ==
 
== Get Involved ==
  
All of the projects developed at Creative Commons are open source
+
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.  
software, and just like most open source projects, outside involvement
 
is key to its success. But you don't have to be a software developer
 
to join us--we'd love to have you in the discussion if you're a user
 
researcher, designer, translator, or just interested in the topic. [http://comfortersetking.com/ comforter set king]
 
  
; E-mail
+
We do all of our development on GitHub and are generally open to pull requests and proposals for new community-maintained projects.
: Join our [http://lists.ibiblio.org/mailman/listinfo/cc-devel mailing list]
+
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/wp-plugin-creativecommons our WordPress plugin]). 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.
; IRC
+
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].
: Chat with us real-time on [irc://irc.freenode.net/cc irc] (Freenode, #cc)
 
  
Coming soon: public team meetings, and other ways to engage.
+
Know more about [https://opensource.creativecommons.org/contributing-code/ how to contribute on existing projects or proposing new ones]!
  
== Projects ==
 
  
; [[OpenHome]]
+
; Mailing list
: A Creative Commons homepage with your content
+
: [mailto:cc-developers+subscribe@creativecommons.org CC Developers] or [mailto:usability-announce+subscribe@creativecommons.org CC Usability Announcements].
; [[Summer of Code 2013|Google Summer of Code 2013]]
+
; Slack
: Ideas and more.
+
: [http://slack-signup.creativecommons.org/ Sign up] and join our sub-communities for tech/developers.
; [[Translate|Localization]]
 
: Find out how to help the Creative Commons community with translations.
 
  
== Core Technologies ==
+
== Other forms of contribution ==
  
; [[RDFa]]
+
; [https://opensource.creativecommons.org/programs/ Google Summer of Code]
: Standard for adding machine-readable statements to web pages.
+
: See CC participation on GSoC since 2006.
; [[CcREL]]
+
; [https://opensource.creativecommons.org/programs/ Outreachy]
: Language for adding licensing information to web pages.
+
: See CC participation on Outreachy since 2019.
; [[LRMI]]
+
; [https://wiki.creativecommons.org/wiki/Translate Translate our Content]
: Language for describing educational resources on the web.
+
: Find out how to help the Creative Commons community with translations.
; [[Liblicense]]
+
; [https://github.com/creativecommons/cc-vocabulary Contribute To Design]
: Library for embedding licensing metadata into files of various formats. (note: now somewhat out of date!)
+
: Contribute to our brand new set of standard UI components and help us apply it to all the existing projects.
  
 
<br clear="all"/>
 
<br clear="all"/>

Latest revision as of 14:24, 10 February 2023

Join the CC Developer Community

Join our Slack community to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time technology 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). 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 or CC Usability Announcements.
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.
Outreachy
See CC participation on Outreachy since 2019.
Translate our Content
Find out how to help the Creative Commons community with translations.
Contribute To Design
Contribute to our brand new set of standard UI components and help us apply it to all the existing projects.