LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  February 2013

CODE4LIB February 2013

Subject:

Re: GitHub Myths (was thanks and poetry)

From:

Tom Johnson <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 20 Feb 2013 11:04:02 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (214 lines)

> But while I get the argument for utility, there does seem to be
barrier-to-entry there for someone just wanting to submit a poem.

The original suggestion wasn't about utility, but about modes of writing.
Git repositories would make for poems which are easily shared, copied,
"forked", and merged back together. I'm interested in the relationship this
has to the idea of an "oral tradition". Especially given that a "git
poetry" tradition would record its own history in the medium.

I agree that wordpress is much more accessible. It seems obvious to me that
we could post poems where we see fit and aggregate them. Written and oral
is even more accessible than that. It seems obvious to me that we could
write down and/or recite poems, pass them around, and commit them to
memory. I think we should do all these things--and maybe play around with
git, too.

For me, the important take away from this discussion is that git art
shouldn't be the dominant form of expression or the raison d'etre for the
'nerd poetry' idea.

As an aside: I share the concerns about GitHub. I resisted joining for
years because of exactly this issue. If Facebook is a man-in-the-middle
exploit on social interaction, then surely GitHub is the same on Free
Software development. I thought the FOSS community would be better served
if we all put up our git repositories in our own ways, and tried to build
tools for collaboration. As it turns out, GitHub has done wonders for code
sharing and collaborative development and the company has been good to us,
which is why I'm there now. I still worry about ways the our platform
dependence could go badly. Luckily, the risk is mitigated by gits
distributed and portable nature.

- Tom


On Wed, Feb 20, 2013 at 10:20 AM, Jason Stirnaman <[log in to unmask]>wrote:

