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  March 2008

CODE4LIB March 2008

Subject:

Re: Access to code4lib.org server--how to work it?

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 21 Mar 2008 12:16:37 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (97 lines)

I think that by allowing a  larger group of people in, we get more done
and have _better_ services. But there's definitely a balancing act,
between stability and more hands.  I don't want to see it balanced too
much toward stability 'guarantees' though. Letting in people we trust to
know what they know and what they dont' know and only touch the stuff
they are volunteering to be responsible for I think can do that.

For instance, I'm happy to be responsible for the planet. And not much
else.  Just being responsible for the planet, I'd be 'wasting' a 'slot'
if we only allowed 2-3 people in---plus I'm not really an experienced
sysadmin!  But I'm willing to manage the planet, and if I weren't doing
it, someone else would have to. I suppose if we can really find 2-3
experienced sysadmin willing to spend a lot of time on code4lib for
free...  but isnt' spreading out the work more a better idea?

As far as the 'formalization' idea---if what you want is a small group
of people deciding who gets shell access, you can have that without
bylaws and a board. Just create the small group of people. Two seperate
questions. If a junta in charge of code4lib sysadmining is a good idea,
create one.

So maybe that's the answer right there. We find 2-3 people to take
_primary_ app-level responsibility for code4lib.org (ryan ordway still
has primary OS-level responsibility), and they are the junta. If someone
else (like me) wants access to do some smaller part, the junta approves
him or her (and the junta can revoke them).  That makes sense to me.
Anyone volunteering to be that junta?   :)

Jonathan

Kevin S. Clarke wrote:
> On Fri, Mar 21, 2008 at 11:13 AM, Jonathan Rochkind <[log in to unmask]> wrote:
>
>>  Pre-OSU hosting, code4lib
>>  was hosted by a defined group of code4libbers who chipped in for hosting
>>  fees, and were the only ones who had shell access. If you wanted shell
>>  access, as I understand it, you'd have to talk to them about becoming a
>>  member of their 'cooperative', and they'd decide whether that would
>>  happen or not.
>>
>
> Well, there wasn't much of a decision.  If folks wanted in they were
> welcome... we weren't turning anyone away or anything.  :-)
>
> Also, just to quibble with the above, the previous machine had more
> than code4libbers on it (some who aren't involved in or that
> interested in code4lib); it was just a working environment that
> volunteered to host the domain for awhile.  It was (and still is) just
> a dev machine... a play space.
>
>
>>  Now, with OSU hosting... what should happen? It probably
>>  doesn't make sense that any Joe Schmoe that nobody's heard of can just
>>  email Ryan and automatically get shell access. So ruling that out....
>>  any ideas?    Maybe if you want shell access to manage a particular
>>  application, you email the code4lib listserv, and....   then what?  Not
>>  sure.
>>
>
> I think one of the reasons of going to OSU was to make the machine a
> production oriented machine.  In my opinion, it should be locked down
> and not be as open as the anvil machine was/is.  I think there should
> be two or three experienced folks who volunteer to do the sysadmining
> (this aligns with the talk of structuring code4libcon).  If there is a
> project that someone wants to start in the code4lib domain that
> benefits the code4lib community, then they should discuss it on the
> mailing list and build up some community support.  If that happens
> (e.g., they get enough volunteers and build an organization structure
> for the project), they should get access to a shell account to bring
> it into production (only after it has been developed and the bugs
> worked out on another machine).
>
> For all the other non-production stuff (experiments with new services,
> etc.), people should use their own machines or form cooperatives
> (formal or informal) to share the costs.  I'm sure Ed could set it up
> so that whatever subdomain they want gets resolved to their machine
> (e.g., freakflag.code4lib.org).  This could be used for testing or
> even for just perpetual projects that are never meant to go
> production.  I see he just sent an email saying that he could :-)
>
> My 2c anyway....
>
> Kevin
>
> --
> There are two kinds of people in the world: those who believe there
> are two kinds of people and those who know better.
>
>

--
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886
rochkind (at) jhu.edu

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

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