You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/community/contents.lr
+72-88
Original file line number
Diff line number
Diff line change
@@ -4,110 +4,94 @@ _template: page-with-toc.html
4
4
---
5
5
title: Join the CC Developer Community
6
6
---
7
-
description: Join our Slack or mailing list communities to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time engineering staff. You can also keep up with us on the <ahref="/blog">CC Open Source Blog</a> or via <ahref="https://twitter.com/cc_opensource">Twitter</a>.
7
+
description: Join our Slack or mailing list communities to meet other
8
+
developers interested in Creative Commons, get feedback on your projects, and
9
+
talk with CC's full-time engineering staff. You can also keep up with us on the
**CC Developers**: For general technical discussion open to all members. Join [on Google Groups](https://groups.google.com/a/creativecommons.org/forum/#!forum/cc-developers) or by sending an email to `cc-developers+subscribe@creativecommons.org`.
18
+
**CC Developers**: For general technical discussion open to all members. Join
19
+
[on Google Groups][group-cc-developers] or by sending an email to
20
+
`cc-developers+subscribe@creativecommons.org`.
21
+
22
+
**CC Usability Announcements**: Announcement-only list for users to sign up for
23
+
usability testing. Join [on Google Groups][group-usability-announce] or by
24
+
sending an email to `usability-announce+subscribe@creativecommons.org`.
**CC Usability Announcements**: Announcement-only list for users to sign up for usability testing. Join [on Google Groups](https://groups.google.com/a/creativecommons.org/forum/#!forum/usability-announce) or by sending an email to `usability-announce+subscribe@creativecommons.org`.
16
29
17
30
## Slack
18
-
Creative Commons has a large Slack community with sub-communities for tech/developers (of course), the [CC Global Network](https://network.creativecommons.org/), specific countries, open education, GLAM, and more. It is open to the public and you can [sign up here](http://slack-signup.creativecommons.org/). If you're not familiar with Slack, please read ["Getting Started" on Slack's usage guide](https://get.slack.help/hc/en-us/categories/360000049043). Information on joining a specific channel is on ["Join a channel"](https://get.slack.help/hc/en-us/articles/205239967-Join-a-channel).
31
+
32
+
Creative Commons has a large Slack community with sub-communities for
33
+
tech/developers (of course), the [CC Global Network][network], specific
34
+
countries, open education, GLAM, and more. It is open to the public and you can
35
+
[sign up here][slack-signup]. If you're not familiar with Slack, please read
36
+
["Getting Started" on Slack's usage guide][slack-usage]. Information on joining
37
+
a specific channel is on ["Join a channel"][slack-join-help].
19
38
20
39
Once you join, please introduce yourself in the `#cc-developers` channel.
The channels most relevant to CC's developer community are:
23
47
24
-
<divclass="table-container">
25
-
<tableclass="table is-bordered is-striped">
26
-
<thead>
27
-
<tr>
28
-
<th>Channel</th>
29
-
<th>Purpose</th>
30
-
</tr>
31
-
</thead>
32
-
<tr>
33
-
<td><code>#cc-dev-browser-extension</code></td>
34
-
<td>Discussion related to the <a href="https://github.com/creativecommons/ccsearch-browser-extension">Search browser extension.</a></td>
35
-
</tr>
36
-
<tr>
37
-
<td><code>#cc-dev-catalog</code></td>
38
-
<td>Discussion related to the <a href="https://api.creativecommons.engineering/">CC Catalog API</a> and <a href="https://github.com/creativecommons/cccatalog">Catalog.</a></td>
<td>Discussion related to the <a href="https://github.com/creativecommons/mp">CC Platform Toolkit</a> Outreachy project.</td>
75
-
</tr>
76
-
<tr>
77
-
<td><code>#cc-search</code></td>
78
-
<td>Discussion related to the <a href="https://search.creativecommons.org/">CC Search.</a></td>
79
-
</tr>
80
-
<tr>
81
-
<td><code>#cc-usability</code></td>
82
-
<td>General usability discussions, seeking feedback on new releases of CC products from the community.</td>
83
-
</tr>
84
-
<tr>
85
-
<td><code>#cc-dev-licenses</code></td>
86
-
<td>Discussion related to the <a href="https://github.com/creativecommons/cc-licenses">CC license infrastructure overhaul project.</a></td>
87
-
</tr>
88
-
<tr>
89
-
<td><code>#cc-dev-icmi</code></td>
90
-
<td>Discussion related to the Image Clustering and Metric Inference project.</a></td>
91
-
</tr>
92
-
<tr>
93
-
<td><code>#cc-dev-ipa</code></td>
94
-
<td>Discussion related to the Image Popularity and Authority project.</a></td>
95
-
</tr>
96
-
<tr>
97
-
<td><code>#cc-dev-lcga</code></td>
98
-
<td>Discussion related to the Linked Commons Graph Analysis project.</a></td>
99
-
</tr>
100
-
</table>
101
-
</div>
48
+
| Channel | Purpose |
49
+
| ------- | ------- |
50
+
|`#cc-dev-browser-extension`| Discussion related to the [creativecommons/ccsearch-browser-extension][ccsearch-browser-extension] project. |
51
+
|`#cc-dev-internships`|**Discussion related to GSoC, GSoD, Outreachy, and other internships.**|
52
+
|`#cc-dev-legaldb`| Discussion related to the [creativecommons/legaldb][legaldb] project. |
53
+
|`#cc-dev-license-chooser`| Discussion related to the [creativecommons/cc-chooser][cc-chooser] project (new CC license chooser). |
54
+
|`#cc-dev-licenses`| Discussion related to the [creativecommons/cc-licenses][cc-licenses] project (CC Licenses formatting and translation). |
55
+
|`#cc-dev-linkchecker`| Discussion related to the [creativecommons/cc-link-checker][cc-link-checker] project. |
56
+
|`#cc-dev-platform-toolkit`| Discussion related to the [creativecommons/mp][mp] project (CC Platform Toolkit). |
57
+
|`#cc-dev-vocabulary`| Discussion related to the [creativecommons/cc-vocabulary][cc-vocabulary] project. |
58
+
|`#cc-dev-wordpress`| Discussion related to the [creativecommons/wp-plugin-creativecommons][wp-plugin-creativecommons] project (creativecommons WordPress plugin). |
59
+
|`#cc-developers`|**General technical discussion, new tech blog posts.**|
60
+
|`#cc-usability`| General usability discussions, seeking feedback on new releases of CC products from the community. |
- You will automatically join the `#general` and `#cc-announcements` channels when you sign in to Slack for the first time.
73
+
74
+
- You will automatically join the `#general` and `#cc-announcements` channels
75
+
when you sign in to Slack for the first time.
105
76
-`#general` is for general purpose discussions relevant to CC.
106
-
-`#cc-announcements` is reserved for important announcements from CC staff.
107
-
- For more information about how Creative Commons uses Slack, see [the Slack page on the CC public wiki](https://wiki.creativecommons.org/wiki/Slack).
108
-
- If you're looking to talk to someone on CC's full-time engineering staff, you're most likely to find us on Slack between 11:00 and 23:00 UTC on weekdays.
77
+
-`#cc-announcements` is reserved for important announcements from CC
78
+
staff.
79
+
- For more information about how Creative Commons uses Slack, see [the Slack
80
+
page on the CC public wiki][wiki-slack].
81
+
- If you're looking to talk to someone on CC's full-time engineering staff,
82
+
you're most likely to find us on Slack between 11:00 and 23:00 UTC on
We don't use IRC much, but if you'd like, you can join the `#creativecommons-dev` channel on [Freenode](https://freenode.net/). This channel is mirrored to the `#cc-developers` channel on Slack so that messages posted on Slack show up on IRC and vice-versa.
112
89
113
-
If you're not familiar with IRC, [here's a good guide to getting started](https://www.wikihow.com/Get-Started-with-IRC-%28Internet-Relay-Chat%29). You can also join using the [Freenode webchat](https://webchat.freenode.net/).
90
+
We don't use IRC much, but if you'd like, you can join the
91
+
`#creativecommons-dev` channel on [Freenode](https://freenode.net/). This
92
+
channel is mirrored to the `#cc-developers` channel on Slack so that messages
93
+
posted on Slack show up on IRC and vice-versa.
94
+
95
+
If you're not familiar with IRC, [here's a good guide to getting
0 commit comments