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: Help with WordPress for Code4Lib Journal

From:

Ross Singer <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 4 Dec 2012 11:08:01 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (71 lines)

Shaun, I think you missed my point.

Our Drupal (and per Tom's reply, Wordpress -- ...and I'm going to take a stab in the dark and throw MediaWiki instance into the pile) is, for all intents and purposes, unmaintained because we have no in charge of maintaining it.  Oregon State hosts it, but that's it.

Every year, every year, somebody proposes we ditch the diebold-o-tron for "something else" (Drupal modules, mediawiki plugins, OCS, ... and most recently Easy Chair), yet nobody has ever bothered to do anything besides send an email of what we should use instead.  Because that requires work and commitment.

What I'm saying is, we don't have any central organization, and thus we have no real sustainable way to implement locally hosted services.  The Drupal instance, the diebold-o-tron (and maybe Mediawiki) are legacies from when several of us ran a shared server in a colocation facility.  We had skin in the game.  And then our server got hacked because Drupal was unpatched (which sucked) and we realized we probably needed to take this a little more seriously.

The problem was, though, when we moved to OSU for our hosting, we lost any power to do anything for ourselves and since we no longer had to (nor could) maintain anything, all impetus to do so was lost.

To be clear, when we ran all these services on anvil, that wasn't sustainable either!  We simply don't have the the organization or resources to effectively run this stuff by ourselves.  That's why I'm really not interested in hearing about some x we can run for y if it's not backed up with "and my organization which has shown commitment through z will take on the task of doing all the work on this".

-Ross.

On Dec 4, 2012, at 10:41 AM, Shaun Ellis <[log in to unmask]> wrote:

> Tom, can you post the plugin to Code4Lib's github so we can have a crack at it?
> 
> Ross, I'm not sure how many folks on this list were aware of the Drupal upgrade troubles.  Regardless, I don't think it's constructive to put new ideas on halt until it gets done.  Not everyone's a Drupal developer, but they could contribute in other ways.
> 
> -Shaun
> 
> On 12/4/12 10:27 AM, Tom Keays wrote:
>> On Tue, Dec 4, 2012 at 9:53 AM, Ross Singer <[log in to unmask]> wrote:
>> 
>>> Seriously, folks, if we can't even figure out how to upgrade our Drupal
>>> instance to a version that was released this decade, we shouldn't be
>>> discussing *new* implementations of *anything* that we have to host
>>> ourselves.
>>> 
>> 
>> Not being one to waste a perfectly good segue...
>> 
>> The Code4Lib Journal runs on WordPress. This was a decision made by the
>> editorial board at the time (2007) and by and large it was a good one. Over
>> time, one of the board members offered his technical expertise to build a
>> few custom plugins that would streamline the workflow for publishing the
>> journal. Out of the "box", WordPress is designed to publish a string of
>> individual articles, but we wanted to publish issues in a more traditional
>> model, with all the issues published at one time and arranged in the issue
>> is a specific order. We could (and have done) all this manually, but having
>> the plugin has been a real boon for us.
>> 
>> The Issue Manager plugin that he wrote provided the mechanism for:
>> a) preventing articles from being published prematurely,
>> b) identifying and arranging a set of final (pending) articles into an
>> issue, and
>> c) publishing that issue at the desired time.
>> 
>> That person is no longer on the Journal editorial board and upkeep of the
>> plugin has not been maintained since he left. We're now several
>> WordPress releases
>> behind, mainly because we delayed upgrading until we could test if doing so
>> would break the plugins. We have now tested, and it did. I won't bore you
>> with the details, but if we want to continue using the plugin to manage our
>> workflow, we need help.
>> 
>> Is there anybody out there with experience writing WordPress plugins that
>> would be willing to work with me to diagnose what has changed in the
>> WordPress codex that is causing the problems and maybe help me understand
>> how to prevent this from happening again with future releases?
>> 
>> Thanks,
>> Tom Keays / [log in to unmask]
>> 
> 
> -- 
> Shaun D. Ellis
> Digital Library Interface Developer
> Firestone Library, Princeton University
> voice: 609.258.1698 | [log in to unmask]

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