Difference between revisions of "Journal"

From OSGeo
Jump to navigation Jump to search
(submission added)
Line 83: Line 83:
 
please list yourself below with name, e-mail and field of expertise to review certain articles - indiv. Edt. will contact you if necessary:
 
please list yourself below with name, e-mail and field of expertise to review certain articles - indiv. Edt. will contact you if necessary:
  
##
+
## TBD
##
+
## TBD
##
+
## TBD
  
 
== Newsletter Software ==
 
== Newsletter Software ==

Revision as of 06:15, 28 February 2007

OSGeo News is the working title for the official OSGeo Newsletter. This is the summary page for the project and for developing future editions.


Background

OSGeo News builds on top of the successful history of the GRASS-News production. Volume 4 of that production was a joint GRASS/OSGeo effort. The next edition is broader and branded as OSGeo News.

Submission of articles

Your article should be written in Latex. For instructions which format/style shall be used, please have a look at this working GRASS Newsletter Latex template. If you do not know Latex yet, don't be scared as it is quite easy. You might want to have a look at the Latex Cheat Sheet to get to know a few commands, e.g. how to enumerate, make tables etc. Please send your zipped document to the respective Editors (see below).


Editions

Content Outline

This is the typical outline for an edition:

  1. Editorials
  2. News
  3. Event Reports (2-3 articles)
  4. Project Spotlight (Introductions) (1-2 articles)
  5. Case Studies (2-3 articles)
  6. Integration Studies (2-3 articles)
  7. Topical Studies (1-2 articles)
  8. Programming Tutorials (2-3 tutorials)
  9. Interviews (1-2 people)
  10. Developer Announcements

Short description of content

  • Editorials: written by Edt. in Chief or/and well-known person
  • News: past 6 months and next 3 months, just keywords/URL/date
  • Event Reports: Brief article about meetings/conferences etc.
  • Project Introductions: General introduction to one software project or particular new features of a project
  • Case Studies: Highlighting specific application of technologies to a certain problem, user community or developer needs
  • Integration Studies: Articles showing how many projects can work together in an intergrated fashion, e.g. the power of GRASS, QGIS and GDAL all working together
  • Programming Tutorials: Tutorials showing how to use a library or application at a programmatic level
  • Interviews: Introducing open source community members or organisations
  • Developer Announcements: Announcements about recent changes/improvements to projects

Positions

Typical needs include volunteers to collect, edit, format articles and design/proof layout. Because layout is done using LaTeX, volunteers familiar with it are always appreciated.

each editor is in charge of:

  • looking through submitted articles
  • doing a brief review and perhaps fwd. them to another more experienced user/developer
  • asking certain projects to submit articles (for volumes covering one subject)
  • check for layout errors, so that the final files can easily be merged with all other sections


Open Positions

Name in brackets are proposals, please add somebody/you and/or remove your name. Positions can be flexible too and others are glad to help coach you in your duties, so don't be afraid! These positions can change from volume to volume, so if you want to just try it out for one volume, that is fine too.

  • Newsletter head: announcing new vol./call for articles; announce release dates - Tyler
  • 'Edt. in Chief: merging all sections, check for final version, asking all Edt. so submit final version etc. - Tyler
  • News Editor: to compile general new items from past 6 months for 1-2 pages in the newsletter.
  • Event Editor: to compile information about OSGeo-related events and to find summary reports that could be included as part of the newsletter

* Project Spotlight editor(s): some contributors will have something already completely written. The editor would just help them get it into good form or would help ask more questions and gather more info - Martin

  • Editor for Case Studies: same as above..
  • Editor for Programming/Code Studies : same as above

* Editor for Integration Studies: same as above - Martin

  • Layout Designer - familiar with graphic design and/or LaTeX (first layout can be taken from GRASS-News, only for forthcoming version/changes further skills are necessary). Help show your skills or develop professional quality publication.
  • Spell-checker: native-speaker to check all articles
  • Reviewers: You have particular expertise and can review certain kinds of articles for content. Somewhat like a peer reviewer too, so logical questions can be turned back to authors if needed.
  • Formating/Conversion - moving non-LaTeX content into LaTeX forms (each author/section Edt.has to check for latex errors etc.)
  • Sponsor - interested in sponsoring the newsletter creation?

Assigned Positions

  • Newsletter head: Tyler Mitchell
  • Edt. in Chief: Tyler Mitchell
  • Project Spotlight editor(s): Martin Wegmann
  • Editor for Integration Studies: Martin Wegmann


Reviewers

please list yourself below with name, e-mail and field of expertise to review certain articles - indiv. Edt. will contact you if necessary:

    1. TBD
    2. TBD
    3. TBD

Newsletter Software

Based on GRASS-News (which was based on R News) Latex is recommended, but other publishing packages might be considered for forthcoming issues.

Contributors ought to submit articles in Latex and images as pdf (high res jpg is fine as well, kim (inside kde) can convert them easily to pdf):

  • template for article
    • template for inserting images
    • template for inserting tables

can be taken from GRASS-News.

Process

  1. Confirm editors/volunteers (in process)
  2. Set deadlines
  3. Solicit articles
  4. Collect/edit/review articles
  5. Format to LaTeX
  6. Produce draft
  7. Set deadline for review
  8. Revisions
  9. Final production
  10. Press Release and promotion