Difference between revisions of "Journal"
Jump to navigation
Jump to search
m (→Volunteer Needs: adding a few ideas) |
Wiki-Martin (talk | contribs) (added various items, discussion welcome) |
||
| Line 14: | Line 14: | ||
# News | # News | ||
# Event Reports (2-3 articles) | # Event Reports (2-3 articles) | ||
| − | # Project Introductions (1-2 articles) | + | # Project Spotlight (Introductions) (1-2 articles) |
# Case Studies (2-3 articles) | # Case Studies (2-3 articles) | ||
# Integration Studies (2-3 articles) | # Integration Studies (2-3 articles) | ||
| Line 20: | Line 20: | ||
# Interview | # Interview | ||
# Developer Announcements | # 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 | ||
| + | * Case Studies: rather scientific articles? or developer focused articles? | ||
| + | * Integration Studies: ? | ||
| + | * Interview: just one? | ||
| + | * Developer Announcements: articles about programming or only announcements? | ||
== Volunteer Needs == | == Volunteer Needs == | ||
Typical needs include volunteers to write, collect, edit, format articles and design/proof layout. Because layout is done using LaTeX, volunteers familiar with it are always appreciated. | Typical needs include volunteers to write, 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 | ||
| + | |||
Some other areas where the Newsletter could use volunteers: | Some other areas where the Newsletter could use volunteers: | ||
| + | |||
| + | * Newsletter head: announcing new vol./call for articles; announce release dates | ||
| + | * Edt. in Chief: merging all sections, check for final version, asking all Edt. so submit final version etc. | ||
* News Editor: to compile general new items from past 6 months for 1-2 pages in the newsletter. | * 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 | * 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 | + | * 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. |
| − | * Case | + | * Editor for Case Studies: same as above.. |
| + | * Editor for Code Studies (Integration Studies?): same as above.. | ||
* Layout Designer - familiar with graphic design and/or LaTeX | * Layout Designer - familiar with graphic design and/or LaTeX | ||
* Formatting/Conversion - moving non-LaTeX content into LaTeX forms | * Formatting/Conversion - moving non-LaTeX content into LaTeX forms | ||
* ?Sponsor - perhaps we could get a paying sponsor/advertiser and find some useful way to spend that money? | * ?Sponsor - perhaps we could get a paying sponsor/advertiser and find some useful way to spend that money? | ||
| + | * spell-checker: native-speaker to check all articles | ||
* ?Translators - should we try to line up translators too? | * ?Translators - should we try to line up translators too? | ||
== Process == | == Process == | ||
| − | # Confirm editors/volunteers | + | # Confirm editors/volunteers (in process) |
# Set deadlines | # Set deadlines | ||
# Solicit articles | # Solicit articles | ||
Revision as of 02:05, 22 February 2007
All draft thoughts thrown up by Tyler - ready for discussion/debate
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.
Editions
- GRASS/OSGeo-News Volume 4
- OSGeo News Volume 1 (Newsletter_Volume_1 - in development)
Content Outline
This is the typical outline for an edition:
- Editorials
- News
- Event Reports (2-3 articles)
- Project Spotlight (Introductions) (1-2 articles)
- Case Studies (2-3 articles)
- Integration Studies (2-3 articles)
- Topical Studies (1-2 articles)
- Interview
- 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
- Case Studies: rather scientific articles? or developer focused articles?
- Integration Studies: ?
- Interview: just one?
- Developer Announcements: articles about programming or only announcements?
Volunteer Needs
Typical needs include volunteers to write, 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
Some other areas where the Newsletter could use volunteers:
- Newsletter head: announcing new vol./call for articles; announce release dates
- Edt. in Chief: merging all sections, check for final version, asking all Edt. so submit final version etc.
- 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.
- Editor for Case Studies: same as above..
- Editor for Code Studies (Integration Studies?): same as above..
- Layout Designer - familiar with graphic design and/or LaTeX
- Formatting/Conversion - moving non-LaTeX content into LaTeX forms
- ?Sponsor - perhaps we could get a paying sponsor/advertiser and find some useful way to spend that money?
- spell-checker: native-speaker to check all articles
- ?Translators - should we try to line up translators too?
Process
- Confirm editors/volunteers (in process)
- Set deadlines
- Solicit articles
- Collect/edit/review articles
- Format to LaTeX
- Produce draft
- Set deadline for review
- Revisions
- Final production
- Press Release and promotion