Improve messaging around CC Open Source

[kgodey]

CC Open Source is currently linked at https://network.creativecommons.org/get-involved/writing-code/. I'd like a couple of changes

• The "Creative Commons open source" button does not link to anything. It should link to https://opensource.creativecommons.org/.
• Please capitalize "Open Source" so that it's "Creative Commons Open Source".

• The text currently says:

  Creative Commons has been building free software for over a decade to support our mission of maximizing digital creativity, sharing, and innovation. Our projects come in all sizes and shapes, from simple static websites to building fast and relevant search interfaces to the 1.6 billion+ Creative Commons works currently available on the internet. Our engineering team is fairly small and spread thin, so we’re really appreciative of volunteers who help us build or test our software.

  Could we change it to:

  Interested in integrating CC tools into your application or helping us build our open source software?

• I would like to direct users to CC Open Source even if they can't code. For example, they could contribute design or just use our products and give us feedback. I don't have a specific suggestion, whatever you think works.

[Atanda1]

I'll like to work on this

[kgodey]

This is not open to community contribution right now.

[valerio-bozzolan]

As already reported, please fix the "Creative Commons open source" button, since it does not link to anything.

https://network.creativecommons.org/get-involved/writing-code/

Probably that button should have this link:

https://opensource.creativecommons.org/

It seems not possible for me to help in any way, since I have not WordPress credentials and/or this part does not appear in the available source code.

[xolotl]

Thanks for your nudge @valerio-bozzolan!

The button is now properly linked and text on the page is updated to say:

"Creative Commons builds free and open software to support our mission to maximize digital creativity, sharing, and innovation. Our projects come in all sizes and shapes to help people add to and engage with the 2.5 billion+ Creative Commons works on the internet. The CC technology team is fairly small and spread thin, so we really appreciate volunteers who help us build, test, and document open software.

Interested in integrating CC tools into your application or helping us build free and open software?"

[valerio-bozzolan]

Thank you a lot @xolotl it seems OK for me! I just also suggest to write "Free" instead of "free" (it's a widely used trick to stress the fact that we like software Freedom, and it's not related to produce proprietary freeware). Thank you so much

• [ ] suggestion: "Free" instead of "free"

[valerio-bozzolan]

Also I can suggest to improve the link removing the target="_blank" HTML attribute, so the link opens in the same tab, just like the other links.

I have not a strong opinion on this small improvement but the destination is not an extra page (like "see privacy info" etc.) but it's the natural navigation flow, suggested from that landing page, so I think it's more natural to keep the link as-is (without opening in new window).

Sorry ahah :D thank you!

Further interesting info:

https://stackoverflow.com/questions/946248/when-should-you-use-target-blank-on-your-links

https://css-tricks.com/use-target_blank/

• [ ] suggestion: normal link (without target=_blank")

[xolotl]

@valerio-bozzolan Thank you for the additional suggestions! I have set the button link to not open in a new tab/window.

It may be a small thing, but the capitalization of "free" (as in libre, not gratis) is not currently covered in the CC style guide. When something like that is not covered, one thing we sometimes do is see how it is handled by sister organizations, for example Wikipedia or even the Free Software Foundation. In my research, neither capitalizes "free" when it is not the beginning of a sentence, or covered by other capitalization practices.

While CC could capitalize like "Free" or add "libre" to clarify for readers, that practice is followed systematically nowhere else in all CC websites or publications and so to do it here on this single page would be inconsistent. I don't think there's enough motivation to undertake the very large project it would be to change practices across all CC publications.