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

CODE4LIB April 2008

Subject:

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

From:

Robert Forkel <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 2 Apr 2008 22:00:32 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (173 lines)

hi all,
in case you want to restore trac - presumably with subversion
repositories - i'd volunteer to admin these apps.
i guess i'm rather unknown, but looking at
https://dev.livingreviews.org/projects/ and
https://dev.livingreviews.org/projects/epubtk/
and https://dev.livingreviews.org/projects/epubtk/wiki/people/robert
might give you an idea.
regards,
robert

On Wed, Apr 2, 2008 at 9:50 PM, Jonathan Rochkind <[log in to unmask]> wrote:
> Good point, agreed. But we've got what we've got, and what we've got can
>  work better if we don't rely on Ryan (who has another job) only to admin
>  it.  Even if we had an agreed moratorium on ever adding anything else, I
>  still think we need to deal with a way to get other code4lib volunteers
>  to have shell access. Examples are me doing the planet; Jon Brinley
>  doing our WordPress install for the Journal; _someone_ taking on Wiki
>  admin, which right now pretty much nobody is doing (which is maybe fine,
>  it's working, but wouldn't we better off if someone did?).
>
>  [ I will admit that I have a personal interest in _replacing_ the
>  MediaWiki install with a DokuWiki install. But it's not fair to ask Ryan
>  to do that. We used to have a 'trac' wiki on the old anvil code4lib, and
>  when I asked Ryan to restore that functionality, he installed MediaWiki.
>  Which is great, but I'd rather have dokuwiki. If I can convince someone
>  to set it up for us. :)  But I shouldn't have even brought this up,
>  because even with no change to our suite of installed apps at all ever,
>  I think we still need to deal with the shell access issue, right? When
>  we put code4lib hosted at OSU, a selling point for some of us would be
>  that shell access for volunteers was possible. I don't think it's fair
>  to expect Ryan to do app-level admin beyond the bare minimum perhaps.
>  But with more than the bare minimum, we can get better services! ]
>
>  Jonathan
>
>
>
>  Ross Singer wrote:
>
> > While I have no comment on this particular issue (since nobody wants
> > me adminning *anything*), I would like to propose that before we set
> > up any new services/applications on code4lib.org, we talk about
> > whether or not any of the existing applications have functionality
> > that could suffice.
> >
> > I guess my point is, the level of ambivalence that this thread is
> > generating doesn't make me terribly hopeful for the longterm
> > sustainability of volunteer service admins.
> >
> > -Ross.
> >
> > On Wed, Apr 2, 2008 at 3:25 PM, Jonathan Rochkind <[log in to unmask]>
> wrote:
> >
> >
> > > Okay, so new plan for access to code4lib server, since nobody stepped up
> > >  to want to be an app admin junta. :)  Subject to approval by Ryan and
> > >  Jeff, of course.  Recall that Ryan and Jeff at OSU say they are ready
> to
> > >  grant shell access to code4libbers, but weren't sure how to figure out
> > >  _who_ to grant access too--granting access to any random person that
> > >  emails Ryan/Jeff seems like a bad idea of course!  So they were open to
> > >  suggestion from us.
> > >
> > >  The idea last time was that there should be one or two or three people
> > >  that take overall responsibility for app-level admin on that machine,
> > >  who could then grant access to others. (Recall that Ryan is still
> > >  overall root sysadmin responsible for OS stuff, just not for our apps).
> > >  Which was a fine plan, but nobody said they wanted to do it. :)
> > >
> > >  So new plan. If someone has a need for shell access (because they want
> > >  to be responsible for management of one of our apps; Like the WordPress
> > >  for the Journal; or the Drupal; or the wiki; or the planet;  including
> > >  possibly new apps that the code4lib community wants)---they email this
> > >  code4lib list explaining what they are going to do, and that they are
> > >  qualified to do it without messing it up. :)  We, in our usual way, nit
> > >  pick it to death and debate it. But eventually a rough consensus is
> > >  reached. And Ryan grants the shell access.  If someone thinks it's a
> > >  horrible idea to give that person shell access, then I guess it doesn't
> > >  go forward. I don't see the need for any actual 'voting', I think
> mostly
> > >  it'll just work out. (For instance, Ryan already pre-emptively gave me
> > >  shell access to add new feeds to the planet. If I had emailed the list
> > >  and said that, which I'm doing now, everyone would have just ignored it
> > >  and/or said, cool.)
> > >
> > >  So?
> > >
> > >  Jonathan
> > >
> > >
> > >
> > >
> > >
> > >
> > > > On 3/21/08 8:13 AM, "Jonathan Rochkind" <[log in to unmask]> wrote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > > So as many of you know, OSU is now hosting the code4lib.org server,
> with
> > > > > the various code4lib community apps running on it. Jeremy Frumkin's
> > > > > group hosts it, and Ryan Ordway does the heavy sysadmin lifting.
> > > > >
> > > > > They're now ready to start granting other people shell access to the
> > > > > machine to manage/admin apps. This was part of the original plan
> when
> > > > > hosting moved to OSU.  While Ryan provides basic sysadmining and
> > > > > security, the intention isn't neccesarily for him to manage
> individual
> > > > > apps, but instead to take advantage of interested code4lib
> volunteers to
> > > > > do this--essentially how things worked before OSU hosted the
> code4lib
> > > > > server. More hands means less work. (Sometimes, to an extent. :) ).
> > > > >
> > > > > So the question for the community is--how the heck should Jeremy and
> > > > > Ryan determine _who_ to give shell access to? 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.  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.
> > > > >
> > > > > Jonathan
> > > > >
> > > > >
> > > > >
> > > > >
> > > > --
> > > >
> > > >
> > > >
> > > >
> > > >
> > >  --
> > >  Jonathan Rochkind
> > >  Digital Services Software Engineer
> > >  The Sheridan Libraries
> > >  Johns Hopkins University
> > >  410.516.8886
> > >  rochkind (at) jhu.edu
> > >
> > >
> > >
> >
> >
> >
>
>  --
>  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

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