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
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,7 @@
1
1
_model: page
2
2
---
3
+
_template: page-with-toc.html
4
+
---
3
5
title: Join the CC Developer Community
4
6
---
5
7
body:
@@ -15,7 +17,7 @@ For information regarding joining a channel on Slack, [look here](https://get.sl
15
17
16
18
Note that channels like `#general` on Slack consist of a fair amount of users. While it is a channel for general-purpose discussions, please take into consideration that a post on such a channel will notify thousands of users. 😄
17
19
18
-
If you're looking to talk to someone on CC's tech team, we are all in the Americas and someone is usually around on Slack between 11:00 and 23:00 UTC on weekdays.
20
+
If you're looking to talk to someone on CC's tech team, we are all in the Americas and someone is usually around on Slack between 11:00 and 23:00 UTC on weekdays. See the [Resources](#resources) section below for best practices for asking technical questions.
19
21
20
22
## Mailing List
21
23
@@ -27,3 +29,7 @@ The archives of our [previous mailing list are here](https://lists.ibiblio.org/p
27
29
We have two channels on [Freenode](https://freenode.net/).
28
30
-`#creativecommons-dev` – for technical discussion
29
31
-`#creativecommons` – for general discussion (this is mirrored to the `#general` channel on Slack, use only if you want to reach 4000+ people)
32
+
33
+
## Resources
34
+
35
+
*[Getting Answers](https://www.mikeash.com/getting_answers.html): A guide to asking good technical questions.
0 commit comments