| /** | |
| * A little script to play the ACSII Star Wars, but with a hidden | |
| * cursor, since over telnet the cursor remains visible | |
| */ | |
| var net = require('net') | |
| var cursor = require('ansi')(process.stdout) | |
| // connect to Star Wars server |
| JSON._dateReviver = function (k,v) { | |
| if (v.length !== 24 || typeof v !== 'string') return v | |
| try {return new Date(v)} | |
| catch(e) {return v} | |
| } | |
| JSON.parseWithDates = function (obj) { | |
| return JSON.parse(obj, JSON._dateReviver); | |
| } |
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 21 Sep 2022 till Thu, 21 Sep 2023.
Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:
githubUsers
.filter(user => user.followers > 1000)
This document lays out some baseline expectations between conference speakers and conference presenters. The general goal is to maximize the value the conference provides to its attendees and community and to let speakers know what they might reasonably expect from a conference.
We believe that all speakers should reasonably expect these things, not just speakers who are known to draw large crowds, because no one is a rockstar but more people should have the chance to be one. We believe that conferences are better -- and, dare we say, more diverse -- when the people speaking are not just the people who can afford to get themselves there, either because their company paid or they foot the bill themselves. Basically, this isn't a rock show rider, it's some ideas that should help get the voices of lesser known folks heard.
These expectations should serve as a starting point for discussion between speaker and organizer. They are not a list of demands; they are a list of rea
| for i in $HOME/local/*; do | |
| [ -d $i/bin ] && PATH="${i}/bin:${PATH}" | |
| [ -d $i/sbin ] && PATH="${i}/sbin:${PATH}" | |
| [ -d $i/include ] && CPATH="${i}/include:${CPATH}" | |
| [ -d $i/lib ] && LD_LIBRARY_PATH="${i}/lib:${LD_LIBRARY_PATH}" | |
| [ -d $i/lib ] && LD_RUN_PATH="${i}/lib:${LD_RUN_PATH}" | |
| # uncomment the following if you use macintosh | |
| # [ -d $i/lib ] && DYLD_LIBRARY_PATH="${i}/lib:${DYLD_LIBRARY_PATH}" | |
| [ -d $i/lib/pkgconfig ] && PKG_CONFIG_PATH="${i}/lib/pkgconfig:${PKG_CONFIG_PATH}" | |
| [ -d $i/share/man ] && MANPATH="${i}/share/man:${MANPATH}" |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <script type="text/javascript" src="http://mbostock.github.com/d3/d3.js?1.27.1"></script> | |
| </head> | |
| <body> | |
| <script type="text/javascript"> | |
| var w = 960, | |
| h = 500; |
| // Short module explanation // Something to gather my thoughts | |
| // // I think this looks cool. | |
| // | |
| module.exports = the_exported_function // Modules are a function. Always. | |
| // | |
| module.exports.extra = extra // Additional API entry points if | |
| module.exports.other = other // desired. | |
| // | |
| var util = require('util') // Other packages from npm or core | |
| var assert = require('assert') // No comma-first due to lots of |
Full version out! http://zachbruggeman.me/github-for-cats/
Because cats just wanna have forks.
If you’re a cat, you probably haven’t heard of GitHub. Maybe your human companion has, but they don’t really know how to explain it to you. (Which, as a cat, is extremely frustrating.) GitHub is a website that allows content creators, whether it be via programming, blogging, or issue-reporting, to collaborate together and to learn from each other. It’s powered by a “distributed version control system” called git. A “distributed version control system” sounds pretty complicated, but it really isn’t. What it really means is that lets you, a cat, manage all of the stuff you have made (like maybe some JavaScript?) in one place, and be able to go back in time to see what you did before. It also lets other cats (or maybe humans) see what you’ve done, and help you out with it. This guide will get you introduced to the world of git and GitHub, and it might even
