CommunityData:Meetup July 2017/Infrastructure

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.

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  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
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
This needs to happen. It's another one that nearly everyone should clone once it exists.

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:


 * 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
We also communicate externally with a few channels:


 * blog.communitydata.cc
 * @comdatasci on Twitter — you all should have access to this on Twitter.