CommunityData:Meetup July 2017/Infrastructure: Difference between revisions
From CommunityData
(→Zotero) |
|||
| (14 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
== Zotero == | |||
Instructions are online at [[CommunityData:Zotero]] | |||
== Git (migration to gitolite from wikiresearch) == | |||
Details on setting up Gitolite are already pretty clearly documented over at [[CommunityData:Git]]. | Details on setting up Gitolite are already pretty clearly documented over at [[CommunityData:Git]]. | ||
| Line 61: | Line 33: | ||
git push --all origin | git push --all origin | ||
=== | == Planning documents repository == | ||
We'll create one on the community data server. Nearly everyone should clone it and contribute once we do! There's also one [[CommunityData:Planning_document|here]] | |||
== Move RCommunityData to its own repository == | |||
This needs to happen. It's another one that nearly everyone should clone once it exists. | |||
== | == Communication channels == | ||
=== Internal === | |||
Since we're a distributed organization, it's pretty important to keep track of the ways/media we use to communicate and how they get used. Here's a pretty current list: | Since we're a distributed organization, it's pretty important to keep track of the ways/media we use to communicate and how they get used. Here's a pretty current list: | ||
You could probably add jit.si to this list and include our bi-weekly meetings. Anyhow, the point is that each of these plays an important role already and we should discuss whether/how they're working. | * [https://wiki.communitydata.cc/CommunityData:Email email lists] (collective, collective-''university'') — announcements, event coordination | ||
* [https://wiki.communitydata.cc/CommunityData:Resources#Chat_on_IRC IRC] — ongoing water cooler; sharing random stuff; ad-hoc group/pair conversations | |||
* wiki — archive of shared resources; asynchronous project coordination | |||
You could probably add jit.si to this list and include our bi-weekly meetings. Anyhow, the point is that each of these plays an important role already and we should discuss whether/how they're working. In particular, Aaron and Mako want to make sure that our internal communication channels are accessible and inclusive for all group members. | |||
=== External === | |||
We also communicate externally with a few channels: | |||
* | * [https://blog.communitydata.cc/ blog.communitydata.cc] | ||
* | * [https://twitter.com/comdatasci @comdatasci on Twitter] — you all should have access to this on Twitter. | ||
Latest revision as of 16:36, 25 July 2017
Zotero[edit]
Instructions are online at CommunityData:Zotero
Git (migration to gitolite from wikiresearch)[edit]
Details on setting up Gitolite are already pretty clearly documented over at CommunityData:Git.
The rest of this section covers migration of the wikiresearch repository off of Github. We'll be doing this at the session and disable/deleting the old repository then.
If you do git remote -v you should all see something like this:
origin git@github.com:aaronshaw/wikiresearch.git (fetch) origin git@github.com:aaronshaw/wikiresearch.git (push)
The first word might be different but the important thing to take note of is that word (i.e., “origin”).
First you need to add the new repository and pull down objects like:
git remote add communitydata git@code.communitydata.cc:wikiresearch git fetch communitydata git push --set-upstream communitydata git remote remove origin git remote rename communitydata origin
Check to see if you have multiple branches:
git branch
If you do, and you want to push them all, you can do that with:
git push --all origin
Planning documents repository[edit]
We'll create one on the community data server. Nearly everyone should clone it and contribute once we do! There's also one here
Move RCommunityData to its own repository[edit]
This needs to happen. It's another one that nearly everyone should clone once it exists.
Communication channels[edit]
Internal[edit]
Since we're a distributed organization, it's pretty important to keep track of the ways/media we use to communicate and how they get used. Here's a pretty current list:
- email lists (collective, collective-university) — announcements, event coordination
- IRC — ongoing water cooler; sharing random stuff; ad-hoc group/pair conversations
- wiki — archive of shared resources; asynchronous project coordination
You could probably add jit.si to this list and include our bi-weekly meetings. Anyhow, the point is that each of these plays an important role already and we should discuss whether/how they're working. In particular, Aaron and Mako want to make sure that our internal communication channels are accessible and inclusive for all group members.
External[edit]
We also communicate externally with a few channels:
- blog.communitydata.cc
- @comdatasci on Twitter — you all should have access to this on Twitter.
