diff --git a/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr b/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr index a3e4009ed..945ff9d1c 100644 --- a/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr +++ b/content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr @@ -51,9 +51,9 @@ De esta manera hemos decidido participar de las siguientes rondas de ambos progr - [Guia de estudiante](https://www.outreachy.org/docs/internship/) ### CC Open Source -- [Guia del postulante](https://opensource.creativecommons.org/programs/contrib-guide/) -- [Listado de proyectos](https://opensource.creativecommons.org/contributing-code/projects/) -- [Lineamientos para contribuir](https://opensource.creativecommons.org/contributing-code/) +- [Guia del postulante](/programs/contrib-guide/) +- [Listado de proyectos](/contributing-code/projects/) +- [Lineamientos para contribuir](/contributing-code/) ## Beneficios Estos programas proveen múltiples beneficios a quienes deseen participar de ellos, por un lado, las organizaciones participantes trabajan en proyectos de código abierto utilizados en todo el mundo y en diversas aplicaciones, convirtiéndose en una oportunidad única de contribuir a proyectos de gran escala que además cuentan con comunidades globales transformando además esta pasantía en una experiencia enriquecedora. @@ -64,10 +64,10 @@ Además, estos programas consideran un estipendio por los 3 meses que dura la pa ## Destrezas -Con respecto al idioma, para participar en estos programas no se exige un manejo del inglés al 100%, solo basta que puedas comunicarte de manera razonable, ya que, si bien, existen algunos proyectos en los cuales yo soy el mentor ( [WP Plugin](https://opensource.creativecommons.org/internships/project-ideas/all/#wp-plugin) e [Implementar Vocabulary](https://opensource.creativecommons.org/internships/project-ideas/all/#vocabulary-integration) ) y podemos tener reuniones en español, la comunicación pública y la documentación debe ser en Inglés. +Con respecto al idioma, para participar en estos programas no se exige un manejo del inglés al 100%, solo basta que puedas comunicarte de manera razonable, ya que, si bien, existen algunos proyectos en los cuales yo soy el mentor ( [WP Plugin](/internships/project-ideas/all/#wp-plugin) e [Implementar Vocabulary](/internships/project-ideas/all/#vocabulary-integration) ) y podemos tener reuniones en español, la comunicación pública y la documentación debe ser en Inglés. Con respecto a nuestros proyectos, todos se encuentran en [Github](https://github.com/creativecommons) por lo tanto debes saber lo básico de [Git](https://rogerdudler.github.io/git-guide/index.es.html). Te recomiendo consultar la [ayuda de Github](https://help.github.com/es) para mayor detalle, sugiero poner atención a la guia sobre como realizar [Pull Request](https://help.github.com/es/github/collaborating-with-issues-and-pull-requests/about-pull-requests) ya que es muy necesario para el flujo de trabajo del equipo tecnico de CC y lo será también para tu pasantía. ## Invitación -Desde yá los dejamos invitados a participar en estos programas o a participar directamente en nuestra [comunidad de código abierto](https://opensource.creativecommons.org/) o visitar nuestro [Github](https://github.com/creativecommons), el cual contiene nuestros proyectos. También pueden unirse a nuestra comunidad global en [Slack](https://slack-signup.creativecommons.org/) donde me pueden encontrar como @hugo si tienen alguna duda o comentario. +Desde yá los dejamos invitados a participar en estos programas o a participar directamente en nuestra [comunidad de código abierto](/) o visitar nuestro [Github](https://github.com/creativecommons), el cual contiene nuestros proyectos. También pueden unirse a nuestra comunidad global en [Slack](https://slack-signup.creativecommons.org/) donde me pueden encontrar como @hugo si tienen alguna duda o comentario. diff --git a/content/blog/entries/2020-03-05-participe-gsoc/contents.lr b/content/blog/entries/2020-03-05-participe-gsoc/contents.lr index a70879c52..26dee92df 100644 --- a/content/blog/entries/2020-03-05-participe-gsoc/contents.lr +++ b/content/blog/entries/2020-03-05-participe-gsoc/contents.lr @@ -28,17 +28,17 @@ O estágio é remunerado naturalmente. Os valores pagos aos estagiários pelo Go Caso voce se interesse em participar do GSoC ou Outreachy esse ano, seguem algumas dicas que poderão te ajudar no seu processo de aplicação e submissão de projeto: -Leia o conteúdo disponível online sobre como o programa funciona. [Google Summer of Code](https://summerofcode.withgoogle.com/how-it-works] e [Outreachy](https://www.outreachy.org/docs/applicant/). Assim voce irá poder entender a proposta do programa, sua estrutura e tirar suas dúvidas; [nossa lista de projetos](https://opensource.creativecommons.org/internships/project-ideas/all/) que estamos sugerindo esse ano para os estudantes trabalhar e ver qual projeto está melhor alinhado com seus interesses e habilidades; e [nosso guia para candidatos](https://opensource.creativecommons.org/programs/applicant-guide/) para entender o passo a passo de como nós iremos trabalhar com candidatos e estudantes selecionados para participar do programa. Esse conteúdo está todo em inglês. +Leia o conteúdo disponível online sobre como o programa funciona. [Google Summer of Code](https://summerofcode.withgoogle.com/how-it-works] e [Outreachy](https://www.outreachy.org/docs/applicant/). Assim voce irá poder entender a proposta do programa, sua estrutura e tirar suas dúvidas; [nossa lista de projetos](/internships/project-ideas/all/) que estamos sugerindo esse ano para os estudantes trabalhar e ver qual projeto está melhor alinhado com seus interesses e habilidades; e [nosso guia para candidatos](/programs/applicant-guide/) para entender o passo a passo de como nós iremos trabalhar com candidatos e estudantes selecionados para participar do programa. Esse conteúdo está todo em inglês. -Sobre inglês, para ser selecionado para trabalhar conosco, é necessário que voce consiga se comunicar razoavelmente bem em inglês. A Creative Commons é uma organização internacional e voce precisará se comunicar com pessoas da organização e da comunidade que não falam português. Eu, Breno Ferreira, autor desse post, falo portugues então caso voce se interesse pelo [projeto que serei responsável](https://opensource.creativecommons.org/internships/project-ideas/all/#cc-search-accessibility), eu poderei me comunicar em privado em portugues, mas toda comunicação dos estudantes em canais públicos deverá ser em inglês. Voce não precisa ser 100% fluente, mas precisa conseguir entender e se fazer entender no idioma. +Sobre inglês, para ser selecionado para trabalhar conosco, é necessário que voce consiga se comunicar razoavelmente bem em inglês. A Creative Commons é uma organização internacional e voce precisará se comunicar com pessoas da organização e da comunidade que não falam português. Eu, Breno Ferreira, autor desse post, falo portugues então caso voce se interesse pelo [projeto que serei responsável](/internships/project-ideas/all/#cc-search-accessibility), eu poderei me comunicar em privado em portugues, mas toda comunicação dos estudantes em canais públicos deverá ser em inglês. Voce não precisa ser 100% fluente, mas precisa conseguir entender e se fazer entender no idioma. O GSoC é um programa focado em contribuições de código, afinal, chama-se Google Summer of Code. Então, voce precisa ter alguns conhecimentos básicos de algumas ferramentas para uma boa participação no programa. Voce precisará saber usar Git e Github. Todos os projetos da Creative Commons estão no Github e o conhecimento básico dessas ferramentas é fundamental. A [documentação do Github](https://help.github.com/pt) pode ajudar, principalmente a parte sobre [como funcionam os Pull Requests](https://help.github.com/pt/github/collaborating-with-issues-and-pull-requests/about-pull-requests) pois é um recurso bem particular do Github e é normal algumas pessoas não saberem utilizar esse recurso muito importante. -Na nossa página de [ideias de projetos](https://opensource.creativecommons.org/internships/project-ideas/all/) os projetos listam as habilidades recomendadas para quem se interessar (listado em *Skills recommended*). Verifique se essas habilidades se alinham com as suas. +Na nossa página de [ideias de projetos](/internships/project-ideas/all/) os projetos listam as habilidades recomendadas para quem se interessar (listado em *Skills recommended*). Verifique se essas habilidades se alinham com as suas. -Nessa fase inicial, o ideal é voce começar a fazer algumas contribuições nos projetos que te interessam. Por exemplo, se voce se interessou pelo projeto de Acessibilidade e Internacionalização do CC Search, o repositório no Github relacionado é . De uma olhada na [lista de issues](https://github.com/creativecommons/cccatalog-frontend/issues) que estão marcadas com os labels ["Good First Issue"](https://github.com/creativecommons/cccatalog-frontend/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) e ["Help Wanted"](https://github.com/creativecommons/cccatalog-frontend/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22). Essas são as tarefas que nós consideramos as melhores para quem quer começar a contribuir para o projeto. Os nossos principais repositórios tem todos issues marcadas com esses labels. É muito importante também ler a documentação do projeto. Leia o arquivo README no repositório. Nossos projetos também possuem um arquivo CONTRIBUTING.md que contém o código de conduta para quem for contribuir com o projeto, e também um guia sobre como contribuir com aquele projeto em específico. Além disso, é interessante também voce [participar da comunidade](https://opensource.creativecommons.org/community/). Entre no nosso Slack e participe dos canais abertos. As pessoas estão lá interagindo, postando comentarios e tirando dúvidas conosco e outros membros em um ambiente respeitoso e cordial. +Nessa fase inicial, o ideal é voce começar a fazer algumas contribuições nos projetos que te interessam. Por exemplo, se voce se interessou pelo projeto de Acessibilidade e Internacionalização do CC Search, o repositório no Github relacionado é . De uma olhada na [lista de issues](https://github.com/cc-archive/cccatalog-frontend/issues) que estão marcadas com os labels ["Good First Issue"](https://github.com/cc-archive/cccatalog-frontend/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) e ["Help Wanted"](https://github.com/cc-archive/cccatalog-frontend/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22). Essas são as tarefas que nós consideramos as melhores para quem quer começar a contribuir para o projeto. Os nossos principais repositórios tem todos issues marcadas com esses labels. É muito importante também ler a documentação do projeto. Leia o arquivo README no repositório. Nossos projetos também possuem um arquivo CONTRIBUTING.md que contém o código de conduta para quem for contribuir com o projeto, e também um guia sobre como contribuir com aquele projeto em específico. Além disso, é interessante também voce [participar da comunidade](/community/). Entre no nosso Slack e participe dos canais abertos. As pessoas estão lá interagindo, postando comentarios e tirando dúvidas conosco e outros membros em um ambiente respeitoso e cordial. Durante o periodo de submissão de projetos voce irá escrever sua proposta de projeto. É bastante importante que voce compartilhe o rascunho da sua proposta o mais cedo possível conosco para que possamos dar feedback e lhe dizer o que precisa ser melhorado. Se voce só compartilhar sua proposta no final do período de submissão, não teremos a oportunidade de dizer o que está bom e ruim e voce não poderá fazer nenhuma melhoria. Então recomendamos que voce compartilhe seus rascunhos com os mentores cedo e frequentemente. diff --git a/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr b/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr index ad29d90a9..5012ae82b 100644 --- a/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr +++ b/content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr @@ -26,9 +26,9 @@ author: kgodey pub_date: 2020-12-07 --- body: -Creative Commons (CC) is adopting a brand new organizational strategy in 2021, just in time for our 20th anniversary. As part of the organization's evolution in alignment with the new strategy, [Alden Page](https://opensource.creativecommons.org/blog/authors/aldenpage/), [Brent Moran](https://opensource.creativecommons.org/blog/authors/mathemancer/), [Hugo Solar](https://opensource.creativecommons.org/blog/authors/hugosolar/), and I ([Kriti Godey](https://opensource.creativecommons.org/blog/authors/kgodey/)) will have departed Creative Commons by the end of December. Moving forward, the CC staff engineering team of [Timid Robot Zehta](https://opensource.creativecommons.org/blog/authors/TimidRobot/) and [Zack Krida](https://opensource.creativecommons.org/blog/authors/zackkrida/) will focus on supporting a smaller set of core projects. +Creative Commons (CC) is adopting a brand new organizational strategy in 2021, just in time for our 20th anniversary. As part of the organization's evolution in alignment with the new strategy, [Alden Page](/blog/authors/aldenpage/), [Brent Moran](/blog/authors/mathemancer/), [Hugo Solar](/blog/authors/hugosolar/), and I ([Kriti Godey](/blog/authors/kgodey/)) will have departed Creative Commons by the end of December. Moving forward, the CC staff engineering team of [Timid Robot Zehta](/blog/authors/TimidRobot/) and [Zack Krida](/blog/authors/zackkrida/) will focus on supporting a smaller set of core projects. -We are extremely proud of the work we have done together to build CC's vibrant open source community over the past two years. And of course, we're thankful for all the amazing contributions that all our community members have made. We've made significant improvements to existing tools, and launched entirely new projects with your help. [We created Vocabulary,](https://opensource.creativecommons.org/blog/categories/cc-vocabulary/) a design system for Creative Commons and launched half a dozen sites using it. We added [dozens of new sources to CC Search](https://opensource.creativecommons.org/blog/categories/cc-catalog/) and improved [its accessibility](https://opensource.creativecommons.org/blog/authors/AyanChoudhary/). We released tools such as the [CC WordPress plugin](https://opensource.creativecommons.org/blog/authors/ahmadbilaldev/) and [CC Search browser extension](https://opensource.creativecommons.org/blog/authors/makkoncept/) that integrated CC licensing with widely used software. And, there's so much more. +We are extremely proud of the work we have done together to build CC's vibrant open source community over the past two years. And of course, we're thankful for all the amazing contributions that all our community members have made. We've made significant improvements to existing tools, and launched entirely new projects with your help. [We created Vocabulary,](/blog/categories/cc-vocabulary/) a design system for Creative Commons and launched half a dozen sites using it. We added [dozens of new sources to CC Search](/blog/categories/cc-catalog/) and improved [its accessibility](/blog/authors/AyanChoudhary/). We released tools such as the [CC WordPress plugin](/blog/authors/ahmadbilaldev/) and [CC Search browser extension](/blog/authors/makkoncept/) that integrated CC licensing with widely used software. And, there's so much more. ### Community Changes @@ -38,7 +38,7 @@ The CC Open Source community remains central to our engineering work, and we wil - We will invite all Community Team members to meetings and documents open to the community, regardless of role. - We will deprecate the "community-team-core" mailing list in favor of a single "community-team" mailing list. - We will have a new monthly Open Source Community meeting and cancel the existing biweekly Engineering Meeting. -- We will no longer have a paid Open Source Community Coordinator, [relying instead on volunteers](https://opensource.creativecommons.org/community/community-team/community-building-roles/) to help assist new community members, maintain our Twitter account, etc. +- We will no longer have a paid Open Source Community Coordinator, [relying instead on volunteers](/community/community-team/community-building-roles/) to help assist new community members, maintain our Twitter account, etc. We welcome new Community Team members and we will continue to participate in internship programs such as Google Summer of Code. @@ -65,9 +65,9 @@ We will continue to actively develop the following projects: The following projects are entering maintenance mode. The services will remain online, but we will not accept any new pull requests or deploy new code after Dec 15, 2020. -- [CC Catalog](https://github.com/creativecommons/cccatalog) -- [CC Catalog API](https://github.com/creativecommons/cccatalog-api) -- [CC Search](https://github.com/creativecommons/cccatalog-frontend/) +- [CC Catalog](https://github.com/cc-archive/cccatalog) +- [CC Catalog API](https://github.com/cc-archive/cccatalog-api) +- [CC Search](https://github.com/cc-archive/cccatalog-frontend/) - [Linked Commons](https://github.com/cc-archive/cccatalog-dataviz/) Catalog, API, and Linked Commons contributors are encouraged to contribute to our other Python projects such as the [CC Legal Database](https://github.com/creativecommons/legaldb) or the upcoming [CC Licenses](https://github.com/creativecommons/cc-licenses) project. If you are a CC Search contributor, we recommend checking out frontend projects such as the [CC Chooser](https://github.com/creativecommons/chooser) or [Vocabulary](https://github.com/creativecommons/vocabulary). diff --git a/content/blog/entries/2023-03-24-community-contributions/contents.lr b/content/blog/entries/2023-03-24-community-contributions/contents.lr index 1ea0c2bbb..65d46c01f 100644 --- a/content/blog/entries/2023-03-24-community-contributions/contents.lr +++ b/content/blog/entries/2023-03-24-community-contributions/contents.lr @@ -68,7 +68,7 @@ there's a gap or where revisions are needed, and how they should be corrected. Whether an Error or Feature/functionality Issue, once it's been submitted, in accordance with the [Contribution -Guidelines](https://opensource.creativecommons.org/contributing-code/), it will +Guidelines](/contributing-code/), it will move to a status of "awaiting triage". This means that it is waiting to be reviewed by one of the core codebase contributors. While it's in this state no implementation work should be done (no PRs, no code work to add or correct the @@ -114,8 +114,8 @@ in progress. If an Issue passes through this period as implementable, then it'll move to a status of "ready for work". This is the point at which it can be implemented, and a contributor can submit a Pull Request addressing it. (See the [Repository -Labels Status section](https://opensource.creativecommons.org/co -ntributing-code/repo-labels/#status) for more information) +Labels Status section](/contributing-code/repo-labels/#status) for more +information) During this process it is worth noting that there will be multiple types of contribution. For example: diff --git a/content/blog/entries/apache-airflow-testing-with-pytest/contents.lr b/content/blog/entries/apache-airflow-testing-with-pytest/contents.lr index 0e59e91c8..22281fdeb 100644 --- a/content/blog/entries/apache-airflow-testing-with-pytest/contents.lr +++ b/content/blog/entries/apache-airflow-testing-with-pytest/contents.lr @@ -198,4 +198,4 @@ We hope that these hints are helpful to the reader. For more, and for the context around the snippets shown here, please take a look at [the repo][frozen_cccatalog]. -[frozen_cccatalog]: https://github.com/creativecommons/cccatalog/tree/c4b80600eb5695cc294e1791ba90bdc3a408b7b9/src/cc_catalog_airflow \ No newline at end of file +[frozen_cccatalog]: https://github.com/cc-archive/cccatalog/tree/c4b80600eb5695cc294e1791ba90bdc3a408b7b9/src/cc_catalog_airflow \ No newline at end of file diff --git a/content/blog/entries/automate-github-for-more-than-CI CD/contents.lr b/content/blog/entries/automate-github-for-more-than-CI CD/contents.lr index 71ebf410c..3a5fa6cdf 100644 --- a/content/blog/entries/automate-github-for-more-than-CI CD/contents.lr +++ b/content/blog/entries/automate-github-for-more-than-CI CD/contents.lr @@ -63,7 +63,7 @@ categories: - 'critical' ``` -The resulting release notes require no manual editing at release time, and has saved us hours over time and allows our developers to focus on DevOps work instead of copywriting on release days. We also never miss a contribution or expression of gratitude to one of our contributors. You can read the [latest CC Search release notes](https://github.com/creativecommons/cccatalog-frontend/releases/latest) or [see our full release-drafter.yml file here](https://github.com/creativecommons/cccatalog-frontend/blob/develop/.github/release-drafter.yml). +The resulting release notes require no manual editing at release time, and has saved us hours over time and allows our developers to focus on DevOps work instead of copywriting on release days. We also never miss a contribution or expression of gratitude to one of our contributors. You can read the [latest CC Search release notes](https://github.com/cc-archive/cccatalog-frontend/releases/latest) or [see our full release-drafter.yml file here](https://github.com/cc-archive/cccatalog-frontend/blob/develop/.github/release-drafter.yml). ### Repository Normalization @@ -107,7 +107,7 @@ Internally and publicly, we use [GitHub Projects](https://github.com/orgs/creati ACCESS_TOKEN: ${{ secrets.ADMIN_GITHUB_TOKEN }} COLUMN_NAME: "In Progress (Community)" PROJECT_URL: https://github.com/orgs/creativecommons/projects/7 - REPO_URL: https://github.com/creativecommons/cccatalog-frontend + REPO_URL: https://github.com/cc-archive/cccatalog-frontend ``` We have additional scripts that sync our community team members across our open source website and GitHub, and several others that do even more of this cross-platform synchronization work. All of these scripts relive significant burden off of our engineering manager and open source community coordinator. diff --git a/content/blog/entries/building-distributed-indexer/contents.lr b/content/blog/entries/building-distributed-indexer/contents.lr index 47cc070fb..c7646d718 100644 --- a/content/blog/entries/building-distributed-indexer/contents.lr +++ b/content/blog/entries/building-distributed-indexer/contents.lr @@ -27,7 +27,7 @@ It turns out that, once your search index contains more than just a few million There is no off-the-shelf solution for this, particularly when performance is of concern; anybody in the business of writing a large search engine is going to have to write a custom indexer at some point. -In the end, given the size of our dataset was in the range of a few hundred gigabytes, it turned out that bulk reindexing every week would be good enough for our purposes; our current upstream data sources don’t update much more frequently than that anyway. We wrote a program that automated the procedure of refreshing our database with the latest upstream data and pushing it to Elasticsearch, all completely online and without negative impact to production performance. A single server was responsible for moving all of our image data around to the appropriate data stores and juggling temporary tables and indices to hide the indexing process from the end user. I wrote a little bit about the design of this piece in [a previous blog post](https://opensource.creativecommons.org/blog/entries/searching-300-million/). +In the end, given the size of our dataset was in the range of a few hundred gigabytes, it turned out that bulk reindexing every week would be good enough for our purposes; our current upstream data sources don’t update much more frequently than that anyway. We wrote a program that automated the procedure of refreshing our database with the latest upstream data and pushing it to Elasticsearch, all completely online and without negative impact to production performance. A single server was responsible for moving all of our image data around to the appropriate data stores and juggling temporary tables and indices to hide the indexing process from the end user. I wrote a little bit about the design of this piece in [a previous blog post](/blog/entries/searching-300-million/). ![Ingestion Server architecture](one_server_indexing.png) diff --git a/content/blog/entries/cc-browser-extension-a-gsoc-project/contents.lr b/content/blog/entries/cc-browser-extension-a-gsoc-project/contents.lr index 7418745ac..8bb084405 100644 --- a/content/blog/entries/cc-browser-extension-a-gsoc-project/contents.lr +++ b/content/blog/entries/cc-browser-extension-a-gsoc-project/contents.lr @@ -16,7 +16,7 @@ pub_date: 2019-06-20 --- body: -With the Creative Commons engineering team working very hard to catalog and index a plethora of CC-licensed works floating all over the internet, the next step is to make a suite of user-centric applications and interfaces to interact, consume and even reuse the content. The CC-Search is one such app with over [300 million CC-Licensed images indexed](https://creativecommons.github.io/blog/entries/cc-search-out-of-beta/) and since there is a full separation of concern between the backend ([CC-Catalog-API](https://github.com/creativecommons/cccatalog-api)) and frontend ([CC-Catalog-frontend](https://github.com/creativecommons/cccatalog-frontend)), we can leverage the backend architecture to design plugins for other platforms. +With the Creative Commons engineering team working very hard to catalog and index a plethora of CC-licensed works floating all over the internet, the next step is to make a suite of user-centric applications and interfaces to interact, consume and even reuse the content. The CC-Search is one such app with over [300 million CC-Licensed images indexed](/blog/entries/cc-search-out-of-beta/) and since there is a full separation of concern between the backend ([CC-Catalog-API](https://github.com/cc-archive/cccatalog-api)) and frontend ([CC-Catalog-frontend](https://github.com/cc-archive/cccatalog-frontend)), we can leverage the backend architecture to design plugins for other platforms. This GSoC project aims to do this by making a Cross-Browser extension to interact with CC-Catalog-API. @@ -61,6 +61,6 @@ Similarly, if we add a feature, say dark-mode, then the users who prefer it over ### How you can help The development is still in the initial phase but you can check out **a working extension** at the [Github Repository](https://github.com/creativecommons/ccsearch-browser-extension). There are instructions to help you get started and load it to Firefox. -Tell us what you expect the extension to do, or a feature that you wish would be implemented. At this early stage of development, it might help us improve our goals. You can join the discussion on `#gsoc-browser-ext` channel on [slack](http://creativecommons.github.io/community/#slack). +Tell us what you expect the extension to do, or a feature that you wish would be implemented. At this early stage of development, it might help us improve our goals. You can join the discussion on `#gsoc-browser-ext` channel on [slack](/community/#slack). I would like to thank [Alden](https://creativecommons.org/author/aldencreativecommons-org/), [Timid](https://creativecommons.org/author/timidcreativecommons-org/) and [Kriti](https://creativecommons.org/author/kriticreativecommons-org/) to for their mentorship and providing an experienced perspective and solutions to the problems faced by this naive developer. diff --git a/content/blog/entries/cc-browser-extension-upcoming-improvements/contents.lr b/content/blog/entries/cc-browser-extension-upcoming-improvements/contents.lr index 7be011fb2..4b13a1fd0 100644 --- a/content/blog/entries/cc-browser-extension-upcoming-improvements/contents.lr +++ b/content/blog/entries/cc-browser-extension-upcoming-improvements/contents.lr @@ -15,7 +15,7 @@ pub_date: 2020-06-01 --- body: -[CC Search Extension](https://opensource.creativecommons.org/ccsearch-browser-extension/) is a cross-browser extension, which lets you search for and filter content that is under Creative Commons licenses. It was developed as one of the CC projects during Google Summer of Code program of 2019. +[CC Search Extension](/ccsearch-browser-extension/) is a cross-browser extension, which lets you search for and filter content that is under Creative Commons licenses. It was developed as one of the CC projects during Google Summer of Code program of 2019. ### The story so far It's release on the extension stores of [Chrome](https://chrome.google.com/webstore/detail/cc-search-browser-extensi/agohkbfananbebiaphblgcfhcclklfnh), [Firefox](https://addons.mozilla.org/en-US/firefox/addon/cc-search-extension/), and [Opera](https://addons.opera.com/en/extensions/details/cc-search/) was accompanied by several announcements on twitter, which were well received by the community and thus the number of weekly users (i.e the number of users that have used the extension at least once during last week) drastically increased. After several weeks, the extension reached 22,000+ weekly users. But, now this number fluctuates between 9,000 - 10,000. So, what happened? Well, the majority of initial influx were the "curious" folks who just wanted to check out this new tool and later thought that this was not something that they might find useful. But, there are also users that are looking for a similar tool and the lack of sufficient features and capabilities of the extension made them stop using it and look for better alternatives. @@ -47,7 +47,7 @@ The extension uses a very outdated version of CC Vocabulary. It will be replaced The new Microsoft Edge browser is based on chromium. This paves the way to add support for it thanks to the power and flexibility of the WebExtension API. This will then allow us to also officially release on the [Microsoft Edge Addon Store](https://microsoftedge.microsoft.com/addons/Microsoft-Edge-Extensions-Home). ### Join the discussion -If you have any feedback/suggestions or just want to say hi, please join the `#cc-dev-browser-extension` channel on [slack](https://opensource.creativecommons.org/community/#slack). You can also track the progress on the project's [Github](https://github.com/creativecommons/ccsearch-browser-extension) Repository. +If you have any feedback/suggestions or just want to say hi, please join the `#cc-dev-browser-extension` channel on [slack](/community/#slack). You can also track the progress on the project's [Github](https://github.com/creativecommons/ccsearch-browser-extension) Repository. diff --git a/content/blog/entries/cc-browser-extension-week5-6/contents.lr b/content/blog/entries/cc-browser-extension-week5-6/contents.lr index 858599820..19b74ffb0 100644 --- a/content/blog/entries/cc-browser-extension-week5-6/contents.lr +++ b/content/blog/entries/cc-browser-extension-week5-6/contents.lr @@ -17,7 +17,7 @@ body: For the context, I am working on my GSoC project that is to make a browser-extension to search CC Licensed content in the public domain by interacting with CC Catalog API. **Previous Blogs**: -- [CC Browser Extension - A GSoC Project](http://creativecommons.github.io/blog/entries/cc-browser-extension-a-gsoc-project/) +- [CC Browser Extension - A GSoC Project](/blog/entries/cc-browser-extension-a-gsoc-project/) ### Work Done These couple weeks were spent on finishing the filter section, setting up infinite-scroll and fixing issues and bugs after some days of testing. @@ -33,7 +33,7 @@ I tested the extension for a couple of days and made some [bug reports](https:// - Let users copy the rich-text or HTML version of the attribution with one click. - Add the download buttons to download the image and the attribution. -You can check out the project on [Github](https://github.com/creativecommons/ccsearch-browser-extension) and join the discussion on `#gsoc-browser-ext` channel on [slack](http://creativecommons.github.io/community/#slack). +You can check out the project on [Github](https://github.com/creativecommons/ccsearch-browser-extension) and join the discussion on `#gsoc-browser-ext` channel on [slack](/community/#slack). *Special Thanks*: [Alden](https://creativecommons.org/author/aldencreativecommons-org/), [Timid](https://creativecommons.org/author/timidcreativecommons-org/) and [Kriti](https://creativecommons.org/author/kriticreativecommons-org/) diff --git a/content/blog/entries/cc-browser-extension-week7-8/contents.lr b/content/blog/entries/cc-browser-extension-week7-8/contents.lr index 29fcd4e1d..70ed0040d 100644 --- a/content/blog/entries/cc-browser-extension-week7-8/contents.lr +++ b/content/blog/entries/cc-browser-extension-week7-8/contents.lr @@ -17,8 +17,8 @@ body: For the context, I am working on my GSoC project that is to make a browser-extension to search CC Licensed content in the public domain by interacting with CC Catalog API. **Previous Blogs**: -- [CC Browser Extension - A GSoC Project](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-a-gsoc-project/) -- [CC Browser Extension Week 5, 6](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-week5-6/) +- [CC Browser Extension - A GSoC Project](/blog/entries/cc-browser-extension-a-gsoc-project/) +- [CC Browser Extension Week 5, 6](/blog/entries/cc-browser-extension-week5-6/) ### Work Done A couple of major features were added to the browser extension these weeks like image Info and attribution preview and options UI. Also, the extension now has dark mode :) @@ -59,6 +59,6 @@ I also added an options page to the extension which will open in a new tab and t - Test and fix bugs. - Improve documentation. -You can check out the project on [Github](https://github.com/creativecommons/ccsearch-browser-extension) and join the discussion on `#gsoc-browser-ext` channel on [slack](https://opensource.creativecommons.org/community/#slack). +You can check out the project on [Github](https://github.com/creativecommons/ccsearch-browser-extension) and join the discussion on `#gsoc-browser-ext` channel on [slack](/community/#slack). *Special Thanks*: [Alden](https://creativecommons.org/author/aldencreativecommons-org/), [Timid](https://creativecommons.org/author/timidcreativecommons-org/) and [Kriti](https://creativecommons.org/author/kriticreativecommons-org/) \ No newline at end of file diff --git a/content/blog/entries/cc-browser-extension-week9-10/contents.lr b/content/blog/entries/cc-browser-extension-week9-10/contents.lr index 8bb77003f..363f71207 100644 --- a/content/blog/entries/cc-browser-extension-week9-10/contents.lr +++ b/content/blog/entries/cc-browser-extension-week9-10/contents.lr @@ -18,14 +18,14 @@ body: For the context, I am working on my GSoC project that is to make a browser-extension to search CC Licensed content in the public domain by interacting with CC Catalog API. **Previous Blogs**: -- [CC Browser Extension - A GSoC Project](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-a-gsoc-project/) -- [CC Browser Extension Week 5, 6](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-week5-6/) -- [CC Browser Extension Week 7, 8](https://opensource.creativecommons.org/blog/entries/cc-browser-extension-week7-8/) +- [CC Browser Extension - A GSoC Project](/blog/entries/cc-browser-extension-a-gsoc-project/) +- [CC Browser Extension Week 5, 6](/blog/entries/cc-browser-extension-week5-6/) +- [CC Browser Extension Week 7, 8](/blog/entries/cc-browser-extension-week7-8/) ### Work Done These weeks were spent on adding bookmarking feature to the extension and writing some unit tests. -On clicking the bookmark icon, that appears when the image thumbnail is hovered on, the image will be bookmarked. Under the hood, the unique image identifier is saved in the local storage of the extension. The images ids are enough to get all the required image and attribution data needed using the `/image/{identifier}` endpoint of [CC Catalog API]([https://github.com/creativecommons/cccatalog-api](https://github.com/creativecommons/cccatalog-api). +On clicking the bookmark icon, that appears when the image thumbnail is hovered on, the image will be bookmarked. Under the hood, the unique image identifier is saved in the local storage of the extension. The images ids are enough to get all the required image and attribution data needed using the `/image/{identifier}` endpoint of [CC Catalog API]([https://github.com/cc-archive/cccatalog-api](https://github.com/cc-archive/cccatalog-api). Bookmarked images persist even when the extension session terminates. User can view, inspect, delete the bookmarked images in the _'Bookmarks'_ section. There is also a button to delete all the bookmarks at once. @@ -37,6 +37,6 @@ The rest of the time was spent on writing tests for the extension. One positive - Test and fix bugs. - Modifying webpack config to spit out code for production. -You can check out the project on [Github](https://github.com/creativecommons/ccsearch-browser-extension) and join the discussion on `#gsoc-browser-ext` channel on [slack](https://opensource.creativecommons.org/community/#slack). +You can check out the project on [Github](https://github.com/creativecommons/ccsearch-browser-extension) and join the discussion on `#gsoc-browser-ext` channel on [slack](/community/#slack). *Special Thanks*: [Alden](https://creativecommons.org/author/aldencreativecommons-org/), [Timid](https://creativecommons.org/author/timidcreativecommons-org/) and [Kriti](https://creativecommons.org/author/kriticreativecommons-org/). diff --git a/content/blog/entries/cc-catalog-leverage-open-data-1/contents.lr b/content/blog/entries/cc-catalog-leverage-open-data-1/contents.lr index 65085fc93..631a7faaa 100644 --- a/content/blog/entries/cc-catalog-leverage-open-data-1/contents.lr +++ b/content/blog/entries/cc-catalog-leverage-open-data-1/contents.lr @@ -34,7 +34,7 @@ The goal for 2019 is to increase the catalog to: The next post will discuss the details of the Common Crawl data pipeline and how instrumental this corpus is for identifying potential providers and understanding how people are using the various CC license. -[cccatalog]:https://github.com/creativecommons/cccatalog +[cccatalog]:https://github.com/cc-archive/cccatalog [cc-search-developer-notes]:https://hackernoon.com/cc-search-developer-notes-and-reflection-418271194682 [cc-search-beta]:https://creativecommons.org/2017/02/07/new-cc-search/ [cc-search-beta-updates]:https://creativecommons.org/2018/09/24/big-changes-for-cc-search-beta-updates-released-today/ @@ -42,9 +42,9 @@ The next post will discuss the details of the Common Crawl data pipeline and how [data-pipeline]:https://en.wikipedia.org/wiki/Pipeline_(computing) [apache-spark]:https://spark.apache.org/ [apache-airflow]:https://airflow.apache.org/ -[cc-search-stable]:https://creativecommons.github.io/blog/entries/cc-search-out-of-beta/ +[cc-search-stable]:/blog/entries/cc-search-out-of-beta/ [cc-search]:https://search.creativecommons.org/ -[cc-catalog-api]:https://github.com/creativecommons/cccatalog-api +[cc-catalog-api]:https://github.com/cc-archive/cccatalog-api [etl-pipeline]:https://en.wikipedia.org/wiki/Extract,_transform,_load [cc-flickr]:https://blog.flickr.net/en/2019/03/08/update-on-creative-commons-licenses-and-in-memoriam-accounts/ [open-api]:https://en.wikipedia.org/wiki/Open_API diff --git a/content/blog/entries/cc-catalog-wrapping-gsoc20/contents.lr b/content/blog/entries/cc-catalog-wrapping-gsoc20/contents.lr index 81314bba3..33e4ad1b1 100644 --- a/content/blog/entries/cc-catalog-wrapping-gsoc20/contents.lr +++ b/content/blog/entries/cc-catalog-wrapping-gsoc20/contents.lr @@ -47,18 +47,18 @@ Provider API implemented : Iconfinder is a provider of icons that could not be integrated as the current strategy of ingestion is very slow and we need a better strategy. - Issue : [Iconfinder ticket][iconfinder_issue] -[science_museum_issue]: https://github.com/creativecommons/cccatalog/issues/302 -[science_museum_script]: https://github.com/creativecommons/cccatalog/pull/400 -[science_museum_workflow]: https://github.com/creativecommons/cccatalog/pull/411 -[statens_museum_issue]: https://github.com/creativecommons/cccatalog/issues/393 -[statens_museum_implementation]: https://github.com/creativecommons/cccatalog/pull/428 -[museums_victoria_issue]: https://github.com/creativecommons/cccatalog/issues/291 -[museums_victoria_implementation]: https://github.com/creativecommons/cccatalog/pull/447 -[nypl_issue]: https://github.com/creativecommons/cccatalog/issues/147 -[nypl_implementation]: https://github.com/creativecommons/cccatalog/pull/462 -[brooklyn_museum_issue]: https://github.com/creativecommons/cccatalog/issues/348 -[brooklyn_museum_implementation]: https://github.com/creativecommons/cccatalog/pull/355 -[iconfinder_issue]:https://github.com/creativecommons/cccatalog/issues/396 +[science_museum_issue]: https://github.com/cc-archive/cccatalog/issues/302 +[science_museum_script]: https://github.com/cc-archive/cccatalog/pull/400 +[science_museum_workflow]: https://github.com/cc-archive/cccatalog/pull/411 +[statens_museum_issue]: https://github.com/cc-archive/cccatalog/issues/393 +[statens_museum_implementation]: https://github.com/cc-archive/cccatalog/pull/428 +[museums_victoria_issue]: https://github.com/cc-archive/cccatalog/issues/291 +[museums_victoria_implementation]: https://github.com/cc-archive/cccatalog/pull/447 +[nypl_issue]: https://github.com/cc-archive/cccatalog/issues/147 +[nypl_implementation]: https://github.com/cc-archive/cccatalog/pull/462 +[brooklyn_museum_issue]: https://github.com/cc-archive/cccatalog/issues/348 +[brooklyn_museum_implementation]: https://github.com/cc-archive/cccatalog/pull/355 +[iconfinder_issue]:https://github.com/cc-archive/cccatalog/issues/396 ## Europeana reingestion strategy @@ -76,9 +76,9 @@ More details regarding the math of reingestion: [Data reingestion][data_reingest

Europeana reingestion workflow

-[europeana_reingestion_issue]: https://github.com/creativecommons/cccatalog/issues/412 -[europeana_reingestion_strategy]: https://github.com/creativecommons/cccatalog/pull/473 -[data_reingestion_blog]: https://opensource.creativecommons.org/blog/entries/date-partitioned-data-reingestion/ +[europeana_reingestion_issue]: https://github.com/cc-archive/cccatalog/issues/412 +[europeana_reingestion_strategy]: https://github.com/cc-archive/cccatalog/pull/473 +[data_reingestion_blog]: /blog/entries/date-partitioned-data-reingestion/ ## Merging Common Crawl tags @@ -88,8 +88,8 @@ Currently the merging logic is applied to Science Museum, Museums Victoria and M In Science Museum, API url in image table is like https://coimages.sciencemuseumgroup.org.uk/images/240/862/large_BAB_S_1_02_0017.jpg and CC url is like https://s3-eu-west-1.amazonaws.com/smgco-images/images/369/541/medium_SMG00096855.jpg . So the idea is to reduce the url to the last identifier like number , so after the modification of the url by modify_urls function it looks like ```gpj.1700_20_1_S_BAB_``` (API url) and ```gpj.55869000GMS_``` (CC url) . Similar logic has been applied to met museum and museum victoria. -- Issue: https://github.com/creativecommons/cccatalog/issues/468 -- Related PR: https://github.com/creativecommons/cccatalog/pull/478 +- Issue: https://github.com/cc-archive/cccatalog/issues/468 +- Related PR: https://github.com/cc-archive/cccatalog/pull/478 ## Acknowledgement diff --git a/content/blog/entries/cc-datacatalog-data-processing-2/contents.lr b/content/blog/entries/cc-datacatalog-data-processing-2/contents.lr index f927e232f..b4d70f05a 100644 --- a/content/blog/entries/cc-datacatalog-data-processing-2/contents.lr +++ b/content/blog/entries/cc-datacatalog-data-processing-2/contents.lr @@ -21,7 +21,7 @@ Search (now [Openverse](https://openverse.org/)). Please also see the [Quantifying the Commons](https://github.com/creativecommons/quantifying) project. -This is a continuation of my last blog post about the data processing part of the CC-data catalog visualization project. I recommend you to read that [last post](https://opensource.creativecommons.org/blog/entries/cc-datacatalog-data-processing/) for a better understanding of what I'll explain here. +This is a continuation of my last blog post about the data processing part of the CC-data catalog visualization project. I recommend you to read that [last post](/blog/entries/cc-datacatalog-data-processing/) for a better understanding of what I'll explain here. ### The data diff --git a/content/blog/entries/cc-datacatalog-data-processing-3/contents.lr b/content/blog/entries/cc-datacatalog-data-processing-3/contents.lr index 979572c4d..e8b471990 100644 --- a/content/blog/entries/cc-datacatalog-data-processing-3/contents.lr +++ b/content/blog/entries/cc-datacatalog-data-processing-3/contents.lr @@ -21,13 +21,13 @@ Search (now [Openverse](https://openverse.org/)). Please also see the [Quantifying the Commons](https://github.com/creativecommons/quantifying) project. -This is a continuation of my last blog post about the data processing part 2 of the CC-data catalog visualization project. I recommend you to read that [last post](https://opensource.creativecommons.org/blog/entries/cc-datacatalog-data-processing-2/) for a better understanding of what I'll explain here. +This is a continuation of my last blog post about the data processing part 2 of the CC-data catalog visualization project. I recommend you to read that [last post](/blog/entries/cc-datacatalog-data-processing-2/) for a better understanding of what I'll explain here. Hello! In this post I am going to talk you about the extraction of unique nodes, and links, and the visualization of the force-directed graph with the processed data. ### Nodes and links generation -The nodes and links will be visualized using [force-graph](https://github.com/vasturiano/force-graph). I spoke about this library in my blog post: [Visualize CC Catalog data](https://opensource.creativecommons.org/blog/entries/cc-datacatalog-visualization/). My first step is to use the data to generate the json file that it needs. Force-graph needs to be passed a single json file with two lists: one containing information about the nodes, and the other containing the links. They are both arrays of dictionaries. I have huge input files (and over 100 million unique domains in total). So in Pandas I need to build a DataFrame of a tsv input file using chunks. The challenge I am facing now is to generate a list of unique nodes. Here is why this is a challenge: +The nodes and links will be visualized using [force-graph](https://github.com/vasturiano/force-graph). I spoke about this library in my blog post: [Visualize CC Catalog data](/blog/entries/cc-datacatalog-visualization/). My first step is to use the data to generate the json file that it needs. Force-graph needs to be passed a single json file with two lists: one containing information about the nodes, and the other containing the links. They are both arrays of dictionaries. I have huge input files (and over 100 million unique domains in total). So in Pandas I need to build a DataFrame of a tsv input file using chunks. The challenge I am facing now is to generate a list of unique nodes. Here is why this is a challenge: - In order to build the nodes list, I need to think aboutwhat are the source and target nodes. - Take into account a source node can also be a target node. diff --git a/content/blog/entries/cc-datacatalog-data-processing/contents.lr b/content/blog/entries/cc-datacatalog-data-processing/contents.lr index 967524b2f..025006a06 100644 --- a/content/blog/entries/cc-datacatalog-data-processing/contents.lr +++ b/content/blog/entries/cc-datacatalog-data-processing/contents.lr @@ -56,10 +56,10 @@ In the dataset, we have domain names in the form of URLs. But we want to make th >>> (ext.subdomain, ext.domain, ext.suffix) ('forums', 'bbc', 'co.uk') #extract the domain name "bbc" ``` -The main part is the extraction of the domain name. This will be applied to the _provider\_domain_ and _links_ fields in order to build the graph. The domain names will be the ones displayed over the nodes, as depicted in [my first blog post](https://creativecommons.github.io/blog/entries/cc-datacatalog-visualization/). +The main part is the extraction of the domain name. This will be applied to the _provider\_domain_ and _links_ fields in order to build the graph. The domain names will be the ones displayed over the nodes, as depicted in [my first blog post](/blog/entries/cc-datacatalog-visualization/). ### License Validation -Another important aspect is the licenses types. In the dataset, we do not have the exact license name; rather, we have a URL that directs to the license definition on [creativecommons.org](https://creativecommons.org). We have developed a [function](https://github.com/creativecommons/cccatalog/blob/master/src/providers/api/modules/etlMods.py#L75) with some regular expressions to validate the correct format of these URls, and extracts from them the license name and version. This information will be shown in the pie chart that appears after the user clicks on a node. +Another important aspect is the licenses types. In the dataset, we do not have the exact license name; rather, we have a URL that directs to the license definition on [creativecommons.org](https://creativecommons.org). We have developed a [function](https://github.com/cc-archive/cccatalog/blob/master/src/providers/api/modules/etlMods.py#L75) with some regular expressions to validate the correct format of these URls, and extracts from them the license name and version. This information will be shown in the pie chart that appears after the user clicks on a node. ``` 'https://creativecommons.org/licenses/by/4.0/' #valid license diff --git a/content/blog/entries/cc-datacatalog-data-thelinkedcommons/contents.lr b/content/blog/entries/cc-datacatalog-data-thelinkedcommons/contents.lr index 3f70465a2..616a30a95 100644 --- a/content/blog/entries/cc-datacatalog-data-thelinkedcommons/contents.lr +++ b/content/blog/entries/cc-datacatalog-data-thelinkedcommons/contents.lr @@ -21,7 +21,7 @@ Search (now [Openverse](https://openverse.org/)). Please also see the [Quantifying the Commons](https://github.com/creativecommons/quantifying) project. -This is a continuation of my last blog post about the data processing part 3 of the CC-data catalog visualization project. I recommend you to read that [last post](https://opensource.creativecommons.org/blog/entries/cc-datacatalog-data-processing-3/) for a better understanding of what I'll explain here. +This is a continuation of my last blog post about the data processing part 3 of the CC-data catalog visualization project. I recommend you to read that [last post](/blog/entries/cc-datacatalog-data-processing-3/) for a better understanding of what I'll explain here. Hello! In this last post, I am going to talk you about the final visualization. First, I would like to talk about the data and share my recommendations. @@ -57,7 +57,7 @@ The final graph is interactive. Users can pan, zoom in and out, hover over a nod ### Pie chart visualization -The pie charts are built using the [Highcarts library](https://www.highcharts.com/). The purpose of this chart is to show to the public how each domain uses CC licenses. I spoke about this in my blog post: [Visualize CC Catalog data](https://opensource.creativecommons.org/blog/entries/cc-datacatalog-visualization/). Here is an image to illustrate the above: +The pie charts are built using the [Highcarts library](https://www.highcharts.com/). The purpose of this chart is to show to the public how each domain uses CC licenses. I spoke about this in my blog post: [Visualize CC Catalog data](/blog/entries/cc-datacatalog-visualization/). Here is an image to illustrate the above:
cc_licenses dictionary
diff --git a/content/blog/entries/cc-gsoc-accepted-students/contents.lr b/content/blog/entries/cc-gsoc-accepted-students/contents.lr index 7a1b4790c..94bd1b105 100644 --- a/content/blog/entries/cc-gsoc-accepted-students/contents.lr +++ b/content/blog/entries/cc-gsoc-accepted-students/contents.lr @@ -31,10 +31,10 @@ If you’re interested in working on one of our remaining [project ideas][projec *A note about availability*: all CC staff have very limited availability over the next week because of[ CC Global Summit][cc-summit] and CC is closed for most of the following week so we won’t be around at all then. Please be patient, we’ll respond to you as soon as we can. -[project-ideas]:https://creativecommons.github.io/gsoc-2019/project-ideas/ +[project-ideas]:/gsoc-2019/project-ideas/ [cc-gsoc-projects]:https://summerofcode.withgoogle.com/organizations/6514859793973248/#projects -[contributing-code]:https://creativecommons.github.io/contributing-code/ -[supercharging-elasticsearch]:https://creativecommons.github.io/gsoc-2019/project-ideas/all/#supercharge-our-indexing-engine -[automated-license-link-checking]:https://creativecommons.github.io/gsoc-2019/project-ideas/all/#automated-link-checking -[cc-search-plugins]:https://creativecommons.github.io/gsoc-2019/project-ideas/all/#cc-plugin-generic +[contributing-code]:/contributing-code/ +[supercharging-elasticsearch]:/gsoc-2019/project-ideas/all/#supercharge-our-indexing-engine +[automated-license-link-checking]:/gsoc-2019/project-ideas/all/#automated-link-checking +[cc-search-plugins]:/gsoc-2019/project-ideas/all/#cc-plugin-generic [cc-summit]:https://summit.creativecommons.org/ diff --git a/content/blog/entries/cc-link-checker/contents.lr b/content/blog/entries/cc-link-checker/contents.lr index a0db1abb0..476a2b572 100644 --- a/content/blog/entries/cc-link-checker/contents.lr +++ b/content/blog/entries/cc-link-checker/contents.lr @@ -63,7 +63,7 @@ I started working on the project a month back i.e. 13 Jun. During this journey t CC Link Checker is only possible due to the support and guidance of my mentors [Alden Page](https://creativecommons.org/author/aldenpage) and [Timid Robot Zehta](https://creativecommons.org/author/TimidRobot), who have been very supportive on every step of the project. Also I would like to thank engineering director [Kriti Godey](https://creativecommons.org/author/kgodey) for her continuous support. -You can follow the project on Github: [creativecommons/cc-link-checker](https://github.com/creativecommons/cc-link-checker). You can also join the discussion on `#cc-link-checker` on [Slack](https://opensource.creativecommons.org/community/#slack) +You can follow the project on Github: [creativecommons/cc-link-checker](https://github.com/creativecommons/cc-link-checker). You can also join the discussion on `#cc-link-checker` on [Slack](/community/#slack) The project is approaching its completion. Can't wait to see it in production. diff --git a/content/blog/entries/cc-plus-gsoc-2019/contents.lr b/content/blog/entries/cc-plus-gsoc-2019/contents.lr index 6414edb37..eb8b6a35f 100644 --- a/content/blog/entries/cc-plus-gsoc-2019/contents.lr +++ b/content/blog/entries/cc-plus-gsoc-2019/contents.lr @@ -36,8 +36,8 @@ If you want to stay updated on our work, join our [brand new developer mailing l [gsoc-homepage]: https://summerofcode.withgoogle.com/ [cc-gsoc-page]: https://summerofcode.withgoogle.com/organizations/6514859793973248/ -[project-ideas]: https://creativecommons.github.io/gsoc-2019/project-ideas/all/ -[cc-open-source]: https://creativecommons.github.io/ +[project-ideas]: /gsoc-2019/project-ideas/all/ +[cc-open-source]: / [cc-search-active-sprint]: https://github.com/orgs/creativecommons/projects/7 [mailing-list]: https://groups.google.com/a/creativecommons.org/forum/#!forum/cc-developers [freenode-homepage]: https://freenode.net/ diff --git a/content/blog/entries/cc-search-accessibility-week1-2/contents.lr b/content/blog/entries/cc-search-accessibility-week1-2/contents.lr index d1c6f599a..e90fe6e0e 100644 --- a/content/blog/entries/cc-search-accessibility-week1-2/contents.lr +++ b/content/blog/entries/cc-search-accessibility-week1-2/contents.lr @@ -19,11 +19,11 @@ These are the first two weeks of my internship with CC. I am working on improvin We started with first compiling the accessibility reports from accessibility insights, lighthouse and pa11y into a single document and then opening up appropriate issues ont he repo to address them. The accessibility issues are listed here: -1. [Accessibility - Improve labels](https://github.com/creativecommons/cccatalog-frontend/issues/996) -2. [Evaluate keyboard navigation effectiveness](https://github.com/creativecommons/cccatalog-frontend/issues/997) -3. [Fix color contrast problems](https://github.com/creativecommons/cccatalog-frontend/issues/998) -4. [Improve elements markup](https://github.com/creativecommons/cccatalog-frontend/issues/999) -5. [Evaluate any accessibility linter tools](https://github.com/creativecommons/cccatalog-frontend/issues/1000) +1. [Accessibility - Improve labels](https://github.com/cc-archive/cccatalog-frontend/issues/996) +2. [Evaluate keyboard navigation effectiveness](https://github.com/cc-archive/cccatalog-frontend/issues/997) +3. [Fix color contrast problems](https://github.com/cc-archive/cccatalog-frontend/issues/998) +4. [Improve elements markup](https://github.com/cc-archive/cccatalog-frontend/issues/999) +5. [Evaluate any accessibility linter tools](https://github.com/cc-archive/cccatalog-frontend/issues/1000) The decision was made to audit the tab indices along with internationalizing the page. The accessibility changes will be done after the completion of internationalization as the aria-labels will have to be internationalized as well. @@ -62,10 +62,10 @@ The final outcome looks pretty good: And voila we are done with the first two weeks. I also internationalized the header and the footer along with the homepage. You can track the work done for these weeks through these PRs: -1. [setup internationalization plugin](https://github.com/creativecommons/cccatalog-frontend/pull/1007) -2. [Internationalize homepage, header and footer](https://github.com/creativecommons/cccatalog-frontend/pull/1013) +1. [setup internationalization plugin](https://github.com/cc-archive/cccatalog-frontend/pull/1007) +2. [Internationalize homepage, header and footer](https://github.com/cc-archive/cccatalog-frontend/pull/1013) -The progress of the project can be tracked on [cc-search](https://github.com/creativecommons/cccatalog-frontend) +The progress of the project can be tracked on [cc-search](https://github.com/cc-archive/cccatalog-frontend) -CC Search Accessiblity is my GSoC 2020 project under the guidance of [Ari Madian](https://opensource.creativecommons.org/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti +CC Search Accessiblity is my GSoC 2020 project under the guidance of [Ari Madian](/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti Godey](https://creativecommons.org/author/kriticreativecommons-org/), have been very supportive. diff --git a/content/blog/entries/cc-search-accessibility-week3-4/contents.lr b/content/blog/entries/cc-search-accessibility-week3-4/contents.lr index c2a80d31a..866881189 100644 --- a/content/blog/entries/cc-search-accessibility-week3-4/contents.lr +++ b/content/blog/entries/cc-search-accessibility-week3-4/contents.lr @@ -89,10 +89,10 @@ And we are done with these two weeks, we be back with another post after two wee You can track the work done for these weeks through these PRs: -1. [Internationalize About Page and Search Guide Page](https://github.com/creativecommons/cccatalog-frontend/pull/1024) -2. [Internationalize feedback page, collections page and not found page](https://github.com/creativecommons/cccatalog-frontend/pull/1031) +1. [Internationalize About Page and Search Guide Page](https://github.com/cc-archive/cccatalog-frontend/pull/1024) +2. [Internationalize feedback page, collections page and not found page](https://github.com/cc-archive/cccatalog-frontend/pull/1031) -The progress of the project can be tracked on [cc-search](https://github.com/creativecommons/cccatalog-frontend) +The progress of the project can be tracked on [cc-search](https://github.com/cc-archive/cccatalog-frontend) -CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](https://opensource.creativecommons.org/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti +CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti Godey](https://creativecommons.org/author/kriticreativecommons-org/), have been very supportive. diff --git a/content/blog/entries/cc-search-accessibility-week5-6/contents.lr b/content/blog/entries/cc-search-accessibility-week5-6/contents.lr index ff37c7eff..aacffe05c 100644 --- a/content/blog/entries/cc-search-accessibility-week5-6/contents.lr +++ b/content/blog/entries/cc-search-accessibility-week5-6/contents.lr @@ -19,8 +19,8 @@ These are the fifth and sixth weeks of my internship with CC. I am working on im This post contains yet another important aspect to be taken care of while internationalizing the Vue components, i.e. modifying tests to include the changes. The components which were left are the two pages displaying the most content: -1. [Browse page](https://github.com/creativecommons/cccatalog-frontend/blob/develop/src/pages/BrowsePage.vue) -2. [ImageDetail page](https://github.com/creativecommons/cccatalog-frontend/blob/develop/src/pages/PhotoDetailPage.vue) +1. [Browse page](https://github.com/cc-archive/cccatalog-frontend/blob/develop/src/pages/BrowsePage.vue) +2. [ImageDetail page](https://github.com/cc-archive/cccatalog-frontend/blob/develop/src/pages/PhotoDetailPage.vue) The above two pages too were handled similar to the remaining pages, special care had to be taken in case of ImageDetail page since there are too many components in different files. By this point we also have our json structure figured out, mostly and are ready to push the json for fetching further translations. @@ -65,16 +65,16 @@ And *drum rolls* we have successfully completed Internationalization of the comp The issues closed with the completion of Internationalization are: -1. [[META] Internationalisation (i18n) Setup](https://github.com/creativecommons/cccatalog-frontend/issues/487) -2. [Set up vue-i18n infrastructure](https://github.com/creativecommons/cccatalog-frontend/issues/941) -3. [Create locale messages format JSON structure](https://github.com/creativecommons/cccatalog-frontend/issues/942) -4. [Allow users to change locale on the client](https://github.com/creativecommons/cccatalog-frontend/issues/943) +1. [[META] Internationalisation (i18n) Setup](https://github.com/cc-archive/cccatalog-frontend/issues/487) +2. [Set up vue-i18n infrastructure](https://github.com/cc-archive/cccatalog-frontend/issues/941) +3. [Create locale messages format JSON structure](https://github.com/cc-archive/cccatalog-frontend/issues/942) +4. [Allow users to change locale on the client](https://github.com/cc-archive/cccatalog-frontend/issues/943) You can track the work done for these weeks through this PR: -1. [Localize browsepage and single-result page](https://github.com/creativecommons/cccatalog-frontend/pull/1040) +1. [Localize browsepage and single-result page](https://github.com/cc-archive/cccatalog-frontend/pull/1040) -The progress of the project can be tracked on [cc-search](https://github.com/creativecommons/cccatalog-frontend) +The progress of the project can be tracked on [cc-search](https://github.com/cc-archive/cccatalog-frontend) -CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](https://opensource.creativecommons.org/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti +CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti Godey](https://creativecommons.org/author/kriticreativecommons-org/), have been very supportive. diff --git a/content/blog/entries/cc-search-accessibility-week7-8/contents.lr b/content/blog/entries/cc-search-accessibility-week7-8/contents.lr index 81ee7fb3f..48de88bbb 100644 --- a/content/blog/entries/cc-search-accessibility-week7-8/contents.lr +++ b/content/blog/entries/cc-search-accessibility-week7-8/contents.lr @@ -121,10 +121,10 @@ Whoosh!! That was quite a lot. We are done with these two weeks for now. Hope to You can track the work done for these weeks through these PRs: -1. [Accessibility](https://github.com/creativecommons/cccatalog-frontend/pull/1068) -2. [Accessibility Improvements](https://github.com/creativecommons/cccatalog-frontend/pull/1072) +1. [Accessibility](https://github.com/cc-archive/cccatalog-frontend/pull/1068) +2. [Accessibility Improvements](https://github.com/cc-archive/cccatalog-frontend/pull/1072) -The progress of the project can be tracked on [cc-search](https://github.com/creativecommons/cccatalog-frontend) +The progress of the project can be tracked on [cc-search](https://github.com/cc-archive/cccatalog-frontend) -CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](https://opensource.creativecommons.org/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti +CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti Godey](https://creativecommons.org/author/kriticreativecommons-org/), have been very supportive. diff --git a/content/blog/entries/cc-search-accessibility-week9-10/contents.lr b/content/blog/entries/cc-search-accessibility-week9-10/contents.lr index d6360c302..b899d4763 100644 --- a/content/blog/entries/cc-search-accessibility-week9-10/contents.lr +++ b/content/blog/entries/cc-search-accessibility-week9-10/contents.lr @@ -51,7 +51,7 @@ The criteria are: 2. The modal should have trap-focus(the user should not exit the modal when using tab to navigate). 3. The modal should close on pressing **esc** or on clicking the overlay. -To meet the criteria we developed a new [modal component](https://github.com/creativecommons/cccatalog-frontend/blob/develop/src/components/AppModal.vue). +To meet the criteria we developed a new [modal component](https://github.com/cc-archive/cccatalog-frontend/blob/develop/src/components/AppModal.vue). This modal has an overlay and closes when we press the **esc** key or click on the overlay. The modal also disables other elements when it is opened. The final task achieved in the modal was the implementation of trap focus. For this we used the [vue-trap-focus library](https://github.com/posva/focus-trap-vue) @@ -119,13 +119,13 @@ And we are officially done with our work for the summer internship. The next blo You can track the work done for these weeks through these PRs: -1. [Accessibility Improvements](https://github.com/creativecommons/cccatalog-frontend/pull/1072) -2. [setup vue-a11y for eslint](https://github.com/creativecommons/cccatalog-frontend/pull/1121) -3. [Aria labels and internationalization](https://github.com/creativecommons/cccatalog-frontend/pull/1123) -4. [internationalize aria-labels for about page and feedback page](https://github.com/creativecommons/cccatalog-frontend/pull/1120) -5. [add trap focus to modals](https://github.com/creativecommons/cccatalog-frontend/pull/1153) +1. [Accessibility Improvements](https://github.com/cc-archive/cccatalog-frontend/pull/1072) +2. [setup vue-a11y for eslint](https://github.com/cc-archive/cccatalog-frontend/pull/1121) +3. [Aria labels and internationalization](https://github.com/cc-archive/cccatalog-frontend/pull/1123) +4. [internationalize aria-labels for about page and feedback page](https://github.com/cc-archive/cccatalog-frontend/pull/1120) +5. [add trap focus to modals](https://github.com/cc-archive/cccatalog-frontend/pull/1153) -The progress of the project can be tracked on [cc-search](https://github.com/creativecommons/cccatalog-frontend) +The progress of the project can be tracked on [cc-search](https://github.com/cc-archive/cccatalog-frontend) -CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](https://opensource.creativecommons.org/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti +CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti Godey](https://creativecommons.org/author/kriticreativecommons-org/), have been very supportive. diff --git a/content/blog/entries/cc-search-accessibility-wrapup/contents.lr b/content/blog/entries/cc-search-accessibility-wrapup/contents.lr index de10e6efc..fbce8ae11 100644 --- a/content/blog/entries/cc-search-accessibility-wrapup/contents.lr +++ b/content/blog/entries/cc-search-accessibility-wrapup/contents.lr @@ -21,14 +21,14 @@ The experience was just amazing and the poeple are so helpful I really enjoyed w You can glance through my work through these blog posts: -1. [CC Search, Proposal Drafting and Community Bonding](http://opensource.creativecommons.org/blog/entries/cc-search-accessibility-and-internationalization/) -2. [CC Search, Setting up vue-i18n and internationalizing homepage](http://opensource.creativecommons.org/blog/entries/cc-search-accessibility-week1-2/) -3. [Internationalization Continued: Handling strings in the store](http://opensource.creativecommons.org/blog/entries/cc-search-accessibility-week3-4/) -4. [Internationalization continued: Modifying tests](http://opensource.creativecommons.org/blog/entries/cc-search-accessibility-week5-6/) -5. [CC Search, Initial Accessibility Improvements](http://opensource.creativecommons.org/blog/entries/cc-search-accessibility-week7-8/) -6. [Accessibility Improvements: Final Changes and Modal Accessilibity](http://opensource.creativecommons.org/blog/entries/cc-search-accessibility-week9-10/) +1. [CC Search, Proposal Drafting and Community Bonding](/blog/entries/cc-search-accessibility-and-internationalization/) +2. [CC Search, Setting up vue-i18n and internationalizing homepage](/blog/entries/cc-search-accessibility-week1-2/) +3. [Internationalization Continued: Handling strings in the store](/blog/entries/cc-search-accessibility-week3-4/) +4. [Internationalization continued: Modifying tests](/blog/entries/cc-search-accessibility-week5-6/) +5. [CC Search, Initial Accessibility Improvements](/blog/entries/cc-search-accessibility-week7-8/) +6. [Accessibility Improvements: Final Changes and Modal Accessilibity](/blog/entries/cc-search-accessibility-week9-10/) -The progress of the project can be tracked on [cc-search](https://github.com/creativecommons/cccatalog-frontend) +The progress of the project can be tracked on [cc-search](https://github.com/cc-archive/cccatalog-frontend) -CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](https://opensource.creativecommons.org/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti +CC Search Accessiblity is my GSoC 2020 project under the guidance of [Zack Krida](https://creativecommons.org/author/zackcreativecommons-org/) and [Ari Madian](/blog/authors/akmadian/), who is the primary mentor for this project, [Anna Tumadóttir](https://creativecommons.org/author/annacreativecommons-org/) for helping all along and engineering director [Kriti Godey](https://creativecommons.org/author/kriticreativecommons-org/), have been very supportive. diff --git a/content/blog/entries/cc-search-out-of-beta/contents.lr b/content/blog/entries/cc-search-out-of-beta/contents.lr index 680f79914..51645fcc3 100644 --- a/content/blog/entries/cc-search-out-of-beta/contents.lr +++ b/content/blog/entries/cc-search-out-of-beta/contents.lr @@ -54,11 +54,11 @@ CC Search is also made possible by a number of institutional and individual supp [cc-search-feedback]:https://search.creativecommons.org/feedback [cc-usability]:https://creativecommons.slack.com/messages/CCS9CF2JE/details/ [cc-slack]:https://wiki.creativecommons.org/wiki/Slack#How_to_join_Slack -[cccatalog]:https://github.com/creativecommons/cccatalog -[cccatalog-api]:https://github.com/creativecommons/cccatalog-api -[cccatalog-frontend]:https://github.com/creativecommons/cccatalog-frontend/ -[contributing-code]:https://creativecommons.github.io/contributing-code/ -[cc-github-io]:https://creativecommons.github.io/ +[cccatalog]:https://github.com/cc-archive/cccatalog +[cccatalog-api]:https://github.com/cc-archive/cccatalog-api +[cccatalog-frontend]:https://github.com/cc-archive/cccatalog-frontend/ +[contributing-code]:/contributing-code/ +[cc-github-io]:/ [arcadia]:https://www.arcadiafund.org.uk/about-peter-baldwin-lisbet-rausing/ [mozilla]:https://www.mozilla.org/en-US/foundation/ [original-blog-post]: https://creativecommons.org/2019/04/30/cc-search-images/ diff --git a/content/blog/entries/cc-search-redesign/contents.lr b/content/blog/entries/cc-search-redesign/contents.lr index bac1a9f2e..0b26bf53d 100644 --- a/content/blog/entries/cc-search-redesign/contents.lr +++ b/content/blog/entries/cc-search-redesign/contents.lr @@ -78,4 +78,4 @@ As part of our Google Summer of Code initiative, we have a project called [CC Vo If you have any feedback, please feel free to send your thoughts and opinions [here](https://ccsearch.creativecommons.org/feedback). -If you feel like contributing to the CC Search frontend code, please refer to our [Contribution guide](https://opensource.creativecommons.org/contributing-code/) and to the [CC Search frontend codebase](https://github.com/creativecommons/cccatalog-frontend). +If you feel like contributing to the CC Search frontend code, please refer to our [Contribution guide](/contributing-code/) and to the [CC Search frontend codebase](https://github.com/cc-archive/cccatalog-frontend). diff --git a/content/blog/entries/cc-vocabulary-docs-updates-2/contents.lr b/content/blog/entries/cc-vocabulary-docs-updates-2/contents.lr index 53159bdfb..a2a930786 100644 --- a/content/blog/entries/cc-vocabulary-docs-updates-2/contents.lr +++ b/content/blog/entries/cc-vocabulary-docs-updates-2/contents.lr @@ -59,7 +59,7 @@ Some say it's hard to learn through virtual internships. Well, let me prove you I believe apart from the internship work that I'm engaged in, I should also help around with some community PR work. I've been told I'm always welcome to, which is great! -- I got the opportunity to speak at a CCOS event alongwith fellow speakers [dhruvkb](https://opensource.creativecommons.org/blog/authors/dhruvkb/) & [dhruvi16](https://opensource.creativecommons.org/blog/authors/dhruvi16/). I had a blast talking to budding students from DSC-IIT Surat & DSC-RIT. +- I got the opportunity to speak at a CCOS event alongwith fellow speakers [dhruvkb](/blog/authors/dhruvkb/) & [dhruvi16](/blog/authors/dhruvi16/). I had a blast talking to budding students from DSC-IIT Surat & DSC-RIT. - The dark mode (as promised) should be out before my next blog post. - Deployed the vocabulary storybook on [Chromatic](https://chromatic.com) and compared & contrasted the pros & cons. Snapshot testing in the near future maybe? - Completed the hacktoberfest challenge. diff --git a/content/blog/entries/cc-vocabulary-docs-updates-3/contents.lr b/content/blog/entries/cc-vocabulary-docs-updates-3/contents.lr index d5c41dd75..60531922b 100644 --- a/content/blog/entries/cc-vocabulary-docs-updates-3/contents.lr +++ b/content/blog/entries/cc-vocabulary-docs-updates-3/contents.lr @@ -29,7 +29,7 @@ Merged? Yes. **Merged**. Here's my story! - After getting a thumbs up from the UX Designer, I put up my [GSoD Website PR](https://github.com/creativecommons/vocabulary/pull/747) for review. - I was confident there would be changes, and I let them roll in. It's important to note here that what seems perfect to you may not be so to others, and only experience teaches you the right from the wrong. - There were a few of them, mainly dealing with spacing, textual content and colors. I resolved them as soon as I could. -- [zackkrida](https://opensource.creativecommons.org/blog/authors/zackkrida/) has been kind enough to point and enumerate all of them for me! +- [zackkrida](/blog/authors/zackkrida/) has been kind enough to point and enumerate all of them for me! - After receiving a final approval from the engineering team, my PR was finally merged! - The final draft of the vocabulary site is live! It will soon be deployed (on [Netlify](https://netlify,com)) and be made available for public viewing. - For my readers, here's [exclusive preview](https://cc-vocab-draft.web.app) of the final draft. diff --git a/content/blog/entries/cc-vocabulary-docs-updates-closing/contents.lr b/content/blog/entries/cc-vocabulary-docs-updates-closing/contents.lr index 4d15244cd..a1fe76aa5 100644 --- a/content/blog/entries/cc-vocabulary-docs-updates-closing/contents.lr +++ b/content/blog/entries/cc-vocabulary-docs-updates-closing/contents.lr @@ -119,7 +119,7 @@ Here's the link to [the landing site](https://cc-vocab-draft.web.app). - Designed the mockups in [Figma](https://figma.com). - Wrote the content filling up the landing page. - After approval from the UX Designer, waited for an approval from the Frontend Engineer. -- Sought continuous approval from my mentor [dhruvkb](https://opensource.creativecommons.org/blog/authors/dhruvkb/). +- Sought continuous approval from my mentor [dhruvkb](/blog/authors/dhruvkb/). - Used [Vue.js](https://vuejs.org) + [CC Vocabulary](https://www.npmjs.com/package/@creativecommons/vocabulary) to build a highly modularised site. - Went through a couple of iterations of the website itself. - Made about **112** commits (**15,000** lines of code) in my *gsod-nimish* branch. @@ -267,28 +267,28 @@ Here's the link to the [documentation site](https://cc-vocabulary.netlify.app). @creativecommons/creativecommons.github.io-source Introductory First Blog Post -https://github.com/creativecommons/creativecommons.github.io-source/pull/530
https://opensource.creativecommons.org/blog/entries/cc-vocabulary-docs-intro/ +https://github.com/creativecommons/creativecommons.github.io-source/pull/530
/blog/entries/cc-vocabulary-docs-intro/ Vocabulary Site Update v1 -https://github.com/creativecommons/creativecommons.github.io-source/pull/549
https://opensource.creativecommons.org/blog/entries/cc-vocabulary-docs-updates-1/ +https://github.com/creativecommons/creativecommons.github.io-source/pull/549
/blog/entries/cc-vocabulary-docs-updates-1/ Vocabulary Mid Internship Update v2 -https://github.com/creativecommons/creativecommons.github.io-source/pull/555
https://opensource.creativecommons.org/blog/entries/cc-vocabulary-docs-updates-2/ +https://github.com/creativecommons/creativecommons.github.io-source/pull/555
/blog/entries/cc-vocabulary-docs-updates-2/ Vocabulary Site Update v3 -https://github.com/creativecommons/creativecommons.github.io-source/pull/561
https://opensource.creativecommons.org/blog/entries/cc-vocabulary-docs-updates-3/ +https://github.com/creativecommons/creativecommons.github.io-source/pull/561
/blog/entries/cc-vocabulary-docs-updates-3/ Vocabulary Site Final Update -https://github.com/creativecommons/creativecommons.github.io-source/pull/564
https://opensource.creativecommons.org/blog/entries/cc-vocabulary-docs-updates-closing/ +https://github.com/creativecommons/creativecommons.github.io-source/pull/564
/blog/entries/cc-vocabulary-docs-updates-closing/ -@creativecommons/cccatalog-api +@cc-archive/cccatalog-api Configured GitHub native dependabot -https://github.com/creativecommons/cccatalog-api/pull/53 +https://github.com/cc-archive/cccatalog-api/pull/53 @creativecommons/ccos-scripts @@ -298,7 +298,7 @@ Here's the link to the [documentation site](https://cc-vocabulary.netlify.app). -Follow along my complete GSoD journey through [these series of posts](https://opensource.creativecommons.org/blog/series/gsod-2020-vocabulary-usage-guide/). +Follow along my complete GSoD journey through [these series of posts](/blog/series/gsod-2020-vocabulary-usage-guide/). ### Memorable Milestones Screenshots diff --git a/content/blog/entries/cc-vocabulary-my-first-four-weeks/contents.lr b/content/blog/entries/cc-vocabulary-my-first-four-weeks/contents.lr index 84026414b..a0d3c72dc 100644 --- a/content/blog/entries/cc-vocabulary-my-first-four-weeks/contents.lr +++ b/content/blog/entries/cc-vocabulary-my-first-four-weeks/contents.lr @@ -17,8 +17,8 @@ body: [Vocabulary](https://cc-vocabulary.netlify.com/) is Creative Commons's web design system; an extension of [CC Style Guide](https://creativecommons.org/wp-content/uploads/2019/10/Creative-Commons-Style-Guide-2019.pdf) -for the web. This project was originally started by my mentors [Dhruv Bhanushali](https://opensource.creativecommons.org/blog/authors/dhruvkb) -and [Hugo Solar](https://opensource.creativecommons.org/blog/authors/hugosolar) to unify all of CC websites and applications. +for the web. This project was originally started by my mentors [Dhruv Bhanushali](/blog/authors/dhruvkb) +and [Hugo Solar](/blog/authors/hugosolar) to unify all of CC websites and applications. Vocabulary has been undergoing a lot of changes lately. As part of my Outreachy internship, I will be contributing to extending its scope and usage. diff --git a/content/blog/entries/cc-vocabulary-new-design-system/contents.lr b/content/blog/entries/cc-vocabulary-new-design-system/contents.lr index d378da423..f4f30e7bc 100644 --- a/content/blog/entries/cc-vocabulary-new-design-system/contents.lr +++ b/content/blog/entries/cc-vocabulary-new-design-system/contents.lr @@ -260,7 +260,7 @@ Creative Commons, _powered by CC Vocabulary_. CC Vocabulary is out now, with its code, design and translations on GitHub and a live styleguide hosted on GitHub pages. Please [check it -out](https://creativecommons.github.io/cc-vocabulary/) and join the discussions. +out](/cc-vocabulary/) and join the discussions. Since it is too early to even call it a beta, your feedback is crucial in shaping its future and with it, the future of all Creative Commons apps. diff --git a/content/blog/entries/cc-vocabulary-so-far/contents.lr b/content/blog/entries/cc-vocabulary-so-far/contents.lr index 95930404a..c983c6018 100644 --- a/content/blog/entries/cc-vocabulary-so-far/contents.lr +++ b/content/blog/entries/cc-vocabulary-so-far/contents.lr @@ -66,7 +66,7 @@ of its offerings in your latest project. CC Vocabulary is out now, with its code, design and translations on GitHub and a live styleguide hosted on GitHub pages. Please [check it -out](https://creativecommons.github.io/cc-vocabulary/) and join the discussions. +out](/cc-vocabulary/) and join the discussions. Since it is too early to even call it a beta, your feedback is crucial in shaping its future and with it, the future of all Creative Commons apps. diff --git a/content/blog/entries/cc-vocabulary-the-main-course/contents.lr b/content/blog/entries/cc-vocabulary-the-main-course/contents.lr index ba30b05d2..fbd178b9c 100644 --- a/content/blog/entries/cc-vocabulary-the-main-course/contents.lr +++ b/content/blog/entries/cc-vocabulary-the-main-course/contents.lr @@ -23,7 +23,7 @@ use for consistency and ease of development. - **Week 3:** we ground spices: _developed and incorporated design tokens_. - **Weeks 4-5:** we cooked appetizers: _our collection of simple Elements_. - **Weeks 6-7:** we cooked the main dishes: _our collection of very functional Patterns and Layouts_. -- **Last week:** we garnished these dishes: _a splash of styling for the [styleguide](https://opensource.creativecommons.org/cc-vocabulary) itself_. +- **Last week:** we garnished these dishes: _a splash of styling for the [styleguide](/cc-vocabulary) itself_. **Today, main course is served, _hot_.** diff --git a/content/blog/entries/data-flow-API-to-DB/contents.lr b/content/blog/entries/data-flow-API-to-DB/contents.lr index 98f5113ac..e60c6d325 100644 --- a/content/blog/entries/data-flow-API-to-DB/contents.lr +++ b/content/blog/entries/data-flow-API-to-DB/contents.lr @@ -43,7 +43,7 @@ about CC licensed images from the respective providers , the data pulled is structured into a standardised format and written into a TSV (Tab Separated Values) file locally. These TSV files are then loaded into S3 and then finally to PostgreSQL DB by the loader workflow. -[dags]: https://github.com/creativecommons/cccatalog/tree/dacb48d24c6ae9b532ff108589b9326bde0d37a3/src/cc_catalog_airflow/dags +[dags]: https://github.com/cc-archive/cccatalog/tree/dacb48d24c6ae9b532ff108589b9326bde0d37a3/src/cc_catalog_airflow/dags ## Provider API workflow The provider workflows are usually scheduled in one of two time frequencies, @@ -77,7 +77,7 @@ cron expression. Example: Cleveland museum is currently scheduled for a monthly crawl with a starting date as ```2020-01-15```. [cleveland_museum_workflow][clm_workflow] -[clm_workflow]: https://github.com/creativecommons/cccatalog/blob/dacb48d24c6ae9b532ff108589b9326bde0d37a3/src/cc_catalog_airflow/dags/cleveland_museum_workflow.py +[clm_workflow]: https://github.com/cc-archive/cccatalog/blob/dacb48d24c6ae9b532ff108589b9326bde0d37a3/src/cc_catalog_airflow/dags/cleveland_museum_workflow.py ## Loader workflow The data from the provider scripts are not directly loaded into S3. Instead, diff --git a/content/blog/entries/date-partitioned-data-reingestion/contents.lr b/content/blog/entries/date-partitioned-data-reingestion/contents.lr index 594963129..a327103e7 100644 --- a/content/blog/entries/date-partitioned-data-reingestion/contents.lr +++ b/content/blog/entries/date-partitioned-data-reingestion/contents.lr @@ -209,4 +209,4 @@ current date is 2020). For more context around what we've shown here, please take a look at [the CC Catalog repo][cccatalog]. -[cccatalog]: https://github.com/creativecommons/cccatalog/ +[cccatalog]: https://github.com/cc-archive/cccatalog/ diff --git a/content/blog/entries/flickr-sub-provider-retrieval/contents.lr b/content/blog/entries/flickr-sub-provider-retrieval/contents.lr index 662b15992..d40ba8654 100644 --- a/content/blog/entries/flickr-sub-provider-retrieval/contents.lr +++ b/content/blog/entries/flickr-sub-provider-retrieval/contents.lr @@ -27,7 +27,7 @@ While there are several providers such as Flickr, Europeana, and Smithsonian fro sub-providers, the consensus was to initially focus on Flickr due to that currently being in production, and since a substantial amount of images made available via CC Search come from Flickr. Thus, in this initial blog post, I will discuss how I addressed the requirement of sub-provider retrieval in Flickr by making the necessary changes in the -[Creative Commons Catalog](https://github.com/creativecommons/cccatalog) repository. +[Creative Commons Catalog](https://github.com/cc-archive/cccatalog) repository. ## Research The primary research involved in the Flickr sub-provider retrieval task was defining which entities to identify as @@ -217,7 +217,7 @@ id | provider | source before the update | source after the update For more information regarding the implementation, please refer to the following PR: -https://github.com/creativecommons/cccatalog/pull/420 +https://github.com/cc-archive/cccatalog/pull/420 ## Acknowledgement diff --git a/content/blog/entries/improving-cc-license-chooser-outcomes/contents.lr b/content/blog/entries/improving-cc-license-chooser-outcomes/contents.lr index fa1b8d2fb..1c791db73 100644 --- a/content/blog/entries/improving-cc-license-chooser-outcomes/contents.lr +++ b/content/blog/entries/improving-cc-license-chooser-outcomes/contents.lr @@ -39,7 +39,7 @@ Working remotely also let me have a flexible work schedule. While ensuring that ### Working together -It's been a pleasure to work with Creative Commons team. My mentors, [Kriti](https://creativecommons.org/author/kriticreativecommons-org/) and [Ari](https://opensource.creativecommons.org/blog/authors/akmadian/), together with [Anna](https://creativecommons.org/author/annacreativecommons-org/), Francisco Vera and [Breno](https://creativecommons.org/author/brenoferreira/), were there for me all through the internship, help me feel a part of CC team. +It's been a pleasure to work with Creative Commons team. My mentors, [Kriti](https://creativecommons.org/author/kriticreativecommons-org/) and [Ari](/blog/authors/akmadian/), together with [Anna](https://creativecommons.org/author/annacreativecommons-org/), Francisco Vera and [Breno](https://creativecommons.org/author/brenoferreira/), were there for me all through the internship, help me feel a part of CC team. But the CC community is much wider than that! I've been amazed at the enthusiasm of the users who helped us with the UX testing, and at the speed with which they jumped on the task of translating the website as soon as we published the text on Transifex. diff --git a/content/blog/entries/improving-cc-license-chooser-weeks-1-2-design/contents.lr b/content/blog/entries/improving-cc-license-chooser-weeks-1-2-design/contents.lr index bd11bdb4f..c993b5af4 100644 --- a/content/blog/entries/improving-cc-license-chooser-weeks-1-2-design/contents.lr +++ b/content/blog/entries/improving-cc-license-chooser-weeks-1-2-design/contents.lr @@ -13,7 +13,7 @@ series: outreachy-dec-2019-chooser pub_date: 2020-01-06 --- body: -Creative Commons License Chooser has been helping creators to choose the most appropriate license for their work for a long time. As anything on the web, it needs updating. One of my mentors, [Ari Madian](https://opensource.creativecommons.org/blog/authors/akmadian/), has created the new version of this chooser as part of his 2019 GSoC Project. As a 2019-2020 Outreachy intern, I will be working on making it production-ready. The goals of my internship include: +Creative Commons License Chooser has been helping creators to choose the most appropriate license for their work for a long time. As anything on the web, it needs updating. One of my mentors, [Ari Madian](/blog/authors/akmadian/), has created the new version of this chooser as part of his 2019 GSoC Project. As a 2019-2020 Outreachy intern, I will be working on making it production-ready. The goals of my internship include: - Improving usability of the Chooser and making it easier for licensors to understand the process of selecting the most appropriate license. - Setting up and automating internalization. diff --git a/content/blog/entries/integration-vocabulary-ccos/contents.lr b/content/blog/entries/integration-vocabulary-ccos/contents.lr index 2df1b28cf..3652e3a80 100644 --- a/content/blog/entries/integration-vocabulary-ccos/contents.lr +++ b/content/blog/entries/integration-vocabulary-ccos/contents.lr @@ -15,7 +15,7 @@ pub_date: 2020-07-08 body: -This blog demonstrates the project I am working on during the course of my Outreachy internship. My project involves redesigning and reimplementing one of the web products of the CC network using our new cohesive design library — [Vocabulary](https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-introduction--page). After my internship is completed, the [Creative Commons Open Source](https://opensource.creativecommons.org/) website will have a complete revamped interface that will extensively use Vocabulary components. +This blog demonstrates the project I am working on during the course of my Outreachy internship. My project involves redesigning and reimplementing one of the web products of the CC network using our new cohesive design library — [Vocabulary](https://cc-vocabulary.netlify.app/?path=/docs/vocabulary-introduction--page). After my internship is completed, the [Creative Commons Open Source](/) website will have a complete revamped interface that will extensively use Vocabulary components. ## The Problem - diff --git a/content/blog/entries/introducing-cc-search-extension/contents.lr b/content/blog/entries/introducing-cc-search-extension/contents.lr index 2257d3e72..c8d866804 100644 --- a/content/blog/entries/introducing-cc-search-extension/contents.lr +++ b/content/blog/entries/introducing-cc-search-extension/contents.lr @@ -47,7 +47,7 @@ In this section, I will go through all the major features(exclusive of any techn - **Search and filter CC Licensed content** -This feature is at the core and the extension does a good job. The searching and filtering is powered by [CC Catalog API](https://github.com/creativecommons/cccatalog-api) which exposes various endpoints to get search results and apply filters for providers, licenses, and use-case. This makes sure that you will find exactly what are you looking for. +This feature is at the core and the extension does a good job. The searching and filtering is powered by [CC Catalog API](https://github.com/cc-archive/cccatalog-api) which exposes various endpoints to get search results and apply filters for providers, licenses, and use-case. This makes sure that you will find exactly what are you looking for.
@@ -161,7 +161,7 @@ We hope that you will give this a shot and maybe use it as your daily driver to You can check out the [project on Github](https://github.com/creativecommons/ccsearch-browser-extension). -Come and say hi to us on [slack](https://opensource.creativecommons.org/community/#slack) and tell about your experience with CC Search extension. The slack channel is `#gsoc-browser-ext`. +Come and say hi to us on [slack](/community/#slack) and tell about your experience with CC Search extension. The slack channel is `#gsoc-browser-ext`. *Special Thanks*: [Alden](https://creativecommons.org/author/aldencreativecommons-org/), [Timid](https://creativecommons.org/author/timidcreativecommons-org/) and [Kriti](https://creativecommons.org/author/kriticreativecommons-org/) \ No newline at end of file diff --git a/content/blog/entries/linked-commons-data-update/contents.lr b/content/blog/entries/linked-commons-data-update/contents.lr index eb8c24ce6..3f3eda80f 100644 --- a/content/blog/entries/linked-commons-data-update/contents.lr +++ b/content/blog/entries/linked-commons-data-update/contents.lr @@ -25,7 +25,7 @@ So far the Linked Commons was using a tiny subset of the data available in the C ## Pilot -The raw CC Catalog data cannot be used directly in the Linked Commons. Our first task involves processing it, which includes removing isolated nodes, etc. You can read more about it in the data processing series [blog](https://opensource.creativecommons.org/blog/entries/cc-datacatalog-data-processing/) written by my mentor Maria. After this, we need to build a database which stores the **"distance list"** of all the nodes. +The raw CC Catalog data cannot be used directly in the Linked Commons. Our first task involves processing it, which includes removing isolated nodes, etc. You can read more about it in the data processing series [blog](/blog/entries/cc-datacatalog-data-processing/) written by my mentor Maria. After this, we need to build a database which stores the **"distance list"** of all the nodes. ### What is "distance list"? @@ -85,7 +85,7 @@ This small change in the design simplified a lot of things, and now the new grap This task was really challenging and I learnt a lot. It was really mesmerizing to see the **Linked Commons grow and evolve**. I hope you enjoyed reading this blog. You can follow the project development [here](https://github.com/cc-archive/cccatalog-dataviz/), and access the stable version of linked commons [here](http://dataviz.creativecommons.engineering/). -Feel free to report bugs and suggest features. It will help us improve this project. If you wish to join the our team, consider joining our [slack](https://creativecommons.slack.com/channels/cc-dev-cc-catalog-viz) channel. Read more about our community teams [here](https://opensource.creativecommons.org/community/). See you in my next blog! 🚀 +Feel free to report bugs and suggest features. It will help us improve this project. If you wish to join the our team, consider joining our [slack](https://creativecommons.slack.com/channels/cc-dev-cc-catalog-viz) channel. Read more about our community teams [here](/community/). See you in my next blog! 🚀 ___ **Linked Commons uses a more complex schema. The picture is just for illustration.* diff --git a/content/blog/entries/meet-gsoc-2019-students/contents.lr b/content/blog/entries/meet-gsoc-2019-students/contents.lr index 8d5b80851..0ba3274e0 100644 --- a/content/blog/entries/meet-gsoc-2019-students/contents.lr +++ b/content/blog/entries/meet-gsoc-2019-students/contents.lr @@ -39,7 +39,7 @@ summer. Here they are! adding new features like integrating with CC Search. Ahmad’s mentor is our Core Systems Manager Timid Robot Zehta, backed up by Hugo Solar.

-

You can follow the progress of this project through the GitHub repo or on the #cc-dev-wordpress channel on our Slack community.

+

You can follow the progress of this project through the GitHub repo or on the #cc-dev-wordpress channel on our Slack community.

ahmad bilal
@@ -66,7 +66,7 @@ summer. Here they are! in sites built using modern JavaScript frameworks (specifically Vue.js) as well as simpler websites built using WordPress. CC’s Web Developer Hugo Solar serves as primary mentor, with backup from Sophine Clachar.

-

You can follow the progress of this project through the GitHub repo or on the #gsoc-cc-vocabulary channel on our Slack community.

+

You can follow the progress of this project through the GitHub repo or on the #gsoc-cc-vocabulary channel on our Slack community.

dhruv bhanushali
@@ -94,7 +94,7 @@ summer. Here they are! the most content, which CC licenses are used the most, and much more. She will be mentored by our Data Engineer Sophine Clachar with backup from Breno Ferreira.

-

You can follow the progress of this project through the GitHub repo or on the #gsoc-cc-catalog-viz channel on our Slack community.

+

You can follow the progress of this project through the GitHub repo or on the #gsoc-cc-catalog-viz channel on our Slack community.

María Belén Guaranda Cabezas
@@ -114,7 +114,7 @@ summer. Here they are!

Ari will be working on creating a modern human-centered version of our CC license chooser tool, which is long overdue for an update. His work will focus on design and usability as well as code. CC’s Front End Engineer Breno Ferreira is the primary mentor for this project with support from Alden Page.

-

You can follow the progress of this project through the GitHub repo or on the #gsoc-license-chooser channel on our Slack community.

+

You can follow the progress of this project through the GitHub repo or on the #gsoc-license-chooser channel on our Slack community.

Ari Madian
@@ -140,13 +140,13 @@ summer. Here they are! switch to a new website. Mayank will be mentored by CC’s Software Engineer Alden Page with support from Timid Robot Zehta.

-

You can follow the progress of this project through the GitHub repo or on the #gsoc-browser-ext channel on our Slack community.

+

You can follow the progress of this project through the GitHub repo or on the #gsoc-browser-ext channel on our Slack community.

You can visit the Creative Commons organization page on Google Summer of Code site to see longer descriptions of the projects. We welcome community input and feedback – you are the users of all these products and we’d love for you to be involved. So don’t - hesitate to join the project Slack channel or talk to us on GitHub or our other community forums.

+ hesitate to join the project Slack channel or talk to us on GitHub or our other community forums.

Mayank Nader
diff --git a/content/blog/entries/overview-of-the-gsoc-2020-project/contents.lr b/content/blog/entries/overview-of-the-gsoc-2020-project/contents.lr index a3870a3f0..32f263fcb 100644 --- a/content/blog/entries/overview-of-the-gsoc-2020-project/contents.lr +++ b/content/blog/entries/overview-of-the-gsoc-2020-project/contents.lr @@ -77,12 +77,12 @@ Brent for his guidance. [flickr_blog_post]: ../flickr-sub-provider-retrieval/ [unit_code_blog_post]: ../smithsonian-unit-code-update/ [reingest_blog_post]: ../date-partitioned-data-reingestion/ -[pr_420]: https://github.com/creativecommons/cccatalog/pull/420 -[pr_442]: https://github.com/creativecommons/cccatalog/pull/442 -[pr_455]: https://github.com/creativecommons/cccatalog/pull/455 -[pr_461]: https://github.com/creativecommons/cccatalog/pull/461 -[pr_465]: https://github.com/creativecommons/cccatalog/pull/465 -[pr_474]: https://github.com/creativecommons/cccatalog/pull/474 -[pr_476]: https://github.com/creativecommons/cccatalog/pull/476 -[pr_483]: https://github.com/creativecommons/cccatalog/pull/483 -[issue_397]: https://github.com/creativecommons/cccatalog/issues/397 \ No newline at end of file +[pr_420]: https://github.com/cc-archive/cccatalog/pull/420 +[pr_442]: https://github.com/cc-archive/cccatalog/pull/442 +[pr_455]: https://github.com/cc-archive/cccatalog/pull/455 +[pr_461]: https://github.com/cc-archive/cccatalog/pull/461 +[pr_465]: https://github.com/cc-archive/cccatalog/pull/465 +[pr_474]: https://github.com/cc-archive/cccatalog/pull/474 +[pr_476]: https://github.com/cc-archive/cccatalog/pull/476 +[pr_483]: https://github.com/cc-archive/cccatalog/pull/483 +[issue_397]: https://github.com/cc-archive/cccatalog/issues/397 \ No newline at end of file diff --git a/content/blog/entries/resource-gathering/contents.lr b/content/blog/entries/resource-gathering/contents.lr index ed8beaa21..ea768fda5 100644 --- a/content/blog/entries/resource-gathering/contents.lr +++ b/content/blog/entries/resource-gathering/contents.lr @@ -15,7 +15,7 @@ pub_date: 2020-06-09 body: -As an outreachy intern, I am handling the integration of [Creative Commons](https://creativecommons.org/) design library — [Vocabulary](https://cc-vocabulary.netlify.app/) with one of our web products — [CC OS](https://opensource.creativecommons.org/). I have been working the design library for 3–4 months now and I have enjoyed the experience the library caters and I am trying to achieve the same experience in the Open source website. To understand UX in-depth, I have been reading different resources and document this knowledge through this series of blogs. This in-depth information will help me achieve the desired experience through the library. +As an outreachy intern, I am handling the integration of [Creative Commons](https://creativecommons.org/) design library — [Vocabulary](https://cc-vocabulary.netlify.app/) with one of our web products — [CC OS](/). I have been working the design library for 3–4 months now and I have enjoyed the experience the library caters and I am trying to achieve the same experience in the Open source website. To understand UX in-depth, I have been reading different resources and document this knowledge through this series of blogs. This in-depth information will help me achieve the desired experience through the library. Using a Coursera course, [Introduction to user experience](https://www.coursera.org/learn/user-experience-design/), I will be describing the UX design cycle with a series of articles and this article is about describing the first step of the design cycle which is Resource Gathering. diff --git a/content/blog/entries/science-museum-implementation/contents.lr b/content/blog/entries/science-museum-implementation/contents.lr index f2f856a16..f49cadf1e 100644 --- a/content/blog/entries/science-museum-implementation/contents.lr +++ b/content/blog/entries/science-museum-implementation/contents.lr @@ -117,7 +117,7 @@ have multiple images with it and using object id we cannot determine the image u for each image. Currently image id is taken from ```multimedia```, multimedia is a field in the json response that lists multiple images and their metadata, for each image data in multimedia, foreign id is in ```admin.uid```. -The implementation can be found [here](https://github.com/creativecommons/cccatalog/blob/master/src/cc_catalog_airflow/dags/provider_api_scripts/science_museum.py). +The implementation can be found [here](https://github.com/cc-archive/cccatalog/blob/master/src/cc_catalog_airflow/dags/provider_api_scripts/science_museum.py). ### Results: Running the scripts we get: @@ -129,6 +129,6 @@ The problem with current implementation is that records with no date would be mi Science Museum provider is the first provider I worked on as a part of the internship and thank my mentor Brent Moran for the help. ### Additional Details : -- [research work](https://github.com/creativecommons/cccatalog/issues/302) -- [implementation](https://github.com/creativecommons/cccatalog/pull/400) +- [research work](https://github.com/cc-archive/cccatalog/issues/302) +- [implementation](https://github.com/cc-archive/cccatalog/pull/400) diff --git a/content/blog/entries/searching-300-million/contents.lr b/content/blog/entries/searching-300-million/contents.lr index 00c0b31ce..61981dad1 100644 --- a/content/blog/entries/searching-300-million/contents.lr +++ b/content/blog/entries/searching-300-million/contents.lr @@ -33,7 +33,7 @@ Instead of using Django signals to incrementally add individual items to the dat ![Ingestion Server](ingestion_diagram.jpg) -The piece of software responsible for updating our search data is called [Ingestion Server](https://github.com/creativecommons/cccatalog-api/tree/master/ingestion_server/ingestion_server). It copies data from the CC Catalog into the production PostgreSQL database, and then indexes that data inside of Elasticsearch in bulk. The tricky part about this is that we had to reload the data without impacting performance or availability of the production system. So, if the ingestion were to fail for some reason (Elasticsearch or our database runs out of space, malformed data breaks the indexer, etc), the users shouldn’t even notice. To accomplish that, all data is loaded into temporary tables and indices, tested for defects, and then promoted to the “live” search index. +The piece of software responsible for updating our search data is called [Ingestion Server](https://github.com/cc-archive/cccatalog-api/tree/master/ingestion_server/ingestion_server). It copies data from the CC Catalog into the production PostgreSQL database, and then indexes that data inside of Elasticsearch in bulk. The tricky part about this is that we had to reload the data without impacting performance or availability of the production system. So, if the ingestion were to fail for some reason (Elasticsearch or our database runs out of space, malformed data breaks the indexer, etc), the users shouldn’t even notice. To accomplish that, all data is loaded into temporary tables and indices, tested for defects, and then promoted to the “live” search index. ## Searching 300 million works in high traffic conditions diff --git a/content/blog/entries/smithsonian-unit-code-update/contents.lr b/content/blog/entries/smithsonian-unit-code-update/contents.lr index 6185094bc..f2e38a17c 100644 --- a/content/blog/entries/smithsonian-unit-code-update/contents.lr +++ b/content/blog/entries/smithsonian-unit-code-update/contents.lr @@ -34,7 +34,7 @@ changes to the *unit code* values and keep the *SMITHSONIAN_SUB_PROVIDERS* dicti [cc_search]: https://ccsearch.creativecommons.org/ [cc_api]: https://api.creativecommons.engineering/v1/ [flickr_blog_post]: ../flickr-sub-provider-retrieval/ -[pr_455]: https://github.com/creativecommons/cccatalog/pull/455 +[pr_455]: https://github.com/cc-archive/cccatalog/pull/455 ## Implementation ### Retrieving the latest unit codes diff --git a/content/blog/entries/ssr-ccsearch/contents.lr b/content/blog/entries/ssr-ccsearch/contents.lr index 8b326c505..b4696267b 100644 --- a/content/blog/entries/ssr-ccsearch/contents.lr +++ b/content/blog/entries/ssr-ccsearch/contents.lr @@ -19,7 +19,7 @@ While easier to implement initially, when we needed to ship the initial versions 2. Empty HTML page: When the initial HTML sent by the server is empty, meaning no visual elements, any internet bots that parse a page HTML wouldn't work properly, that is: SEO, social media websites (when users share a link to CC Search on Twitter or Facebook, those nice previews wouldn't work), the Web Archive, etc.. -So on July 26th we deployed our first release of CC Search with Server Side Rendering. You can see the work that went into it on this [Pull Request on Github](https://github.com/creativecommons/cccatalog-frontend/pull/411). +So on July 26th we deployed our first release of CC Search with Server Side Rendering. You can see the work that went into it on this [Pull Request on Github](https://github.com/cc-archive/cccatalog-frontend/pull/411). My goal with this blog post will be to explain some of the challenges that we faced while both coding the SSR support on the VueJS codebase and also the operations side with deployment and maintenance. @@ -36,7 +36,7 @@ On some cases, a simple check for undefined values is sufficient, for example: ``` const queryParams = !(typeof window === 'undefined') ? window.location.search : ''; ``` -_link to change diff [here](https://github.com/creativecommons/cccatalog-frontend/pull/411/files#diff-e3b1ca4ad5a207c170c97a435b3d1ff3L15)_ +_link to change diff [here](https://github.com/cc-archive/cccatalog-frontend/pull/411/files#diff-e3b1ca4ad5a207c170c97a435b3d1ff3L15)_ There were also cases of components that accessed browser APIs directly on, for example, `computed` values. Since those values are eagerly evaluated during render of a component, it would break on server rendering. @@ -48,7 +48,7 @@ mounted() { this.shareURL = window.location.href; } ``` -_link to change diff [here](https://github.com/creativecommons/cccatalog-frontend/pull/411/files#diff-f987cb63f02cb3471ab3cfae238746f7R37)_ +_link to change diff [here](https://github.com/cc-archive/cccatalog-frontend/pull/411/files#diff-f987cb63f02cb3471ab3cfae238746f7R37)_ But there was a more complicated case in which we had dependencies to visual components which in turn depended on these browser APIs to render. One in particular was the image search result grid, which is a responsive grid layout that fits all images nicely on whatever screen size the users have. @@ -62,9 +62,9 @@ One of the cases, we had a dependency tree that looked like this: A few other page components also depended on this `GridLayoutComponent` component. Our solution was to split the higher level components into server and client versions. The browser version would render the search grid, and the server version wouldn't. -You can an example of this case with the client version of the component [here](https://github.com/creativecommons/cccatalog-frontend/pull/411/commits/d3e05c01262d4fbc5bed1eceb1c256fc8da9ea80#diff-15c47fe052b8e07589e6cd5c7ce126fe) and the server version [here](https://github.com/creativecommons/cccatalog-frontend/pull/411/commits/d3e05c01262d4fbc5bed1eceb1c256fc8da9ea80#diff-9bfa3295d81a84c0fee1b5af98992561). We used a mixin to provide the component interaction logic [here](https://github.com/creativecommons/cccatalog-frontend/pull/411/commits/d3e05c01262d4fbc5bed1eceb1c256fc8da9ea80#diff-b4102772ceac63ff8d35545a2d003200). +You can an example of this case with the client version of the component [here](https://github.com/cc-archive/cccatalog-frontend/pull/411/commits/d3e05c01262d4fbc5bed1eceb1c256fc8da9ea80#diff-15c47fe052b8e07589e6cd5c7ce126fe) and the server version [here](https://github.com/cc-archive/cccatalog-frontend/pull/411/commits/d3e05c01262d4fbc5bed1eceb1c256fc8da9ea80#diff-9bfa3295d81a84c0fee1b5af98992561). We used a mixin to provide the component interaction logic [here](https://github.com/cc-archive/cccatalog-frontend/pull/411/commits/d3e05c01262d4fbc5bed1eceb1c256fc8da9ea80#diff-b4102772ceac63ff8d35545a2d003200). -Since we had different components, we also needed different routers that mapped to the [server](https://github.com/creativecommons/cccatalog-frontend/pull/411/files#diff-96a7306e1ed8bbbc4982aac42b5ef8df) and [client](https://github.com/creativecommons/cccatalog-frontend/pull/411/files#diff-9b23694ae94e6ff902037f3d79772bae) components. +Since we had different components, we also needed different routers that mapped to the [server](https://github.com/cc-archive/cccatalog-frontend/pull/411/files#diff-96a7306e1ed8bbbc4982aac42b5ef8df) and [client](https://github.com/cc-archive/cccatalog-frontend/pull/411/files#diff-9b23694ae94e6ff902037f3d79772bae) components. ## Deployment @@ -74,7 +74,7 @@ One thing we did, and still do, is build the assets for both server and client r ### Micro cache -Soon after we deployed the initial release of SSR, we noticed that our Node servers were sometimes crashing, for memory exhaustion reasons, or sometimes taking too long to respond due to GC running. It seems that rendering Vue apps has a [high memory footprint from components and their Virtual DOM Nodes](https://ssr.vuejs.org/guide/caching.html#page-level-caching). Because of that, we decided to adopt a micro-caching of every server response, as you can see [here](https://github.com/creativecommons/cccatalog-frontend/pull/475/commits/aa5ee97101d38443416ef19a954dff63031e293a). Important caveat: no CC Search page has user specific content. They all serve the same content, no matter which user requests it. So that makes it trivial to cache the responses, since the response never changes for individual users. If that were the case, we either wouldn't be able to cache the response or only cache some request responses but not others. +Soon after we deployed the initial release of SSR, we noticed that our Node servers were sometimes crashing, for memory exhaustion reasons, or sometimes taking too long to respond due to GC running. It seems that rendering Vue apps has a [high memory footprint from components and their Virtual DOM Nodes](https://ssr.vuejs.org/guide/caching.html#page-level-caching). Because of that, we decided to adopt a micro-caching of every server response, as you can see [here](https://github.com/cc-archive/cccatalog-frontend/pull/475/commits/aa5ee97101d38443416ef19a954dff63031e293a). Important caveat: no CC Search page has user specific content. They all serve the same content, no matter which user requests it. So that makes it trivial to cache the responses, since the response never changes for individual users. If that were the case, we either wouldn't be able to cache the response or only cache some request responses but not others. After implementing this cache, we saw that the memory consumption dropped dramatically and response times were now constant of a few milliseconds. Node wasn't crashing because it ran out of memory and GC wasn't being triggered as much lowering response times. @@ -83,12 +83,12 @@ After implementing this cache, we saw that the memory consumption dropped dramat Another optimization was to not repeat requests, which were made on the server, again on the client. One example is the [image details page](https://ccsearch.creativecommons.org/photos/df2e7f75-7fe9-457b-a58f-edc1833a1ed8). The image can be loaded both on the server and the client, but we don't want the user to request the image data if it was already loaded on the server. -We did this by using the `serverPrefetch` method to load the data on the server, but on the client, in the `mounted` method, we check if the data isn't already available before making the request. You can see how that works [here](https://github.com/creativecommons/cccatalog-frontend/pull/411/files#diff-e33cf6c2e6f63a3ac958ac500eeabcaaR87). +We did this by using the `serverPrefetch` method to load the data on the server, but on the client, in the `mounted` method, we check if the data isn't already available before making the request. You can see how that works [here](https://github.com/cc-archive/cccatalog-frontend/pull/411/files#diff-e33cf6c2e6f63a3ac958ac500eeabcaaR87). ## Future improvements As said before, we have a dependency on a component that uses browser APIs which doesn't work on the server side. That dependency is [Masonry Layout](https://github.com/shershen08/vue-masonry). And because of that, we had to split components and router into server and client versions. -To remove that complexity, we will probably try to use a pure-CSS approach to generate the responsive grid, as described in [this issue on Github](https://github.com/creativecommons/cccatalog-frontend/issues/489). If that doesn't work, we'll use something like [vue-client-only](https://github.com/egoist/vue-client-only). +To remove that complexity, we will probably try to use a pure-CSS approach to generate the responsive grid, as described in [this issue on Github](https://github.com/cc-archive/cccatalog-frontend/issues/489). If that doesn't work, we'll use something like [vue-client-only](https://github.com/egoist/vue-client-only). --- series: diff --git a/content/blog/entries/vocabulary-so-long/contents.lr b/content/blog/entries/vocabulary-so-long/contents.lr index 075248ed3..98fa350c9 100644 --- a/content/blog/entries/vocabulary-so-long/contents.lr +++ b/content/blog/entries/vocabulary-so-long/contents.lr @@ -77,7 +77,7 @@ got the standards like `InputField` and `Button`, some unconventional ones like `Definition` and `Quote`, and some components that only our own tailored design library could afford like `Header` and `Footer`. -Here's a list and [there's](https://creativecommons.github.io/cc-vocabulary) +Here's a list and [there's](/cc-vocabulary) a living styleguide.

@@ -175,7 +175,7 @@ the designs and revisions, was accomplished in two months and a half_. The code follows the [Standard code style](https://standardjs.com/) and the [Vue official style guide](https://vuejs.org/v2/style-guide/). In addition, Vocabulary has [its own style -guide](https://opensource.creativecommons.org/cc-vocabulary/#/Vocabulary/Code%20style) +guide](/cc-vocabulary/#/Vocabulary/Code%20style) that has rules right down to the order of rules in the CSS. This ensures that code is sensibly written, easily understandable and as little in debt as possible. @@ -318,7 +318,7 @@ Plus Font Awesome provides Vue components! What's not to like. I'm not sure if there is enough time in the GSoC period for the integration PR to be reviewed and merged but I'm not going anywhere and neither are you. You can follow the integration as it happens -[here](https://github.com/creativecommons/cccatalog-frontend/pull/413). +[here](https://github.com/cc-archive/cccatalog-frontend/pull/413). If you're enthusiastic you can clone the branch and run the setup on your machine. Experience it for yourself, how about that? @@ -327,9 +327,9 @@ machine. Experience it for yourself, how about that? **Repository:** https://github.com/dhruvkb/cccatalog-frontend/ -**PR**: https://github.com/creativecommons/cccatalog-frontend/pull/413/ +**PR**: https://github.com/cc-archive/cccatalog-frontend/pull/413/ -**Commits:** https://github.com/creativecommons/cccatalog-frontend/pull/413/commits +**Commits:** https://github.com/cc-archive/cccatalog-frontend/pull/413/commits The proposal aimed to replace a lot of indigenous components with Vocabulary counterparts. Internationalisation and a consistent icon system are just me @@ -339,7 +339,7 @@ going above and beyond. Summarising, [CC Vocabulary](https://github.com/creativecommons/cc-vocabulary) is now mature and [is getting -married](https://github.com/creativecommons/cccatalog-frontend/pull/413) to [CC +married](https://github.com/cc-archive/cccatalog-frontend/pull/413) to [CC Search](https://github.com/creativecommons/cc-vocabulary). GSoC was a successful matchmaker. diff --git a/content/blog/entries/what-is-up-ccos/contents.lr b/content/blog/entries/what-is-up-ccos/contents.lr index d6b6eda96..4cf295d96 100644 --- a/content/blog/entries/what-is-up-ccos/contents.lr +++ b/content/blog/entries/what-is-up-ccos/contents.lr @@ -19,7 +19,7 @@ In my previous blog, I demonstrated what my Outreachy project was about. Here I ### The Set-Up - -The [Creative Commons Open Source](https://opensource.creativecommons.org/) website is built using [Lektor](https://www.getlektor.com/). I was not very familiar with it, so I started by going through the documentation and the official website code. I learned how awesome it is and can also be used by non-coders. I got familiar with the [jinja templates](https://palletsprojects.com/p/jinja/) and working of themes in a Lektor app. For integrating new styles from Vocabulary, I replaced `templates/` folder with a `theme/` folder. Here is the link to how [templates](https://www.getlektor.com/docs/templates/) work in Lektor. +The [Creative Commons Open Source](/) website is built using [Lektor](https://www.getlektor.com/). I was not very familiar with it, so I started by going through the documentation and the official website code. I learned how awesome it is and can also be used by non-coders. I got familiar with the [jinja templates](https://palletsprojects.com/p/jinja/) and working of themes in a Lektor app. For integrating new styles from Vocabulary, I replaced `templates/` folder with a `theme/` folder. Here is the link to how [templates](https://www.getlektor.com/docs/templates/) work in Lektor. As the revamping process is gradual, there was a need of setting up a staging environment where we could test the website. Deploying the branch that consists of the ongoing changes was pretty easy, I just followed the official [documentation](https://www.netlify.com/blog/2016/05/25/lektor-on-netlify-a-step-by-step-guide/) provided by Netlify and deployed it.