#x27;t
answer any of these questions in this thread, or on this listserv at all,
really. )
From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of MJ Ray
[m...@phonecoop.coop]
Sent: Friday, February 22, 2013 3:55 AM
To: CODE4LIB@LISTSERV.ND.EDU
S
estions in this thread, or on this listserv at all,
really. )
From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of MJ Ray
[m...@phonecoop.coop]
Sent: Friday, February 22, 2013 3:55 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] GitHub My
Shaun Ellis
> If you read my email, I don't tell anyone what to use, but simply
> attempt to clear up some fallacies. Distributed version control is new
> to many, and I want to make sure that folks are getting accurate
> information from this list.
As would I. I don't think spreading misinf
Don't you mean " I hope to see all of you there."
On Thu, Feb 21, 2013 at 2:44 PM, David Friggens wrote:
>> If you're not willing to provide even your name to make use of a free
>> service, then I dare say you are erecting your own barriers. Such is your
>> choice, of course, but I don't think ot
On Thu, Feb 21, 2013 at 2:44 PM, David Friggens wrote:
> "To all the people complaining about the Code4Lib 2014 conference
> being unwelcoming because of our new No Clothes Policy, I say you are
> wrong. We are entitled to enact our own conditions of entry, and if
> you are unwilling to front up n
> If you're not willing to provide even your name to make use of a free
> service, then I dare say you are erecting your own barriers. Such is your
> choice, of course, but I don't think others need to be compelled
> to accommodate the barriers you create for yourself.
>
> And just because the term
As far as the poetry goes, not my thing, so I don't have a comment on what
is actually used. The thread appeared to fork onto a discussion about
github use more generally. My apologies to all if it is still tightly
coupled to the poetry thing. The rest of my comments assume the more
general convers
Devon:
I don't think anyone is asking you to accommodate them in your choice of
tools or even approve of what they see as barriers. This conversation
started because of an understanding that the poetry folks *do want* to
accommodate others' needs and preferences. Taking that assumption in hand,
I
> An open tool is Internet email: I can send an email from my provider
> (ucop.edu) to yours (princeton.edu). A closed tool is github, where I
> need a github account to send you a pull request. An open tool would
> be one where I can send a pull request bitbucket to github.
> (Obviously, bitbucket
> Once again, these are not “fallacies”: they are disagreements.
When you say that "GitHub is not team-centered," it's not a
disagreement; it's simply false. If you say "I don't agree with the way
GitHub implements the concept of teams", then that is a disagreement.
You said the first, but pe
At Thu, 21 Feb 2013 10:29:28 -0500,
Shaun Ellis wrote:
>
> If you read my email, I don't tell anyone what to use, but simply
> attempt to clear up some fallacies. Distributed version control is new
> to many, and I want to make sure that folks are getting accurate
> information from this list.
Jonathan++
The more the merrier, says I. If we decide we need complete record of all
the poetry we create at some point in the future, we can deal with that
then. For right now, everybody have fun!
This is supposed to be fun, right?
On Thu, Feb 21, 2013 at 10:33 AM, Andrew Hankinson <
andrew.ha
Also, as a side note (and of interest to some) you *can* add pull requests to
your repo:
https://gist.github.com/piscisaureus/3342247
On 2013-02-21, at 10:29 AM, Shaun Ellis wrote:
> If you read my email, I don't tell anyone what to use, but simply attempt to
> clear up some fallacies. Dist
If you read my email, I don't tell anyone what to use, but simply
attempt to clear up some fallacies. Distributed version control is new
to many, and I want to make sure that folks are getting accurate
information from this list.
Unfortunately, this statement is not accurate either:
// There
If you're not willing to provide even your name to make use of a free
service, then I dare say you are erecting your own barriers. Such is your
choice, of course, but I don't think others need to be compelled
to accommodate the barriers you create for yourself.
And just because the terms of use ar
Shaun Ellis
> * Myth #1 : GitHub creates a barrier to entry.
That's a fact, not a myth. Myself, I won't give GitHub my full legal
name and I suspect there are others who won't. So, we're not welcome
there and if we lie to register, all our work would be subject to
deletion at an arbitrary futur
At Wed, 20 Feb 2013 11:50:45 -0800,
Tom Johnson wrote:
>
> > but it would be difficult to replace the social network around the
> projects.
>
> Especially difficult now that GitHub is where the community is. It's
> technically possible to build a social web that works on a decentralized
> basis,
Ah, my bad.
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Karen Coyle
> Sent: Wednesday, February 20, 2013 1:15 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] GitHub Myths (was thanks and poetry)
>
Probably a mistake for me to post at all, but I'm full of mistakes. You
know what, if someone wants to set up a spot for nerd poetry, I think
they should do so. If someone else wants to set up a different spot
using different tech, I think they should do so too.
I think it's mistaken to think
ther people share, adapt, fork, the poems.
> 5. Help the poems persist and record their history as they go.
>
> Jason
>
>
> From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Tom Johnson
> [johnson.tom+code4...@gmail.com]
ODE4LIB@LISTSERV.ND.EDU] On Behalf Of Karen
Coyle
Sent: Thursday, 21 February 2013 6:07 a.m.
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] GitHub Myths (was thanks and poetry)
Sure. Although the question was more: how can we make it easy to have a bunch
of accounts? Or should we have a c4l
gt; > 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
> > >
m]
Sent: Wednesday, February 20, 2013 1:04 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] GitHub Myths (was thanks and poetry)
> 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 was
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
&g
__
> From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Karen
> Coyle [li...@kcoyle.net]
> Sent: Wednesday, February 20, 2013 10:42 AM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] GitHub Myths (was thanks and poetry)
>
> Shaun,
At Wed, 20 Feb 2013 11:20:33 -0500,
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 m
...@kcoyle.net]
Sent: Wednesday, February 20, 2013 10:42 AM
To: CODE4LIB@LISTSERV.ND.EDU
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 tellin
LISTSERV.ND.EDU] On Behalf Of
Karen Coyle
Sent: Wednesday, February 20, 2013 12:07 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] GitHub Myths (was thanks and poetry)
Sure. Although the question was more: how can we make it easy to have a
bunch of accounts? Or should we have a c4l accoun
2:07 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] GitHub Myths (was thanks and poetry)
>
> Sure. Although the question was more: how can we make it easy to have a
> bunch of accounts? Or should we have a c4l account that we share (and
> monitor for spam)? I think an
>* 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
Sure. Although the question was more: how can we make it easy to have a
bunch of accounts? Or should we have a c4l account that we share (and
monitor for spam)? I think anything wysiwyg-y and familiar (wordpress
certainly meets those criteria) would be fine. There does seem to be a
lot of famil
On Wed, Feb 20, 2013 at 11:42 AM, Karen Coyle wrote:
> 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.
While it may be true that you don'
On Feb 20, 2013, at 11:42 AM, Karen Coyle wrote:
> 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 bl
Wordpress?
On Wed, Feb 20, 2013 at 11:42 AM, Karen Coyle wrote:
> 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 thin
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 bea
> (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 pa
36 matches
Mail list logo
