has become outdated. A couple of those listed have 'retired', no?
Anyone know who's who? Is MJ still on the committee?
Jonathan
--
You received this message because you are subscribed to the Google Groups "Code4Lib Journal-discuss" group.
To post to this group, send email to c4lj-d...@googlegroups.com.
To unsubscribe from this group, send email to c4lj-discuss+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/c4lj-discuss?hl=en.
I haven't seen EC around this list for a while... and Emily is coming
back, right?
Is it time to recruit a couple new editors?
Tim M
On 7/20/11 1:35 PM, Jodi Schneider wrote:
> Technically it should be updated every issue -- maybe a checklist is in
> order.
>
> I've seen CFP's for issue 15 but this mentions the CE for 13...
>
> Otherwise, I've no clue. :(
>
> -J
>
> On Wed, Jul 20, 2011 at 5:49 PM, Jonathan Rochkind <roch...@jhu.edu
> <mailto:roch...@jhu.edu>> wrote:
>
> I think our list of editors at:
> http://journal.code4lib.org/__editorial-committee
> <http://journal.code4lib.org/editorial-committee>
>
> has become outdated. A couple of those listed have 'retired', no?
> Anyone know who's who? Is MJ still on the committee?
>
> Jonathan
>
> --
> You received this message because you are subscribed to the Google
> Groups "Code4Lib Journal-discuss" group.
> To post to this group, send email to c4lj-d...@googlegroups.com
> <mailto:c4lj-d...@googlegroups.com>.
> To unsubscribe from this group, send email to
> c4lj-discuss+unsubscribe@__googlegroups.com
> <mailto:c4lj-discuss%2Bunsu...@googlegroups.com>.
> For more options, visit this group at
> http://groups.google.com/__group/c4lj-discuss?hl=en
> <http://groups.google.com/group/c4lj-discuss?hl=en>.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Code4Lib Journal-discuss" group.
> To post to this group, send email to c4lj-d...@googlegroups.com.
> To unsubscribe from this group, send email to
> c4lj-discuss...@googlegroups.com.
MJ indicated a few weeks ago that Issue 14 would be his last.
I haven't seen EC around this list for a while... and Emily is coming back, right?
Is it time to recruit a couple new editors?
Tim M
On 7/20/11 1:35 PM, Jodi Schneider wrote:
Technically it should be updated every issue -- maybe a checklist is in
order.
I've seen CFP's for issue 15 but this mentions the CE for 13...
Otherwise, I've no clue. :(
-J
On Wed, Jul 20, 2011 at 5:49 PM, Jonathan Rochkind <roch...@jhu.edu<mailto:roch...@jhu.edu>> wrote:
I think our list of editors at:
http://journal.code4lib.org/__editorial-committee
<http://journal.code4lib.org/editorial-committee>
has become outdated. A couple of those listed have 'retired', no?
Anyone know who's who? Is MJ still on the committee?
Jonathan
--
You received this message because you are subscribed to the Google
Groups "Code4Lib Journal-discuss" group.
To post to this group, send email to c4lj-d...@googlegroups.com
<mailto:c4lj-discuss@googlegroups.com>.
<mailto:c4lj-discuss%2Bunsu...@googlegroups.com>.--
For more options, visit this group at
http://groups.google.com/__group/c4lj-discuss?hl=en
<http://groups.google.com/group/c4lj-discuss?hl=en>.
You received this message because you are subscribed to the Google
Groups "Code4Lib Journal-discuss" group.
To post to this group, send email to c4lj-d...@googlegroups.com.
To unsubscribe from this group, send email to
--
You received this message because you are subscribed to the Google Groups "Code4Lib Journal-discuss" group.
To post to this group, send email to c4lj-d...@googlegroups.com.
To unsubscribe from this group, send email to c4lj-discuss+unsubscribe@googlegroups.com.
I'm not sure any timing is perfect.
On 7/20/11 1:49 PM, Jodi Schneider wrote:
> I'd suggest an annual recruit at the conference. Badly timed right now
> though... -J
>
> On Wed, Jul 20, 2011 at 6:40 PM, Tim McGeary <timmc...@gmail.com
> <mailto:timmc...@gmail.com>> wrote:
>
> MJ indicated a few weeks ago that Issue 14 would be his last.
>
> I haven't seen EC around this list for a while... and Emily is
> coming back, right?
>
> Is it time to recruit a couple new editors?
>
> Tim M
>
>
> On 7/20/11 1:35 PM, Jodi Schneider wrote:
>
> Technically it should be updated every issue -- maybe a
> checklist is in
> order.
>
> I've seen CFP's for issue 15 but this mentions the CE for 13...
>
> Otherwise, I've no clue. :(
>
> -J
>
> On Wed, Jul 20, 2011 at 5:49 PM, Jonathan Rochkind
> <roch...@jhu.edu <mailto:roch...@jhu.edu>
> <mailto:roch...@jhu.edu <mailto:roch...@jhu.edu>>> wrote:
>
> I think our list of editors at:
> http://journal.code4lib.org/____editorial-committee
> <http://journal.code4lib.org/__editorial-committee>
> <http://journal.code4lib.org/__editorial-committee
> <http://journal.code4lib.org/editorial-committee>>
>
> has become outdated. A couple of those listed have
> 'retired', no?
> Anyone know who's who? Is MJ still on the committee?
>
> Jonathan
>
> --
> You received this message because you are subscribed to the
> Google
> Groups "Code4Lib Journal-discuss" group.
> To post to this group, send email to
> c4lj-d...@googlegroups.com <mailto:c4lj-d...@googlegroups.com>
> <mailto:c4lj-discuss@__googlegroups.com
> <mailto:c4lj-d...@googlegroups.com>>.
>
> To unsubscribe from this group, send email to
> c4lj-discuss+unsubscribe@__goo__glegroups.com
> <http://googlegroups.com>
> <mailto:c4lj-discuss%__2Buns...@googlegroups.com
> <mailto:c4lj-discuss%252Buns...@googlegroups.com>__>.
>
> For more options, visit this group at
> http://groups.google.com/____group/c4lj-discuss?hl=en
> <http://groups.google.com/__group/c4lj-discuss?hl=en>
> <http://groups.google.com/__group/c4lj-discuss?hl=en
> <http://groups.google.com/group/c4lj-discuss?hl=en>>.
>
>
> --
>
> You received this message because you are subscribed to the Google
> Groups "Code4Lib Journal-discuss" group.
> To post to this group, send email to
> c4lj-d...@googlegroups.com
> <mailto:c4lj-d...@googlegroups.com>.
> To unsubscribe from this group, send email to
> c4lj-discuss+unsubscribe@__googlegroups.com
> <mailto:c4lj-discuss%2Bunsu...@googlegroups.com>.
> For more options, visit this group at
> http://groups.google.com/__group/c4lj-discuss?hl=en
> <http://groups.google.com/group/c4lj-discuss?hl=en>.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Code4Lib Journal-discuss" group.
> To post to this group, send email to c4lj-d...@googlegroups.com
> <mailto:c4lj-d...@googlegroups.com>.
> To unsubscribe from this group, send email to
> c4lj-discuss+unsubscribe@__googlegroups.com
> <mailto:c4lj-discuss%2Bunsu...@googlegroups.com>.
> For more options, visit this group at
> http://groups.google.com/__group/c4lj-discuss?hl=en
> <http://groups.google.com/group/c4lj-discuss?hl=en>.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Code4Lib Journal-discuss" group.
> To post to this group, send email to c4lj-d...@googlegroups.com.
> To unsubscribe from this group, send email to
> c4lj-discuss...@googlegroups.com.
Kelley
//Ed
I think we can accomodate more editors at this point. I think it's okay if we accept new editors without a giant announcement with deadlines for new editor nominations -- just like we accept rolling article submissions. Can we have Ed fill out our very short application we've used before, and then vote, as per our usual process for accepting new editors?
________________________________________
From: c4lj-d...@googlegroups.com [c4lj-d...@googlegroups.com] on behalf of Ed Summers [e...@pobox.com]
Sent: Friday, July 22, 2011 7:52 AM
To: c4lj-d...@googlegroups.com
Subject: Re: [c4lj] current editors
+1 for people that take the initiative seeking a more active role in the Journal!
+1 for proceeding as JR suggests.
Carol Bean
bean...@gmail.com
> You received this message because you are subscribed to the Google Groups "Code4Lib Journal Articles" group.
> To post to this group, send email to c4lj-a...@googlegroups.com.
> To unsubscribe from this group, send email to c4lj-article...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/c4lj-articles?hl=en.
>
>