CommunityData:Meetup July 2017/Infrastructure: Difference between revisions

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.

@@ Line 1: / Line 1: @@
-== Outline ==
+== Zotero ==
-=== Zotero ===
-Checkoff list before we start:
+Instructions are online at [[CommunityData:Zotero]]
-* Everybody upgrade to Zotero 5.0. You will need to download this from https://www.zotero.org because it was released recently and its not in the distributions yet. It's important to be running the new version. This will break support for BetterBibLaTeX but is also fixes most of the bugs that required this in the first place.
+== Git (migration to gitolite from wikiresearch) ==
-* Everybody make sure you have joined and a member of the [https://www.zotero.org/groups/163394/community_data_science_collective Community Data Science Collective Zotero repository].
-Things that everybody should know:
+Details on setting up Gitolite are already pretty clearly documented over at [[CommunityData:Git]].
-* In Zotero, folders are not like traditional folders. They are like tags. Do not add things if they are already there!
+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.
-* Holding down <tt>Alt</tt> is extremely useful! It will show you which folders the selected item is in!
-The process to add something cleanly is complicated but should always include the following steps:
-# Check to see if it's in the CDSC shared folder by clicking on the top level of the shared group and searching. If it is already there, just drag it into your new subfolder for your project. If it's not, click back on your sub-folder and add it.
-# Once you've added, change the title to sentence case. You can do this by: (a) ''Right clicking on Title → Transform Text → Sentence Case'' (b) you will then need to capitalize any proper nouns (e.g., Scratch, Wikipedia) as well as anything immediately following a ":". This is important because software like BibTeX/BibLaTeX can change from "Sentence case" to "Title Case" automatically, but not the other way around. APA 6 requires sentence case.
-# Ensure that there's a DOI for your entry if it's necessary. Some publishers and conferences (like AAAI publications which publishes ICWSM) do not have DOIs. If your publication does not a DOI, it needs to have a URL because APA 6 requires one or the other.
-# Edit & clean the Publisher field. According to [http://blog.apastyle.org/apastyle/2010/01/the-generic-reference-where.html APA 6 style] we should drop common words like "Press," "Publisher," "Inc." as well as first names (i.e., just Wiley, not John Wiley Inc.)
-# Edit & clean the Place field. [http://blog.apastyle.org/apastyle/2010/01/the-generic-reference-where.html APA 6 style] requires "City, State" within the USA and "City, Country" outside. So, it's "New York, New York" for the ACM and "Cambridge, UK" for University of Cambridge Press.
-# Remove anything in the "Extra" field unless it's something you want to be printed every time. Sometimes things like "ⓒ JSTOR" sneaks in.
-# Make sure that there's a PDF attached and then rename the PDF by: ''Right click on PDF → Rename File from Parent Metadata''
-== Ideas of things to cover in an infrastructure and hygiene session ==
+If you do <code>git remote -v</code> you should all see something like this:
-* gitolite
+ origin git@github.com:aaronshaw/wikiresearch.git (fetch)
-* mailing list
+ origin git@github.com:aaronshaw/wikiresearch.git (push)
-* IRC
-* Zotero(!!)
+The first word might be different but the important thing to take note of is that word (i.e., “origin”).
-* Migration away from the wikiresearch hosting on Github
-* Planning documents (creating a shared repository?)
+First you need to add the new repository and pull down objects like:
-* Wiki organization
-* Move RCommunityData to it's own git repository
+ 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 [[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:
+* [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.