Timestamps are in GMT/BST.
[6:48] -hitchcock.freenode.net- *** Looking up your hostname...
[6:48] -hitchcock.freenode.net- *** Checking Ident
[6:48] -hitchcock.freenode.net- *** Found your hostname
[6:48] -hitchcock.freenode.net- *** No Ident response
[6:48] [frigg VERSION]
[6:49] * DuraLogBot (~PircBot@atlas.duraspace.org) has joined #duraspace
[6:49] * Topic is '[Welcome to DuraSpace - This channel is logged - http://irclogs.duraspace.org/]'
[6:49] * Set by cwilper!ad579d86@gateway/web/freenode/ip.173.87.157.134 on Fri Oct 22 01:19:41 UTC 2010
[9:24] * eddies (~eddies@unaffiliated/eddies) Quit (Quit: Leaving.)
[11:23] * eddies (~eddies@cm18.epsilon183.maxonline.com.sg) has joined #duraspace
[11:23] * eddies (~eddies@cm18.epsilon183.maxonline.com.sg) Quit (Changing host)
[11:23] * eddies (~eddies@unaffiliated/eddies) has joined #duraspace
[12:24] * mhwood (mwood@mhw.ulib.iupui.edu) has joined #duraspace
[13:11] * tdonohue (~tdonohue@c-67-177-108-221.hsd1.il.comcast.net) has joined #duraspace
[14:59] * linux4u (~james@employed.library.emory.edu) has joined #duraspace
[15:22] <linux4u> so who is replacing wilper?
[15:24] <tdonohue> Hi linux4u -- DuraSpace is planning to hire a replacement for Chris Wilper (who left last week for a good opportunity at Thompson Reuters in his hometown). At this time we are still working on the job description/posting. Obviously once that job posting goes out we'll go through a normal hiring process for a replacement.
[15:26] <tdonohue> The only reason the job description hasn't already been posted, is that we're working with other institutions in the Fedora community around a possible "Fedora Repository Futures" project -- which was mentioned recently on the Fedora lists. So, it's very possible the job description may include a role in that project (still being worked out)
[15:27] <tdonohue> does that make sense? If there are questions, let us know. In any case, we will be hiring a replacement for Chris Wilper. It's just a matter of going through call for applicants and hiring processes
[15:39] * linux4u (~james@employed.library.emory.edu) Quit (Read error: Connection reset by peer)
[15:51] * linux4u (~james@employed.library.emory.edu) has joined #duraspace
[16:04] <linux4u> thanks
[16:11] <tdonohue> not a problem!
[17:47] <tdonohue> REMINDER: The DuraSpace Wiki (wiki.duraspace.org) will be going offline in less than 15mins for maintenance & an upgrade. If you are doing any work in the wiki, you should wrap it up & save your changes.
[18:57] <tdonohue> The DuraSpace Wiki upgrade is now complete! If anyone notices anything odd or problematic, feel free to contact sysadmin@duraspace.org, and we'll get it resolved.
[19:37] * linux4u (~james@employed.library.emory.edu) Quit (Ping timeout: 246 seconds)
[19:54] * linux4u (~james@employed.library.emory.edu) has joined #duraspace
[20:19] * mhwood (mwood@mhw.ulib.iupui.edu) Quit (Remote host closed the connection)
[21:45] * hpottinger (~hpottinge@mu-162198.dhcp.missouri.edu) has joined #duraspace
[21:51] * tdonohue (~tdonohue@c-67-177-108-221.hsd1.il.comcast.net) Quit (Read error: Connection reset by peer)
[21:53] * hpottinger (~hpottinge@mu-162198.dhcp.missouri.edu) Quit (Quit: Later, taterz!)
These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.