> Another option might be to set it up like the Planet. Where individuals
> just post their poetry to their own blogs, Tumblrs, etc., tag them, and
> have $PLANET_NERD_POETS aggregate them.
>
> Git and Github are great. But while I get the argument for utility, there
> does seem to be barrier-to-entry there for someone just wanting to submit a
> poem.
>
> Jason
>
> Jason Stirnaman
> Digital Projects Librarian
> A.R. Dykes Library
> University of Kansas Medical Center
> 913-588-7319
>
> ________________________________________
> From: Code for Libraries [[log in to unmask]] on behalf of Karen
> Coyle [[log in to unmask]]
> Sent: Wednesday, February 20, 2013 10:42 AM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] GitHub Myths (was thanks and poetry)
>
> Shaun, you cannot decide whether github is a barrier to entry FOR ME (or
> anyone else), any more than you can decide whether or not my foot hurts.
> I'm telling you github is NOT what I want to use. Period.
>
> I'm actually thinking that a blog format would be nice. It could be
> pretty (poetry and beauty go together). Poems tend to be short, so
> they'd make a nice blog post. They could appear in the Planet blog roll.
> They could be coded by author and topic. There could be comments! Even
> poems as comments! The only down-side is managing users. Anyone have
> ideas on that?
>
> kc
>
>
> On 2/20/13 8:20 AM, Shaun Ellis wrote:
> > > (As a general rule, for every programmer who prefers tool A, and says
> > > that everybody should use it, there’s a programmer who disparages tool
> > > A, and advocates tool B. So take what we say with a grain of salt!)
> >
> > It doesn't matter what tools you use, as long as you and your team are
> > able to participate easily, if you want to.  But if you want to
> > attract  contributions from a given development community, then
> > choices should be balanced between the preferences of that community
> > and what best serve the project.
> >
> > From what I've been hearing, I think there is a lot of confusion about
> > GitHub.  Heck, I am constantly learning about new GitHub features,
> > APIs, and best practices myself. But I find it to be an incredibly
> > powerful platform for moving open source, distributed software
> > development forward.  I am not telling anyone to use GitHub if they
> > don't want to, but I want to dispel a few myths I've heard recently:
> >
> > ------------
> >
> > * Myth #1 : GitHub creates a barrier to entry.
> > * "To contribute to a project on GitHub, you need to use the
> > command-line. It's not for non-coders."
> >
> > GitHub != git.  While GitHub was initially built for publishing and
> > sharing code via integration with git, all GitHub functionality can be
> > performed directly through the web gui.  In fact, GitHub can even be
> > used as your sole coding environment. There are other tools in the
> > "eco-system" that allow non-coders to contribute documentation, issue
> > reporting, and more to a project.
> >
> > ------------
> >
> > * Myth #2 : GitHub is for sharing/publishing code.
> > * "I would be fun to have a wiki for more durable poetry (github
> > unfortunately would be a barrier to many)."
> >
> > GitHub can be used to collaborate on and publish other types of
> > content as well.  For example, GitHub has a great wiki component* (as
> > well as a website component).  In a number of ways, has less of a
> > "barrier to entry" than our Code4Lib wiki.
> >
> > While the path of least resistance requires a "repository" to have a
> > wiki, public repos cost nothing and can consist of a simple "README"
> > file.  The wiki can be locked down to a team, or it can be writable by
> > anyone with a github account.  You don't need to do anything via
> > command-line, don't need to understand "git-flow", and you don't even
> > need to learn wiki markup to write content. All you need is an account
> > and something to say, just like any wiki. Log in, go to the
> > anti-harassment policy wiki, and see for yourself:
> > https://github.com/code4lib/antiharassment-policy/wiki
> >
> > * The github wiki even has an API (via Gollum) that you can use to
> > retrieve raw or formatted wiki content, write new content, and collect
> > various meta data about the wiki as a whole:
> > https://github.com/code4lib/antiharassment-policy/wiki/_access
> >
> > ------------
> >
> > * Myth #3 : GitHub is person-centric.
> > > "(And as a further aside, there’s plenty to dislike about github as
> > > well, from it’s person-centric view of projects (rather than
> > > team-centric)..."
> >
> > Untrue. GitHub is very team centered when using organizational
> > accounts, which formalize authorization controls for projects, among
> > other things: https://github.com/blog/674-introducing-organizations
> >
> > ------------
> >
> > * Myth #4 : GitHub is monopolizing open source software development.
> > > "... to its unfortunate centralizing of so much free/open
> > > source software on one platform.)"
> >
> > Convergence is not always a bad thing. GitHub provides a great, free
> > service with lots of helpful collaboration tools beyond version
> > control.  It's natural that people would flock there, despite having
> > lots of other options.
> >
> > ------------
> >
> > -Shaun
> >
> >
> >
> >
> >
> >
> >
> > On 2/19/13 5:35 PM, Erik Hetzner wrote:
> >> At Sat, 16 Feb 2013 06:42:04 -0800,
> >> Karen Coyle wrote:
> >>>
> >>> gitHub may have excellent startup documentation, but that startup
> >>> documentation describes git in programming terms mainly using *nx
> >>> commands. If you have never had to use a version control system
> >>> (e.g. if
> >>> you do not write code, especially in a shared environment), "clone"
> >>> "push" "pull" are very poorly described. The documentation is all in
> >>> terms of *nx commands. Honestly, anything where this is in the
> >>> documentation:
> >>>
> >>> On Windows systems, Git looks for the |.gitconfig| file in the |$HOME|
> >>> directory (|%USERPROFILE%| in Windows’ environment), which is
> >>> |C:\Documents and Settings\$USER| or |C:\Users\$USER| for most people,
> >>> depending on version (|$USER| is |%USERNAME%| in Windows’ environment).
> >>>
> >>> is not going to work for anyone who doesn't work in Windows at the
> >>> command line.
> >>>
> >>> No, git is NOT for non-coders.
> >>
> >> For what it’s worth, this programmer finds git’s interface pretty
> >> terrible. I prefer mercurial (hg), but I don’t know if it’s any better
> >> for people who aren’t familar with a command line.
> >>
> >>    http://mercurial.selenic.com/guide/
> >>
> >> (As a general rule, for every programmer who prefers tool A, and says
> >> that everybody should use it, there’s a programmer who disparages tool
> >> A, and advocates tool B. So take what we say with a grain of salt!)
> >>
> >> (And as a further aside, there’s plenty to dislike about github as
> >> well, from it’s person-centric view of projects (rather than
> >> team-centric) to its unfortunate centralizing of so much free/open
> >> source software on one platform.)
> >>
> >> best, Erik
> >>
> >>
> >>
> >> Sent from my free software system <http://fsf.org/>.
> >>
>
> --
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> ph: 1-510-540-7596
> m: 1-510-435-8234
> skype: kcoylenet
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2024
September 2024
August 2024
July 2024
June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager