Yes, that's a good place to start. Once you have git installed and link
it up to your github account, you can follow the same "Contribute" steps
that are on the README of the anti-harassment policy:
1.) Fork the codebase e.g. to https://github.com/your-username/issue-manager
2.) Clone your fork locally (git clone
g...@github.com:your-username/issue-manager.git my-antiharassment-policy)
3.) Create a branch to hold your changes (git checkout -b my-changes)
4.) Commit the changes you've made (git commit -am "Some descriptive
text around what you've added")
5.) Push your branch to github (git push origin my-changes)
Once you do that, we can test it out for you before merging.
-Shaun
On 12/4/12 5:45 PM, Jonathan Rochkind wrote:
I'd check out the links under "Bootcamp" here:
https://help.github.com/
On 12/4/2012 5:18 PM, Mark Pernotto wrote:
As I'm clearly not well-versed in the goings-on of GitHub, I've
'forked' a response, but am not sure it worked correctly.
I've zipped up and sent updates to Tom. If anyone could point me in
the direction of a good GitHub tutorial (for contributing to projects
such as these - the 'creating an account' part I think I have down),
I'd appreciate it.
Thanks,
Mark
On Tue, Dec 4, 2012 at 1:43 PM, Tom Keays <tomke...@gmail.com> wrote:
Let's have mine be the canonical version for now. It will be too
confusing
to have two versions that don't have an explicit fork relationship.
https://github.com/tomkeays/issue-manager
Tom
On Tue, Dec 4, 2012 at 1:56 PM, Chad Nelson <chadbnel...@gmail.com>
wrote:
Beat me by one minute Tom!
And here it is in code4lib github
https://github.com/code4lib/IssueManager
On Tue, Dec 4, 2012 at 1:47 PM, Tom Keays <tomke...@gmail.com> wrote:
On Tue, Dec 4, 2012 at 1:01 PM, Shaun Ellis <sha...@princeton.edu>
wrote:
You can upload it to your account and then someone with admin
rights to
Code4Lib can fork it if they think our Code4Lib Journal custom code
should
be a repo there. Doesn't really matter if they do actually. I think
for
debugging, it's best to point folks to the actual code the journal is
running, which was forked from the official one on the Codex, right?
It was written for the Journal and originally kept in a Google Code
repo
(this is before Github became the de facto). After the author left the
journal, he did a couple of updates which he uploaded to the WP Codex,
but
nothing for a few years.
Anyway, here it is:
https://github.com/tomkeays/issue-manager
--
Shaun D. Ellis
Digital Library Interface Developer
Firestone Library, Princeton University
voice: 609.258.1698 | sha...@princeton.edu
