LISTSERV mailing list manager LISTSERV 16.0

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  December 2012

CODE4LIB December 2012

Subject:

Re: code4lib.org domain

From:

"Reese, Terry" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 18 Dec 2012 22:08:48 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (123 lines)

Wilhelmina,

To answer your two questions.
1) yes, during the 30 day expiration period when registration lapses your site will typically become unavailable
2) this isn't just about one person at OSU.  Ryan Ordway is our sys admin, but c4l is supported by a number of folks at the institution in various capacities...up to the director.  Were Ryan to leave, the process for maintaining the infrastructure would simply fall to someone else at the Library.

Tr



*************************************
Terry Reese, Associate Professor
Gray Family Chair for
Innovative Library Services
121 Valley Library
Corvallis, OR 97331
541.737.6384
************************************
________________________________
From: Wilhelmina Randtke
Sent: 12/18/2012 2:00 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] code4lib.org domain

Pay for it shouldn't be an issue.  It's like $10 a year to register the
domain, right?  So, don't make a big deal out of OSU paying for it.  The
fee is negligible.

The key concern is how committed to OSU is Ryan Ordway, and what's the
climate there like.  I see this as transferring to the people who are
currently technical contacts at OSU, not to a faceless organization.  If
they already hold several other URLs, and have a policy and timeframe for
tracking and renewing these then that's a plus.

Also, I asked before, and I'm going to ask again, will the domain stop
working (so stop pointing at nameservers) during the redemption period?  If
so, then a worst case scenario is not too bad, because there will be some
warning and a late fee assuming the registered owner can be contacted,
rather than just loosing the domain if the bill isn't paid.

-Wilhelmina Randtke


On Tue, Dec 18, 2012 at 3:41 PM, Jonathan Rochkind <[log in to unmask]> wrote:

> I definitely see what you're saying, but think there are pro's and con's
> both ways.
>
> OSU is already responsible for the bulk of our infrastructure too, adding
> the DNS would be minor.
>
> But there are definitely pro's (as well as con's) to individual and/or
> non-institutional ownership/responsibility/**management, compared to
> institutional.
>
> In the end, as with much Code4Lib, as with much volunteer projects -- what
> it comes down to is who's offering to volunteer to do it. OSU is offering
> to volunteer to do it (and pay for it, apparently?), and we obviously find
> OSU to be generally responsible, since they host the rest of our
> infrastructure.
>
> Someone offering to do it right now, someone we find generally responsible
> -- always beats the hypothetical other solution that has nobody actually
> volunteering to do it.
>
> So, Wilhelmina, are you volunteering to run the DNS instead? :) (and pay
> for it, or fundraise to pay for it)  If you are, then we might have two
> options. Otherwise, we've got one, and no reason to reject it unless we
> thought OSU was not trustworthy with the responsibility or something (which
> if we did, would be a big problem, since they already responsible for a lot
> more than that).
>
>
> On 12/18/2012 4:34 PM, Wilhelmina Randtke wrote:
>
>> I'm for individual ownership and management over organizational.
>> Organizations tend to not have written documentation, and to rely on
>> institutional memory.  I see two things going wrong:  Contact at OSU
>> leaves
>> OSU and no one thinks to renew domain, or OSU doesn't have a dedicated
>> contact and at some point they don't renew because they don't see the
>> value.
>>
>> Also important:  OSU is on state funding cycles, so may have some rule
>> against renewing for more than a year at a time.  So, the deadline to
>> renew
>> will come more frequently than it would with unrestricted funds and the
>> ability to renew for 5 or 10 years at a time.
>>
>> When the domain expires, it will go into a redemption period of about a
>> month.  I remember what the whois record looks like for domains in the
>> redemption period, and whois does give the contact information.  Does the
>> URL stop working during this period?  If so, then that's great because if
>> there is a problem with a renewal then many people will notice the URL not
>> working, and be able to check the status of the domain and get on it.
>>
>> -Wilhelmina Randtke
>>
>>
>> On Tue, Dec 18, 2012 at 2:32 PM, Ed Summers <[log in to unmask]> wrote:
>>
>>  HI all,
>>>
>>> I've owned the code4lib.org since 2005 and have been thinking it might
>>> be wise for to transfer ownership of it to someone else. Sometimes I
>>> forget to pay bills, and miss emails, and it seems like the domain
>>> means something to a larger group of people.
>>>
>>> With Ryan Ordway's help Oregon State University indicated they would
>>> be willing to take over administration of the domain. They also have
>>> been responsible for running the Drupal instance at code4lib.org and
>>> the Mediawiki instance at wiki.code4lib.org -- so it seems like a
>>> logical move.
>>>
>>> But I thought I would bring it up here first in the interests of
>>> transparency, community building and whatnot, to see if there were any
>>> objections or ideas.
>>>
>>> //Ed
>>>
>>>
>>
>>

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

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