You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>Ahmad Bilal is a Computer Science undergrad from UET Lahore, who likes computers, problems and using the former to solve the later. He is always excited about Open Source, and is currently focused on Node.js, Serverless, GraphQL, Cloud, Gatsby.js with React.js and WordPress. He likes organizing meetups, conferences and meeting new people. Cats are his weakness, and he is a sucker for well-engineered cars.</p>
159
-
<p>Ahmad is working on <ahref="https://github.com/creativecommons/creativecommons-wordpress-plugin">the CC WordPress plugin</a> as part of <ahref="/gsoc-2019">Google Summer of Code 2019</a>.</p>
159
+
<p>Ahmad is working on <ahref="https://github.com/creativecommons/creativecommons-wordpress-plugin">the CC WordPress plugin</a> as part of <ahref="/gsoc-2019/">Google Summer of Code 2019</a>.</p>
<p>Chidiebere Onyegbuchulem is a Frontend developer based in Lagos, Nigeria.</p>
159
-
<p>Chidi is currently working on <ahref="https://github.com/creativecommons/cc-vocabulary">CC Vocabulary</a> as part of 2019-2020 <ahref="/programs/outreachy/2019-12-start">Outreachy Internship</a>.</p>
159
+
<p>Chidi is currently working on <ahref="https://github.com/creativecommons/cc-vocabulary">CC Vocabulary</a> as part of 2019-2020 <ahref="/programs/outreachy/2019-12-start/">Outreachy Internship</a>.</p>
<p>Dhruv Bhanushali is a Mumbai-based software developer and an Engineering-Physics graduate from IIT Roorkee. He started programming as a hobby in high-school and having found his calling, is now pursuing a career in the field. He is a huge fan of alternative and post-rock music and keeps his curated collection with him at all times. He also loves to binge watch TV shows and movies, especially indie art films.</p>
159
-
<p>Dhruv developed <ahref="https://opensource.creativecommons.org/cc-vocabulary/">CC Vocabulary</a> as part of <ahref="/gsoc-2019">Google Summer of Code 2019</a> and now is a maintainer for the project. He is consistently <ahref="https://dhruvkb.github.io/"><code>@dhruvkb</code></a> everywhere.</p>
159
+
<p>Dhruv developed <ahref="https://opensource.creativecommons.org/cc-vocabulary/">CC Vocabulary</a> as part of <ahref="/gsoc-2019/">Google Summer of Code 2019</a> and now is a maintainer for the project. He is consistently <ahref="https://dhruvkb.github.io/"><code>@dhruvkb</code></a> everywhere.</p>
<p><ahref="https://creativecommons.org/author/obulat/">Olga</a> is a developer based in Istanbul, Turkey. She loves programming in Python and Javascript. Her main areas of interest are web development, Natural Language Processing, languages, geography and education. Apart from that, she is busy raising her (soon to be) three kids.</p>
159
-
<p>Olga is currently working on improving <ahref="https://github.com/creativecommons/cc-chooser">the CC License Chooser</a> as part of 2019-2020 <ahref="/programs/outreachy">Outreachy Internship</a>.</p>
159
+
<p>Olga is currently working on improving <ahref="https://github.com/creativecommons/cc-chooser">the CC License Chooser</a> as part of 2019-2020 <ahref="/programs/outreachy/">Outreachy Internship</a>.</p>
<p>Maria is a Bachelor of Computer Science from Ecuador. As a research assistant, she worked in projects including computer vision, the estimation of socio-economic indexes through CDRs analysis, and a machine learning model with sensors data. During her spare time, she likes to watch animes and read. She loves sports, especially soccer. She is also committed to environmental causes, and she is a huge fan of cats and dogs (she has 4 and 1 respectively).</p>
159
-
<p>Maria worked in the <ahref="https://github.com/creativecommons/cccatalog-dataviz">data visualizations of the CC Catalog</a> as part of <ahref="/gsoc-2019">Google Summer of Code 2019</a>, and is currently a mentor in this year's edition of the program.</p>
159
+
<p>Maria worked in the <ahref="https://github.com/creativecommons/cccatalog-dataviz">data visualizations of the CC Catalog</a> as part of <ahref="/gsoc-2019/">Google Summer of Code 2019</a>, and is currently a mentor in this year's edition of the program.</p>
<p>Subham Sahu is an undergraduate student from Indian Institute Of Technology, Ropar. He is currently working on the <ahref="https://github.com/creativecommons/cccatalog-dataviz">Linked Commons</a> as part of <ahref="/gsoc-2020">Google Summer of Code 2020</a>.</p>
158
+
<p>Subham Sahu is an undergraduate student from Indian Institute Of Technology, Ropar. He is currently working on the <ahref="https://github.com/creativecommons/cccatalog-dataviz">Linked Commons</a> as part of <ahref="/gsoc-2020/">Google Summer of Code 2020</a>.</p>
Copy file name to clipboardExpand all lines: blog/entries/cc-vocabulary-the-main-course/index.html
+1-1
Original file line number
Diff line number
Diff line change
@@ -313,7 +313,7 @@ <h2 class="mb-0">CC Vocabulary: the main course</h2>
313
313
<h3id="what-s-next">What's next</h3><p>There are a number of components under construction right now such as cards and social media buttons. They will be
314
314
published on the styleguide very soon. After these, the final month, phase III of of the project's GSoC term will be
315
315
spent continuously polishing the project to suit the needs of all CC apps as discovered during the integration with
316
-
CC Search as mentioned by <ahref="/blog/authors/brenoferreira">Breno Ferreira</a> in the 'Next steps' in his post on
316
+
CC Search as mentioned by <ahref="/blog/authors/brenoferreira/">Breno Ferreira</a> in the 'Next steps' in his post on
<p>In keeping with the culinary theme of this post, think of it as sweet sweet dessert.</p>
319
319
<h3id="closing-note">Closing note</h3><p>In closing, I would like to thank my GSoC mentor Hugo Solar as always for always being present to help and refer me to
Copy file name to clipboardExpand all lines: blog/entries/cc-vocabulary-week9-13/index.html
+1-1
Original file line number
Diff line number
Diff line change
@@ -196,7 +196,7 @@ <h3 id="where-i-am-now">Where I am now</h3><ul>
196
196
<li>Still working to improve where I am now </li>
197
197
</ul>
198
198
<h2id="whats-next?">Whats next?</h2><p>I will continue to contribute to CC open source projects especially to the Vocabulary project that I have become a part of. I would love to see the application of Vocabulary to the development of other CC platforms and applications. I also want to apply the skills that I have acquired to get a full-time software developer position.</p>
199
-
<p>My special appreciation to Outreachy for this opportunity, the entire CC team especially those I worked with, My mentors <ahref="/blog/authors/hugosolar">Hugo Solar</a> and <ahref="/blog/authors/dhruvkb">Dhruv Bhanushali</a> for their guidance, direction, and help whenever I got stuck, also to the Director of Engineering <ahref="/blog/authors/kgodey">Kriti Godey</a> for always checking up on me ensuring I had a wonderful internship experience.</p>
199
+
<p>My special appreciation to Outreachy for this opportunity, the entire CC team especially those I worked with, My mentors <ahref="/blog/authors/hugosolar/">Hugo Solar</a> and <ahref="/blog/authors/dhruvkb/">Dhruv Bhanushali</a> for their guidance, direction, and help whenever I got stuck, also to the Director of Engineering <ahref="/blog/authors/kgodey/">Kriti Godey</a> for always checking up on me ensuring I had a wonderful internship experience.</p>
Copy file name to clipboardExpand all lines: blog/feed.xml
+2-2
Original file line number
Diff line number
Diff line change
@@ -1105,7 +1105,7 @@ of an Amazon EC2.</em> (<a href="https://aws.amazon.com/amazon-lin
1105
1105
<li>Still working to improve where I am now </li>
1106
1106
</ul>
1107
1107
<h2 id="whats-next?">Whats next?</h2><p>I will continue to contribute to CC open source projects especially to the Vocabulary project that I have become a part of. I would love to see the application of Vocabulary to the development of other CC platforms and applications. I also want to apply the skills that I have acquired to get a full-time software developer position.</p>
1108
-
<p>My special appreciation to Outreachy for this opportunity, the entire CC team especially those I worked with, My mentors <a href="/blog/authors/hugosolar">Hugo Solar</a> and <a href="/blog/authors/dhruvkb">Dhruv Bhanushali</a> for their guidance, direction, and help whenever I got stuck, also to the Director of Engineering <a href="/blog/authors/kgodey">Kriti Godey</a> for always checking up on me ensuring I had a wonderful internship experience.</p>
1108
+
<p>My special appreciation to Outreachy for this opportunity, the entire CC team especially those I worked with, My mentors <a href="/blog/authors/hugosolar/">Hugo Solar</a> and <a href="/blog/authors/dhruvkb/">Dhruv Bhanushali</a> for their guidance, direction, and help whenever I got stuck, also to the Director of Engineering <a href="/blog/authors/kgodey/">Kriti Godey</a> for always checking up on me ensuring I had a wonderful internship experience.</p>
@@ -2825,7 +2825,7 @@ brainchild comes of age.</p>
2825
2825
<h3 id="what-s-next">What's next</h3><p>There are a number of components under construction right now such as cards and social media buttons. They will be
2826
2826
published on the styleguide very soon. After these, the final month, phase III of of the project's GSoC term will be
2827
2827
spent continuously polishing the project to suit the needs of all CC apps as discovered during the integration with
2828
-
CC Search as mentioned by <a href="/blog/authors/brenoferreira">Breno Ferreira</a> in the 'Next steps' in his post on
2828
+
CC Search as mentioned by <a href="/blog/authors/brenoferreira/">Breno Ferreira</a> in the 'Next steps' in his post on
<p>In keeping with the culinary theme of this post, think of it as sweet sweet dessert.</p>
2831
2831
<h3 id="closing-note">Closing note</h3><p>In closing, I would like to thank my GSoC mentor Hugo Solar as always for always being present to help and refer me to
<h2id="codes-of-conduct">Codes of Conduct</h2><p>This document provides incident reporting guidelines and an enforcement manual for the following codes of conduct used by Creative Commons:</p>
201
201
<ul>
202
-
<li><ahref="/community/code-of-conduct">CC Open Source Code of Conduct</a></li>
202
+
<li><ahref="/community/code-of-conduct/">CC Open Source Code of Conduct</a></li>
203
203
<li><ahref="https://wiki.creativecommons.org/wiki/Slack/Code_of_Conduct">Slack/Code of Conduct</a></li>
204
204
</ul>
205
205
<h2id="reporting-guidelines">Reporting Guidelines</h2><p>If you believe someone is violating the code of conduct, we ask that you report it to Creative Commons by emailing
Copy file name to clipboardExpand all lines: community/community-team/index.html
+2-2
Original file line number
Diff line number
Diff line change
@@ -199,8 +199,8 @@ <h3 id="benefits-of-joining-the-community-team">Benefits of joining the Communit
199
199
<h2id="roles">Roles</h2><p>There are two main groups of roles – project roles and community building roles. Project roles are intended for folks interested in contributing to a specific project or codebase. Community building roles are for folks interested in interacting with people and helping grow the community.</p>
<li><ahref="/community/community-team/community-building-roles/">Community building roles</a></li>
204
204
</ul>
205
205
<p>Please note that we do not expect you to do work just because you have a role on the Community Team. Any role you are granted is based on appreciation for the work you’ve <em>already</em> done.</p>
206
206
<h2id="how-to-apply">How to Apply</h2><p>Please apply via <ahref="https://forms.gle/zDmp4yu2Yw2ktcsR8">this Google Form</a>.</p>
Copy file name to clipboardExpand all lines: community/index.html
+1-1
Original file line number
Diff line number
Diff line change
@@ -171,7 +171,7 @@ <h1 class="page-title pb-3 mb-4">Join the CC Developer Community</h1>
171
171
</ul>
172
172
</div>
173
173
</div>
174
-
<pclass="lead">Join our Slack or 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 <ahref="/blog">CC Open Source Blog</a> or via <ahref="https://twitter.com/cc_opensource">Twitter</a>.</p><h2id="mailing-lists">Mailing Lists</h2><p><strong>CC Developers</strong>: For general technical discussion open to all members. Join <ahref="https://groups.google.com/a/creativecommons.org/forum/#!forum/cc-developers">on Google Groups</a> or by sending an email to <code>cc-developers+subscribe@creativecommons.org</code>.</p>
174
+
<pclass="lead">Join our Slack or 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 <ahref="/blog/">CC Open Source Blog</a> or via <ahref="https://twitter.com/cc_opensource">Twitter</a>.</p><h2id="mailing-lists">Mailing Lists</h2><p><strong>CC Developers</strong>: For general technical discussion open to all members. Join <ahref="https://groups.google.com/a/creativecommons.org/forum/#!forum/cc-developers">on Google Groups</a> or by sending an email to <code>cc-developers+subscribe@creativecommons.org</code>.</p>
175
175
<p><strong>CC Usability Announcements</strong>: Announcement-only list for users to sign up for usability testing. Join <ahref="https://groups.google.com/a/creativecommons.org/forum/#!forum/usability-announce">on Google Groups</a> or by sending an email to <code>usability-announce+subscribe@creativecommons.org</code>.</p>
176
176
<h2id="slack">Slack</h2><p>Creative Commons has a large Slack community with sub-communities for tech/developers (of course), the <ahref="https://network.creativecommons.org/">CC Global Network</a>, specific countries, open education, GLAM, and more. It is open to the public and you can <ahref="http://slack-signup.creativecommons.org/">sign up here</a>. If you're not familiar with Slack, please read <ahref="https://get.slack.help/hc/en-us/categories/360000049043">"Getting Started" on Slack's usage guide</a>. Information on joining a specific channel is on <ahref="https://get.slack.help/hc/en-us/articles/205239967-Join-a-channel">"Join a channel"</a>.</p>
177
177
<p>Once you join, please introduce yourself in the <code>#cc-developers</code> channel.</p>
Copy file name to clipboardExpand all lines: community/write-a-blog-post/index.html
+3-3
Original file line number
Diff line number
Diff line change
@@ -165,7 +165,7 @@ <h1 class="page-title pb-3 mb-4">Write a Blog Post</h1>
165
165
</ul>
166
166
</div>
167
167
</div>
168
-
<pclass="lead">We invite members of the Creative Commons community to write guest posts on <ahref="/blog">our technical blog</a>.</p><h2id="what-to-write-about">What to write about</h2><p>You can write about anything that generally intersects with CC and technology. Some examples:</p>
168
+
<pclass="lead">We invite members of the Creative Commons community to write guest posts on <ahref="/blog/">our technical blog</a>.</p><h2id="what-to-write-about">What to write about</h2><p>You can write about anything that generally intersects with CC and technology. Some examples:</p>
169
169
<ul>
170
170
<li>a new CC or copyright related tool you've built</li>
171
171
<li>your use of CC's official tools or services</li>
@@ -174,7 +174,7 @@ <h1 class="page-title pb-3 mb-4">Write a Blog Post</h1>
174
174
<li>guides to best practices of working with technologies in the context of a CC-related project</li>
175
175
<li><em>your idea here</em></li>
176
176
</ul>
177
-
<p>It is a good idea to float what you're going to write about <ahref="/community">with the CC tech team</a> ahead of time so that we can give you feedback before you put in the work of writing it.</p>
177
+
<p>It is a good idea to float what you're going to write about <ahref="/community/">with the CC tech team</a> ahead of time so that we can give you feedback before you put in the work of writing it.</p>
178
178
<h2id="writing-tips">Writing tips</h2><p><strong>Structuring posts about your project</strong><br>
179
179
If you're writing about a project you're working on, here are a few ways you could structure your post:</p>
180
180
<ul>
@@ -184,7 +184,7 @@ <h2 id="writing-tips">Writing tips</h2><p><strong>Structuring posts about your p
184
184
<li>Write an overview of how your project works without as much narrative (example: <ahref="https://creativecommons.github.io/blog/entries/cc-catalog-leverage-open-data-1/">this post about the CC Catalog</a>)</li>
185
185
</ul>
186
186
<pclass="text-muted"><em>If you have more tips, <ahref="https://github.com/creativecommons/creativecommons.github.io-source/blob/master/content/community/write-a-blog-post/contents.lr">submit an edit to this page</a>.</em></p><h2id="how-to-post">How to post</h2><p>Once you have written your post, you can either send it to us (Markdown is easiest for us, but we're happy to work with other formats) or directly create a pull request for your post as detailed below.</p>
187
-
<p><ahref="/contributing-code/pr-guidelines">Pull requests</a> should be submitted to the <strong><ahref="https://github.com/creativecommons/creativecommons.github.io-source">creativecommons.github.io-source</a> repository</strong>. The CC Open Source site is built using the static site generator <ahref="https://www.getlektor.com/">Lektor</a> and your blog post must follow the specific format documented below to appear correctly on the site. For example, please see <ahref="https://github.com/creativecommons/creativecommons.github.io-source/commit/eac3fbc23b7cadb58fe49d3af3286e4c8bf20d2f">this commit adding a post</a>.</p>
187
+
<p><ahref="/contributing-code/pr-guidelines/">Pull requests</a> should be submitted to the <strong><ahref="https://github.com/creativecommons/creativecommons.github.io-source">creativecommons.github.io-source</a> repository</strong>. The CC Open Source site is built using the static site generator <ahref="https://www.getlektor.com/">Lektor</a> and your blog post must follow the specific format documented below to appear correctly on the site. For example, please see <ahref="https://github.com/creativecommons/creativecommons.github.io-source/commit/eac3fbc23b7cadb58fe49d3af3286e4c8bf20d2f">this commit adding a post</a>.</p>
188
188
<ol>
189
189
<li>Each blog entry lives in its own subdirectory of the <ahref="https://github.com/creativecommons/creativecommons.github.io-source/tree/master/content/blog/entries">content/blog/entries</a> folder. Create a new subdirectory with a <ahref="https://blog.tersmitten.nl/slugify/">slugified</a> version of your blog post title.</li>
190
190
<li>Create a file named <code>contents.lr</code> in the subdirectory you just created. This is the file that will contain your blog post content.</li>
0 commit comments