Merge branch 'master' into hotfix/improve-readme

Author: TimidRobot

content/blog/authors/dhruvkb/contents.lr

@@ -5,6 +5,5 @@ name: Dhruv Bhanushali
 md5_hashed_email: 0eab64adad056cff2492e7c407a9aa21
 ---
 about:
-Dhruv Bhanushali is a Mumbai-based software developer and an Engineering-Physics graduate from IIT Roorkee. He started programming as a hobby in high-school and having found his calling, is now pursuing a career in the field. He is a huge fan of alternative and post-rock music and keeps his curated collection with him at all times. He also loves to binge watch TV shows and movies, especially indie art films.
 
-Dhruv developed [CC Vocabulary](https://opensource.creativecommons.org/cc-vocabulary/) as part of [Google Summer of Code 2019](/gsoc-2019/) and now is a maintainer for the project. He is consistently [`@dhruvkb`](https://dhruvkb.github.io/) everywhere.
+[Dhruv Bhanushali](https://dhruvkb.github.io/) is the Open Source Community Coordinator at Creative Commons. He goes by `@dhruvkb` on the CC Community Slack workspace. Dhruv developed [CC Vocabulary](https://opensource.creativecommons.org/cc-vocabulary/) as part of [Google Summer of Code 2019](/gsoc-2019/) and now is a maintainer for the project.

content/blog/entries/legal-database-features/404-page.png

@@ -0,0 +1,69 @@
+title: CC Legal Database: Developing features
+---
+categories:
+cc-legal-database
+product
+outreachy
+---
+author: krysal
+---
+series: outreachy-may-2020-legal-database
+---
+pub_date: 2020-08-07
+---
+body:
+In this post, I want to update the progress on Reimplementing the CC Legal Database site, my Outreachy project. There are several features added over the last month to date.
+
+### Submission forms
+
+The first thing I wanted to implement was the respective forms so that anyone can submit a case or article to the database. These forms were slightly modified in the redesign (discussed in the previous articles), so now it has fewer mandatory fields to lower the bar and facilitate the contribution of users.
+
+<figure style="text-align: center;">
+    <img src="scholarship-form.png" alt="Form to submit an article related to CC licenses" style="border: 1px solid black; width: 60%;">
+    <figcaption>Scholarship form to submit an article.</figcaption>
+</figure>
+
+For the Scholarship form, for example, it is only needed to share your name, email and a link to propose an article related to any of the CC licenses, although the more information you can provide us the better, in any case, each contribution is reviewed by the staff before publishing.
+
+### Search
+
+The second important task was to allow searching in each of the listings. A basic function to start making use of the exposed information. In the [current site](https://labs.creativecommons.org/caselaw/), this function is delegated to an external service, a certain famous search engine. Filtering is now performed in the backend based on the keywords entered by the user, thus returning the reduced list. Later this will be combined with filtering by tags or topics that are associated with each entry (case or scholarship).
+
+### Automated tests
+
+While developing the mentioned functionalities I was also in charge of adding automatic unit tests, to ensure that future changes to the code base do not damage already functional parts of the site. This, in addition to giving more confidence to future contributors, they provide value immediately, at the time of writing the tests you should think about possible edge cases, so they allowed me to notice a missing validation in a couple of routes and then correct it.
+
+<figure style="text-align: center;">
+    <img src="404-page.png" alt="404 page" style="border:1px solid black; width:70%;">
+    <figcaption>Example of page obtained when requesting a case detail that is not published or doesn't exist.</figcaption>
+</figure>
+
+In this process of adding automated tests I wanted them to run on every pull request created, so I learned how to write a GitHub Action with a PostgreSQL service, the DBMS used in this case. Previously, I had already created a job for linting, so I needed to add another one to run in parallel to save time. This service provided by GitHub is pretty cool and useful, it opens up a world of possibilities, from running third party services like [Lighthouse test](https://github.com/GoogleChrome/lighthouse-ci) to even [send tweets](https://github.com/gr2m/twitter-together)! If you want to see the GitHub Action file configurated for this project, check it out: [`.github/workflows/main.yml`](https://github.com/creativecommons/caselaw/blob/31c3002a7860d78f3fdb464150c5c1b2f8bb86fc/.github/workflows/main.yml).
+
+### Accessibility
+
+To check if the site had shortcomings I did the Lighthouse test on the homepage, discovering that there were indeed some issues to tackle. In principle the results were these:
+
+<figure style="text-align: center;">
+    <img src="lighthouse-before.png" alt="" style="border:1px solid black; width:70%;">
+    <figcaption>Initial Lighthouse test measurements.</figcaption>
+</figure>
+
+The good thing about this test is that it throws up suggestions on how to fix the bugs found, so after adding certain missing attributes and labels, the following results were achieved.
+
+<figure style="text-align: center;">
+    <img src="lighthouse-after.png" alt="" style="border:1px solid black; width:70%;">
+    <figcaption>Lighthouse test measurements after corrections.</figcaption>
+</figure>
+
+There is still room for improvement but at least we are within a quite acceptable green range.
+
+### Other features and tweaks
+
+Some other features were implemented but only relevant to our registered users, that is, the Legal Staff. They consist of Django admin customization, such as filtering records by status, and a particular thing requested, the answers of frequently asked questions need to be displayed formatted, so they are now saved as Markdown text and transformed to HTML with style on the public site, showing lists, bold text, links, etc. The admin can also see a preview while editing.
+
+### Conclusion
+
+After reviewing all done this last month I see significant progress has been made, I have learned many things along the way: more of what Django and its ecosystem offers, about accessibility, continuous integration in Heroku and GitHub, and more. One of the things that makes me most happy is being able to be contributing and being part of an Open Source organization, knowing how it moves and works inside, something I never imagine before.
+
+Time flies and there are less than two weeks left to finish, so if you want to follow the project here is the repository to suggest improvements or report bugs, or if you prefer something less technical you can join us on the [slack channel](https://creativecommons.slack.com/channels/cc-dev-legal-database).

content/blog/entries/legal-database-features/contents.lr

@@ -0,0 +1,164 @@
+title: Say Hello To Our Community Team
+---
+categories:
+announcements
+community
+open-source
+---
+author: dhruvkb
+---
+pub_date: 2020-08-14
+---
+body:
+
+Creative Commons is committed to open-source software. We have over two dozen
+projects, spanning three times as many repositories on GitHub, each with its
+small, but extremely enthusiastic, subcommunity. With only a few full-time
+employees working on these projects, it is vital that we enable members from the
+community to take increased responsibility in developing and maintaining them,
+and growing the community of which they are a part.
+
+With that goal in mind, we've launched our Community Team initiative.
+
+### What is the Community Team?
+
+Communities that grow organically around open source projects tend to be a bit
+disorganised and the frequency of contributions and degree of involvement tends
+to vary from member to member. Our goal is to identify contributors who are
+actively involved within their communities and give them increased permissions
+over the codebase and access to more information channels and tools in an effort
+to empower them to participate more fully in the project.
+
+This is not restricted to code though. We're also looking for people who work
+with the community on other aspects of the projects, such as design,
+documentation, evangelism, and onboarding to name a few.
+
+- The Community Team establishes a framework for formalising the level of
+  involvement, which is a spectrum, into discrete level or 'roles'.
+- Each role is mapped to a set of responsibilities that a member holding the
+  role is encouraged to take up.
+- Each role also entrusts the members holding it to certain privileges, accesses
+  and permissions, to help them execute these responsibilities.
+
+Roles also progressively include members in our roadmaps and planning meetings
+to ensure that the community is aligned with our long-term goals.
+
+### What's in it for me?
+
+The Community Team is not just a one-sided deal. Your membership in the
+Community Team is just as beneficial for the you as it is for us. While there is
+a [laundry list of benefits][benefits] that you're entitled to, I'll just
+mention some notable ones here.
+
+[benefits]:/community/community-team/#benefits-of-joining-the-community-team
+
+- You gain real-world practical experience of working on open-source projects.
+- You gain both soft-skills and technical-skills by interacting with other
+  developers from both the community as well as CC staff.
+- Since we've already seen the quality of your work and involvement with the
+  community, you get priority in internship applications*.
+
+Oh and, lest I forget, you'll receive CC swag!
+
+<blockquote class="twitter-tweet" data-align="center">
+  <p lang="en" dir="ltr">
+    Thanks for the goodies!!
+    <a href="https://twitter.com/creativecommons?ref_src=twsrc%5Etfw">@creativecommons</a>
+    😀
+    <a href="https://twitter.com/hashtag/OpenSource?src=hash&amp;ref_src=twsrc%5Etfw">#OpenSource</a>
+    <a href="https://twitter.com/hashtag/creativecommons?src=hash&amp;ref_src=twsrc%5Etfw">#creativecommons</a>
+    <a href="https://twitter.com/hashtag/GSoC?src=hash&amp;ref_src=twsrc%5Etfw">#GSoC</a>
+    <a href="https://t.co/DFvpXCs8uu">pic.twitter.com/DFvpXCs8uu</a>
+  </p>
+  &mdash;
+  Mayank Nader (@MayankNader)
+  <a href="https://twitter.com/MayankNader/status/1137995920866390016?ref_src=twsrc%5Etfw">June 10, 2019</a>
+</blockquote>
+<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+### What are these 'roles'?
+
+If you've reached this point, I assume you see the potential of the Community
+Team. Let's see where you'd fit in them.
+
+We have two kinds of roles, code-oriented [Project roles][projectroles], that
+give you responsibilities and permissions related to one CC project, and
+non-code-oriented [Community Building roles][communitybuildingroles], that give
+you responsibilities and permissions related to improving the community of all
+CC projects as a whole.
+
+[projectroles]:/community/community-team/project-roles/
+[communitybuildingroles]:/community/community-team/community-building-roles/
+
+Each type has a few levels but that I'll just link them for you to read on your
+own. While your eligibility for any role depends on how involved you have been
+in the past, the role you choose reflects how involved you would like to be in
+the future.
+
+Start by asking yourself a simple question, "Do I code?"
+
+#### "Sure, I can code..."
+
+*That's awesome!* We have projects in a diverse array of languages, using myriad
+tools and frameworks. Depending on the skills you have, or are planning to
+acquire, you can pick a project and start contributing to it. Based on your
+contributions and your familiarity with the codebase, you can then apply for the
+role that matches your desired level of involvement.
+
+So if you want to be lightly involved with code-reviews and would like to know
+about our plans in advance, you can start off as a Project Contributor. This is
+a fantastic role to get started with and ensures that you get excellent
+mentorship as you start your FOSS journey.
+
+As your familiarity with the codebase increases, you might want to triage
+incoming issues or block certain PRs that you've reviewed. You could escalate
+your role to Project Collaborator. Want to me more involved? You can apply to be
+a Project Core Committer, or even a Project Maintainer.
+
+#### "No, I can't code..."
+
+*That's cool too!* We realise that open source communities are never just about
+the code. If you're passionate about growing the CC community by enabling new
+contributors to get started or by spreading the word, you can apply for one of
+the Community Building roles. Like the Project roles, there are a couple of
+levels to choose from.
+
+Community builders have a whole different set of responsibilities and privileges
+specifically catered to the unique task of cultivating a healthy community
+around our many open source projects.
+
+So if you want to be lightly involved with onboarding new contributors to the
+repositories and the workflows, you could start off as a Community Contributor.
+This is a fantastic role to help new contributors get a headstart in their
+journey with FOSS.
+
+As your familiarity with the community increases, you might want to suggest
+tweets for our Twitter account, or pariticipate in long-term community building
+tasks from Asana. You could escalate your role to Community Collaborator. Want
+to me more involved? You can even apply to be a Community Maintainer.
+
+### What's next?
+
+<p style="text-align:center;">
+  <img
+    alt="Gromit laying the tracks ahead of the toy train he is riding on"
+    title="We'll just figure things out as we go!"
+    src="gromit.gif"/><br/>
+  <small>
+    We'll just figure things out as we go!
+  </small>
+</p>
+
+The Community Team is a fairly novel idea for us and we're still tweaking things
+along the way. For example, we recently merged of two Project roles, namely
+Project Member and Project Collaborator, when we realised they weren't so
+different. As we internalise these roles more and more, we'll find more scope
+for improvement and we'll continue to refine these roles over time.
+
+We're excited about the Community Team. If you're interested in joining us on
+this ride, it's really easy to [get started][communityteam].
+
+[communityteam]:/community/community-team/
+
+<small>*We do not guarantee that you will be accepted if you apply for an
+internship!</small>

content/blog/entries/legal-database-features/lighthouse-after.png

@@ -4,7 +4,7 @@ title: Open Source at CC
 ---
 body:
 
-**[Creative Commons](https://creativecommons.org/)** has been building free software for over a decade to support our mission of maximizing digital creativity, sharing, and innovation. We work on products that, among other things, make applying CC licenses to content easier, help users find CC licensed content easily, promote and educate users about CC licenses and copyright, and connect the global CC community. Our projects come in all sizes and shapes, from several simple static websites to making the 1.6 billion+ Creative Commons works currently available on the internet [searchable](https://search.creativecommons.org/). 
+**[Creative Commons](https://creativecommons.org/)** has been building free software for over a decade to support our mission of maximizing digital creativity, sharing, and innovation. We work on products that, among other things, make applying CC licenses to content easier, help users find CC licensed content easily, promote and educate users about CC licenses and copyright, and connect the global CC community. Our projects come in all sizes and shapes, from several simple static websites to making the 1.6 billion+ Creative Commons works currently available on the internet [searchable](https://search.creativecommons.org/).
 
 ## Get Involved
 
@@ -16,7 +16,7 @@ So if you're looking to integrate CC licenses or CC licensed works into your app
     <div class="card-img-top">
       <img class="mx-auto d-block" src="/comments-solid.png" alt="Community icon"/>
     </div>
-    <div class="card-body" align="center">
+    <div class="card-body" style="text-align: center;">
       <p class="card-text text-center">Join the CC developer chat and mailing list communities to connect with other developers working with CC tools.</p>
       <a href="/community/" class="btn btn-sm btn-outline-primary">See how to join</a>
     </div>
@@ -27,7 +27,7 @@ So if you're looking to integrate CC licenses or CC licensed works into your app
     <div class="card-img-top">
       <img class="mx-auto d-block" src="/laptop-code-solid.png" alt="Code icon"/>
     </div>
-    <div class="card-body" align="center">
+    <div class="card-body" style="text-align: center;">
       <p class="card-text text-center">Fix one of our open issues or work on something new that you'd like to use. All skill levels are welcome.</p>
       <a href="/contributing-code/" class="btn btn-sm btn-outline-primary">Guidelines</a>
       <a href="https://github.com/search?q=org%3Acreativecommons+is%3Aopen+label%3A%22help+wanted%22" class="btn btn-sm btn-outline-primary">"Help Wanted" issues</a>
@@ -39,7 +39,7 @@ So if you're looking to integrate CC licenses or CC licensed works into your app
     <div class="card-img-top">
       <img class="mx-auto d-block" src="/creative-commons-remix-brands.png" alt="CC remix icon"/>
     </div>
-    <div class="card-body" align="center">
+    <div class="card-body" style="text-align: center;">
       <p class="card-text text-center">Use CC-licensed works in your application or (coming soon!) use our WordPress plugin to license your content.</p>
       <a href="https://api.creativecommons.engineering/" class="btn btn-sm btn-outline-primary">Catalog API</a>
       <a href="/contributing-code/projects/" class="btn btn-sm btn-outline-primary">All our projects</a>
@@ -51,7 +51,7 @@ So if you're looking to integrate CC licenses or CC licensed works into your app
     <div class="card-img-top">
       <img class="mx-auto d-block" src="/keyboard-solid.png" alt="Keyboard icon icon"/>
     </div>
-    <div class="card-body" align="center">
+    <div class="card-body" style="text-align: center;">
       <p class="card-text text-center">If you've worked on software that uses CC licenses or tools, tell the community about it on <a href="/blog/">our tech blog</a>.</p>
       <a href="/community/write-a-blog-post/" class="btn btn-sm btn-outline-primary">Write a blog post</a>
     </div>
@@ -62,7 +62,7 @@ So if you're looking to integrate CC licenses or CC licensed works into your app
     <div class="card-img-top">
       <img class="mx-auto d-block" src="/vials-solid.png" alt="Test tubes icon"/>
     </div>
-    <div class="card-body" align="center">
+    <div class="card-body" style="text-align: center;">
       <p class="card-text text-center">Participate in one of our regular usability tests for CC tools that we're actively working on (we'll give you a gift card!)</p>
       <a href="/contributing-code/usability/" class="btn btn-sm btn-outline-primary">Learn more</a>
       <a href="https://github.com/creativecommons/creativecommons.org/issues/new/choose" class="btn btn-sm btn-outline-primary">File an issue</a>
@@ -74,7 +74,7 @@ So if you're looking to integrate CC licenses or CC licensed works into your app
     <div class="card-img-top">
       <img class="mx-auto d-block" src="/language-solid.png" alt="Translation icon"/>
     </div>
-    <div class="card-body" align="center">
+    <div class="card-body" style="text-align: center;">
       <p class="card-text text-center">Translate our content into your language. Contact us if you'd like to write code to make this process easier for new tools.</p>
       <a href="https://wiki.creativecommons.org/wiki/Translate" class="btn btn-sm btn-outline-primary">Translation information</a>
     </div>
@@ -85,7 +85,7 @@ So if you're looking to integrate CC licenses or CC licensed works into your app
     <div class="card-img-top">
       <img class="mx-auto d-block" src="/pencil-ruler-solid.png" alt="Pencil and ruler icon"/>
     </div>
-    <div class="card-body" align="center">
+    <div class="card-body" style="text-align: center;">
       <p class="card-text text-center">Contribute to our brand new set of standard UI components and help us apply it to all existing projects.</p>
       <a href="https://github.com/creativecommons/cc-vocabulary" class="btn btn-sm btn-outline-primary">CC Vocabulary</a>
     </div>