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
Copy file name to clipboardExpand all lines: content/archives/old-tech-blog/entries/ccsearch-testing-progress/contents.lr
+2-2
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ body:
9
9
10
10
Two months ago we set out to develop a brand new interface for [search.creativecommons.org](http://search.creativecommons.org). During that time, two UIs have been in testing alongside the current search. All visitors have had the option to switch their experience over to one of the beta versions.
11
11
12
-
1.[A drop-down list](/demos/search/search1) of supported search engines
13
-
2.[A radio button group](/demos/search/search2) of search engines
12
+
1.[A drop-down list](/demos/search/search1/) of supported search engines
13
+
2.[A radio button group](/demos/search/search2/) of search engines
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.
9
9
10
-
Ahmad is working on [the CC WordPress plugin](https://github.com/creativecommons/creativecommons-wordpress-plugin) as part of [Google Summer of Code 2019](/gsoc-2019).
10
+
Ahmad is working on [the CC WordPress plugin](https://github.com/creativecommons/creativecommons-wordpress-plugin) as part of [Google Summer of Code 2019](/gsoc-2019/).
Chidiebere Onyegbuchulem is a Frontend developer based in Lagos, Nigeria.
9
9
10
-
Chidi is currently working on [CC Vocabulary](https://github.com/creativecommons/cc-vocabulary) as part of 2019-2020 [Outreachy Internship](/programs/outreachy/2019-12-start).
10
+
Chidi is currently working on [CC Vocabulary](https://github.com/creativecommons/cc-vocabulary) as part of 2019-2020 [Outreachy Internship](/programs/outreachy/2019-12-start/).
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.
9
9
10
-
Dhruv developed [CC Vocabulary](https://opensource.creativecommons.org/cc-vocabulary/) as part of [Google Summer of Code 2019](/gsoc-2019) and now is a maintainer for the project. He is consistently [`@dhruvkb`](https://dhruvkb.github.io/) everywhere.
10
+
Dhruv developed [CC Vocabulary](https://opensource.creativecommons.org/cc-vocabulary/) as part of [Google Summer of Code 2019](/gsoc-2019/) and now is a maintainer for the project. He is consistently [`@dhruvkb`](https://dhruvkb.github.io/) everywhere.
[Olga](https://creativecommons.org/author/obulat/) 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.
9
9
10
-
Olga is currently working on improving [the CC License Chooser](https://github.com/creativecommons/cc-chooser) as part of 2019-2020 [Outreachy Internship](/programs/outreachy).
10
+
Olga is currently working on improving [the CC License Chooser](https://github.com/creativecommons/cc-chooser) as part of 2019-2020 [Outreachy Internship](/programs/outreachy/).
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).
9
9
10
-
Maria worked in the [data visualizations of the CC Catalog](https://github.com/creativecommons/cccatalog-dataviz) as part of [Google Summer of Code 2019](/gsoc-2019), and is currently a mentor in this year's edition of the program.
10
+
Maria worked in the [data visualizations of the CC Catalog](https://github.com/creativecommons/cccatalog-dataviz) as part of [Google Summer of Code 2019](/gsoc-2019/), and is currently a mentor in this year's edition of the program.
Subham Sahu is an undergraduate student from Indian Institute Of Technology, Ropar. He is currently working on the [Linked Commons](https://github.com/creativecommons/cccatalog-dataviz) as part of [Google Summer of Code 2020](/gsoc-2020).
8
+
Subham Sahu is an undergraduate student from Indian Institute Of Technology, Ropar. He is currently working on the [Linked Commons](https://github.com/creativecommons/cccatalog-dataviz) as part of [Google Summer of Code 2020](/gsoc-2020/).
Copy file name to clipboardExpand all lines: content/blog/entries/cc-vocabulary-week9-13/contents.lr
+1-1
Original file line number
Diff line number
Diff line change
@@ -54,4 +54,4 @@ Before this internship, I had just switched careers from Network engineering to
54
54
55
55
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.
56
56
57
-
My special appreciation to Outreachy for this opportunity, the entire CC team especially those I worked with, My mentors [Hugo Solar](/blog/authors/hugosolar) and [Dhruv Bhanushali](/blog/authors/dhruvkb) for their guidance, direction, and help whenever I got stuck, also to the Director of Engineering [Kriti Godey](/blog/authors/kgodey) for always checking up on me ensuring I had a wonderful internship experience.
57
+
My special appreciation to Outreachy for this opportunity, the entire CC team especially those I worked with, My mentors [Hugo Solar](/blog/authors/hugosolar/) and [Dhruv Bhanushali](/blog/authors/dhruvkb/) for their guidance, direction, and help whenever I got stuck, also to the Director of Engineering [Kriti Godey](/blog/authors/kgodey/) for always checking up on me ensuring I had a wonderful internship experience.
Copy file name to clipboardExpand all lines: content/community/community-team/contents.lr
+2-2
Original file line number
Diff line number
Diff line change
@@ -29,8 +29,8 @@ Joining [one of our community forums](https://opensource.creativecommons.org/com
29
29
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.
*[Community building roles](/community/community-team/community-building-roles/)
34
34
35
35
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 _already_ done.
Copy file name to clipboardExpand all lines: content/community/write-a-blog-post/contents.lr
+2-2
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ You can write about anything that generally intersects with CC and technology. S
18
18
- guides to best practices of working with technologies in the context of a CC-related project
19
19
-*your idea here*
20
20
21
-
It is a good idea to float what you're going to write about [with the CC tech team](/community) ahead of time so that we can give you feedback before you put in the work of writing it.
21
+
It is a good idea to float what you're going to write about [with the CC tech team](/community/) ahead of time so that we can give you feedback before you put in the work of writing it.
22
22
23
23
## Writing tips
24
24
@@ -35,7 +35,7 @@ If you're writing about a project you're working on, here are a few ways you cou
35
35
36
36
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.
37
37
38
-
[Pull requests](/contributing-code/pr-guidelines) should be submitted to the **[creativecommons.github.io-source](https://github.com/creativecommons/creativecommons.github.io-source) repository**. The CC Open Source site is built using the static site generator [Lektor](https://www.getlektor.com/) and your blog post must follow the specific format documented below to appear correctly on the site. For example, please see [this commit adding a post](https://github.com/creativecommons/creativecommons.github.io-source/commit/eac3fbc23b7cadb58fe49d3af3286e4c8bf20d2f).
38
+
[Pull requests](/contributing-code/pr-guidelines/) should be submitted to the **[creativecommons.github.io-source](https://github.com/creativecommons/creativecommons.github.io-source) repository**. The CC Open Source site is built using the static site generator [Lektor](https://www.getlektor.com/) and your blog post must follow the specific format documented below to appear correctly on the site. For example, please see [this commit adding a post](https://github.com/creativecommons/creativecommons.github.io-source/commit/eac3fbc23b7cadb58fe49d3af3286e4c8bf20d2f).
39
39
40
40
1. Each blog entry lives in its own subdirectory of the [content/blog/entries](https://github.com/creativecommons/creativecommons.github.io-source/tree/master/content/blog/entries) folder. Create a new subdirectory with a [slugified](https://blog.tersmitten.nl/slugify/) version of your blog post title.
41
41
1. Create a file named `contents.lr` in the subdirectory you just created. This is the file that will contain your blog post content.
Copy file name to clipboardExpand all lines: content/contributing-code/contents.lr
+3-3
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ We do all of our development [on GitHub](https://github.com/creativecommons/). I
12
12
13
13
## Finding an issue
14
14
15
-
Here's a list of [all our current projects](/projects). We use GitHub issues associated with each project to track the work associated with that project. That's where you can find things to work on.
15
+
Here's a list of [all our current projects](/projects/). We use GitHub issues associated with each project to track the work associated with that project. That's where you can find things to work on.
16
16
17
17
We make extensive use of issue labels to desginate the status of various issues. We have a standard set of labels across all projects, [documented here](https://github.com/creativecommons/ccos-scripts/blob/master/normalize_repos/labels.py). Here are some of the ones that are most relevant to finding a good issue to work on:
18
18
@@ -39,7 +39,7 @@ Once you've found an issue you'd like to work on, please follow these steps to m
39
39
40
40
1. Comment on it and say you're working on that issue. This is to avoid conflicts with others also working on the issue.
41
41
* A project maintainer may mark the issue with an `in progress` label at this point, but we don't always get around to that.
42
-
2. Write your code and submit your pull request. Be sure to read and follow our **[pull request guidelines](/contributing-code/pr-guidelines)**!
42
+
2. Write your code and submit your pull request. Be sure to read and follow our **[pull request guidelines](/contributing-code/pr-guidelines/)**!
43
43
3. Wait for code review and address any issues raised as soon as you can.
44
44
45
45
**A note on collaboration:** We encourage people to collaborate as much as possible. We especially appreciate contributors reviewing each others pull requests, as long as you are [kind and constructive](https://medium.com/@otarutunde/comments-during-code-reviews-2cb7791e1ac7) when you do so.
@@ -53,4 +53,4 @@ If you want to work on something that there is no GitHub issue for, follow these
53
53
2. The issue will automatically have the `not ready for work` label applied. Wait for a project maintainer to evaluate your issue and decide whether it's something that we will accept a pull request for.
54
54
3. Once the project maintainer has approved the issue and removed the `not ready for work` label, you may start work on code as described in the "Contribution process" section above.
55
55
56
-
When in doubt, ask a question on [one of our community forums](/community).
56
+
When in doubt, ask a question on [one of our community forums](/community/).
Copy file name to clipboardExpand all lines: content/contributing-code/github-repo-guidelines/contents.lr
+1-1
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,6 @@ Each repo should have a `.cc-metadata.yml` file in the root directory with the f
64
64
</code>
65
65
</pre>
66
66
67
-
This metadata file is used in the [Projects](/projects) page. Repos that are marked as non-engineering projects are not displayed in the page and repos marked as featured as displayed at the top of the page. Repos should be marked as featured if we are actively looking for community contributions and have the bandwidth to review them quickly.
67
+
This metadata file is used in the [Projects](/projects/) page. Repos that are marked as non-engineering projects are not displayed in the page and repos marked as featured as displayed at the top of the page. Repos should be marked as featured if we are actively looking for community contributions and have the bandwidth to review them quickly.
68
68
69
69
Repos without this metadata file are treated as `engineering_projects: true`, `featured: false` and `slack: ""`. A default is necessary since it will take time for us to clean up and add metadata to all our repos.
Copy file name to clipboardExpand all lines: content/internships/applicant-guide/contents.lr
+4-4
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ title: Open Source Internships: Applicant Guide
6
6
---
7
7
body:
8
8
9
-
Creative Commons participates in open source mentorship programs such as [Google Summer of Code](https://summerofcode.withgoogle.com/), [Google Season of Docs](https://developers.google.com/season-of-docs/), and [Outreachy](https://www.outreachy.org/). Details about specific programs and rounds are listed in the [Overview page](/internships); this page serves as a general guide to applicants.
9
+
Creative Commons participates in open source mentorship programs such as [Google Summer of Code](https://summerofcode.withgoogle.com/), [Google Season of Docs](https://developers.google.com/season-of-docs/), and [Outreachy](https://www.outreachy.org/). Details about specific programs and rounds are listed in the [Overview page](/internships/); this page serves as a general guide to applicants.
10
10
11
11
## Getting Started
12
12
@@ -28,7 +28,7 @@ If you have a question about how we work, our programs, our licenses, or anythin
28
28
[Join the `#cc-gsoc-outreachy` channel on the CC Slack or the CC Developers mailing list](/community/) as early as possible to introduce yourself and get feedback on your ideas. All our mentors will be on Slack and respond to emails on the mailing list and it is better to post there rather than contacting them individually. Feel free to ask questions!
29
29
30
30
### Pick a Project
31
-
Your next step should be to pick a particular project that you're interested in working on. The [Overview page](/internships) will cover the current internship rounds and link to related project ideas.
31
+
Your next step should be to pick a particular project that you're interested in working on. The [Overview page](/internships/) will cover the current internship rounds and link to related project ideas.
32
32
33
33
Once you pick the project you're interested in, make sure to learn about the project thoroughly. You're going to be spending three months working on the project and you'll need to understand what the work entails so that you can plan the work out ahead of time and submit a strong application. The project descriptions are quite short so we expect you to do a lot of work here duron your own taking those descriptions and fleshing them out into a more detailed project plan and implementation timeline.
34
34
@@ -46,7 +46,7 @@ The final step is to create a draft application and share it with your chosen pr
46
46
Contributions are for you to get a sense of what it's like to contribute to an open source project (getting used to the GitHub workflow, interacting with other contributors, etc.) and for us to see a sample of your work/skills. If we are impressed by your contributions, we are more likely to select you as an intern.
47
47
48
48
### How to contribute
49
-
Please read our [Contributing Code](/contributing-code) page for information on how to contribute. You can contribute to any Creative Commons repository, although it's better if you demonstrate skills related to the project you are applying for. Also, check your project's description for more specific contribution guidelines (not all of them will have them).
49
+
Please read our [Contributing Code](/contributing-code/) page for information on how to contribute. You can contribute to any Creative Commons repository, although it's better if you demonstrate skills related to the project you are applying for. Also, check your project's description for more specific contribution guidelines (not all of them will have them).
50
50
51
51
If you're applying via Outreachy, remember to record your contribution via the Outreachy website! You can record contributions even if you have not yet received feedback on them or if they have not been merged – our mentors are busy so we can be slow to provide feedback.
52
52
@@ -76,7 +76,7 @@ If you are applying for Outreachy, please link to the project proposal document
76
76
77
77
## Contacting Mentors
78
78
79
-
All the CC mentors are on [Slack](/community). **Please use public channels on Slack as the primary method of communication.** Public channels are better than direct messages because it allows any available mentor (or even another applicant) to answer your questions and interact with you. It also allows other applicants who have the same questions to benefit from the answers the mentor is giving you.
79
+
All the CC mentors are on [Slack](/community/). **Please use public channels on Slack as the primary method of communication.** Public channels are better than direct messages because it allows any available mentor (or even another applicant) to answer your questions and interact with you. It also allows other applicants who have the same questions to benefit from the answers the mentor is giving you.
80
80
81
81
**Please ask mentors specific questions.** We don't know how to help you get started unless we know what you have questions about. People come from a variety of experiences and backgrounds and the things you may be confused about may be totally different than the things that someone else has questions about. Please give us as much information as possible, the more you tell us, the better we can help you.
0 commit comments