I think that editors for big journals typically offload a lot of the work to their associate editors. In fact, the more I look at the OJS system, I think it's set up nicely for this. Another thing that might be useful would be a monthly conference call or IRC chat to discuss dates, plans, etc and to give everyone a bit of a (re-)kick start each month... - Dan<br>
<br><div class="gmail_quote">On Tue, Apr 8, 2008 at 3:42 AM, Yann Chemin <<a href="mailto:yann.chemin@gmail.com">yann.chemin@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tyler,<br>
<br>
What a bout choosing/inviting a guest editor for each release?<br>
That person would have the coordinating role of scientific content<br>
especially, she/he would be sent draft for review/approval.<br>
<br>
The person does not need to be into it, but just review (on a separate<br>
document or by email) and approve quality, maybe this will offload<br>
from your shoulders.<br>
<br>
Cheers,<br>
Yann<br>
<div><div></div><div class="Wj3C7c"><br>
On 08/04/2008, Tyler Mitchell (OSGeo) <<a href="mailto:tmitchell@osgeo.org">tmitchell@osgeo.org</a>> wrote:<br>
> Hi everyone,<br>
> I'm still picking away at Volume 4 - the Annual Report. But as I do so, I<br>
> wanted to bring up an idea some of you may be interested in.<br>
><br>
> The Journal is not one of my highest priorities and as such suffers a bit<br>
> of neglect, especially around timing of issues, involving new volunteers,<br>
> etc. I am wondering if anyone would be interested in trying out<br>
> coordinating the next release. It would require no long term commitment and<br>
> we couldn't fire you ;-) You could think of it as being a (guest) Release<br>
> Manager. If it worked out well, then it would become a regular position.<br>
> At least it would give you some experience and you'd probably have many<br>
> suggestions for improvements. I'd be here to help support and guide, but I<br>
> realise I need some further help to keep things moving.<br>
><br>
> I'm hopeful that with the growing interest and momentum behind the journal,<br>
> we can tap into some more of your skills and interests. If you ever see a<br>
> way to improve the processes, please discuss them on this list, then we can<br>
> see how to implement them.<br>
><br>
> Best wishes,<br>
> Tyler<br>
> _______________________________________________<br>
> newsletter mailing list<br>
> <a href="mailto:newsletter@lists.osgeo.org">newsletter@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/newsletter" target="_blank">http://lists.osgeo.org/mailman/listinfo/newsletter</a><br>
><br>
<br>
<br>
</div></div><font color="#888888">--<br>
Yann Chemin<br>
International Rice Research Institute<br>
Office: <a href="http://www.irri.org/gis" target="_blank">http://www.irri.org/gis</a><br>
Perso: <a href="http://www.freewebs.com/ychemin" target="_blank">http://www.freewebs.com/ychemin</a><br>
</font><div><div></div><div class="Wj3C7c">_______________________________________________<br>
newsletter mailing list<br>
<a href="mailto:newsletter@lists.osgeo.org">newsletter@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/newsletter" target="_blank">http://lists.osgeo.org/mailman/listinfo/newsletter</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Daniel P. Ames, PhD, PE<br>Geospatial Software Lab<br>Department of Geosciences<br>Idaho State University - Idaho Falls<br><a href="mailto:amesdani@isu.edu">amesdani@isu.edu</a><br>
<a href="http://www.hydromap.com">www.hydromap.com</a><br>