https://wiki.osgeo.org/w/api.php?action=feedcontributions&feedformat=atom&user=Wiki-Danames 2026-04-11T15:39:00Z User contributions MediaWiki 1.35.9 https://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Edu_BOF_sign_up&diff=57083 2011-09-08T21:56:17Z

<p>Wiki-Danames: /* Wed Sept 14th OSGeo Edu BOF meeting 5:30-8:30 pm */</p> <hr /> <div>'''Please add your name below in either of the two suggested OSGeo edu working sessions if you are interested in participating at FOSS4G in Denver'''. <br /> <br /> BOF sessions are scheduled for Wed Sept 14th from 5:30-8:30 pm. We should definitely have a meeting then. <br /> <br /> There is also space available for a further meeting on Saturday Sept 17th if people are around and willing to use some of that day to work on content-related activities (TBD). One idea would be to try and have a &quot;Workbook development sprint&quot;?<br /> <br /> == Wed Sept 14th OSGeo Edu BOF meeting 5:30-8:30 pm ==<br /> <br /> * Phillip Davis, GeoTech Center<br /> * Ari Jolma, Aalto University, Finland<br /> * Charlie Schweik, UMass Amherst USA (by Skype)<br /> * Walt Jaslanek, UMass Amherst, USA<br /> * Helena Mitasova, North Carolina State University, USA<br /> * Suchith Anand, University of Nottingham, UK (by Skype)<br /> * Scott Mitchell, Carleton University, Ottawa, Canada<br /> * Rafael Moreno, University of Colorado Denver<br /> * Dan Ames, Idaho State University, Idaho, USA<br /> <br /> == Possible discussion topic items ==<br /> <br /> * Short informal presentations by Phillip and Suchith on their activities in their organizations and how they see the OSGeo edu group connecting to them<br /> * Short individual reports on OSGeo-relevant activities by other participants<br /> * See if we can come to any consensus on what we as a group should focus on over the next 6 months... for example, can we make any progress collectively on Open Source Desktop and Web handbooks? Should that be our focus? What have individuals done over the last year and are there tangible education-related products they are willing to share with the community? <br /> * Edu community -- enter any thoughts you have here</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=FOSS4G_2011_Edu_BOF_sign_up&diff=57060 2011-09-07T18:05:41Z

<p>Wiki-Danames: /* Wed Sept 14th OSGeo Edu BOF meeting 5:30-8:30 pm */</p> <hr /> <div>'''Please add your name below in either of the two suggested OSGeo edu working sessions if you are interested in participating at FOSS4G in Denver'''. <br /> <br /> BOF sessions are scheduled for Wed Sept 14th from 5:30-8:30 pm. We should definitely have a meeting then. <br /> <br /> There is also space available for a further meeting on Saturday Sept 17th if people are around and willing to use some of that day to work on content-related activities (TBD). One idea would be to try and have a &quot;Workbook development sprint&quot;?<br /> <br /> == Wed Sept 14th OSGeo Edu BOF meeting 5:30-8:30 pm ==<br /> <br /> * Phillip Davis, GeoTech Center<br /> * Ari Jolma, Aalto University, Finland<br /> * Charlie Schweik, UMass Amherst USA (by Skype)<br /> * Walt Jaslanek, UMass Amherst, USA<br /> * Helena Mitasova, North Carolina State University, USA<br /> * Suchith Anand, University of Nottingham, UK (by Skype)<br /> * Scott Mitchell, Carleton University, Ottawa, Canada<br /> * Rafael Moreno, University of Colorado Denver<br /> * Dan Ames, Idaho State University<br /> <br /> == Possible discussion topic items ==<br /> <br /> * Short informal presentations by Phillip and Suchith on their activities in their organizations and how they see the OSGeo edu group connecting to them<br /> * Short individual reports on OSGeo-relevant activities by other participants<br /> * See if we can come to any consensus on what we as a group should focus on over the next 6 months... for example, can we make any progress collectively on Open Source Desktop and Web handbooks? Should that be our focus? What have individuals done over the last year and are there tangible education-related products they are willing to share with the community? <br /> * Edu community -- enter any thoughts you have here</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=File:DotNetListHeaderLogo.png&diff=47457 2010-05-14T16:09:18Z

<p>Wiki-Danames: Header graphic for the info page for the .NET mailing list.</p> <hr /> <div>Header graphic for the info page for the .NET mailing list.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Projects&diff=46946 2010-04-09T21:10:07Z

<p>Wiki-Danames: adding MapWindow to pending incubation status</p> <hr /> <div>= OSGeo Labs Projects =<br /> <br /> <br /> = Purpose =<br /> OSGeo Labs is a place to list Open Source Geospatial Software that hasn't reached Incubation status. OSGeo Labs aims to:<br /> * Help projects progress to OSGeo Incubation.<br /> * Advertise projects and find like minded developers.<br /> * Merge with similar projects. A project has a greater chance of reaching Incubation when integrated with similar projects.<br /> <br /> This is the right place to start submitting your project so other OSGeo members can review them and send you feedback.<br /> <br /> == Criteria ==<br /> Projects should only list themselves in OSGeo Labs if they follow the OSGeo Incubation principles.<br /> # The code is under an OSI approved license (data &amp; doc projects need to specify their choice for a type of license).<br /> # The project is willing to keep code clear of encumbrances<br /> # The project is &quot;geospatial&quot;, or directly supports geospatial applications.<br /> # The project hopes to become a graduated OSGeo project, or have reasons why incubation is not appropriate.<br /> <br /> ==Becoming a Labs Project==<br /> Becoming an OSGeo Labs should be easy and encouraged to all project that respond to criterias above. All project that use the OSGeo infrastructure or that wants to assign their copyright to OSGeo should add themselves below.<br /> <br /> ==Pending Incubation==<br /> Projects which have self assessed themselves ready for incubation and waiting for a mentor: [http://trac.osgeo.org/osgeo/query?status=new&amp;status=assigned&amp;component=Incubator&amp;keywords=%7Eapplication List from OSGeo trac]<br /> * [http://mapwindow.org MapWindow] - The MapWindow project was started in 1998 and became open source in January, 2005. It includes an ActiveX component (similar to ESRI's now discontinued MapObjects tool) an extensible desktop application, and a set of .NET libraries (MapWindow 6) which are intended to be an alternative to ESRI's ArcObjects. The MapWindow team has been a supporter of OSGeo since its inception, with workshops and exhibits at all-but-one FOSS4g conferences and participation on various OSGeo committees and efforts. We just held our first formal project conference in April 2010 at which the team agreed to apply for incubation status with OSGeo. The application is forth-coming.<br /> <br /> ==Stable Projects==<br /> * [http://geowebcache.org GeoWebCache]<br /> * [http://pgrouting.org pgRouting]<br /> <br /> ==Young or Experimental Projects==<br /> * [http://geoext.org GeoExt]<br /> * GeoFunctions [http://sourceforge.net/projects/geofunctions/ Geo Functions sourceforge page]<br /> * Geoinformatica [http://trac.osgeo.org/geoinformatica/ OSGeo trac site]<br /> * [[OpenGeocoder]]<br /> * [[OpenRouter]]<br /> * [http://www.geog.leeds.ac.uk/people/a.turner/src/andyt/java/grids/ Grids]<br /> * [[OSGeo Graphics]]<br /> * [[thinkGeo]], a Semantic GIS toolkit<br /> <br /> == Responsibilities ==<br /> OSGeo Labs aims to have minimal red tape to reduce overhead.<br /> <br /> ===Project Champion===<br /> The Project Champion is responsible for:<br /> # Strongly recommended: Read Karl Fogel's book on [http://producingoss.com/ Open Source Software - How to Run a Successful Free Software Project]<br /> # Ensure the project complies with OSGeo principles by addressing the [[#Criteria]] above.<br /> # Create a home page for the project. The OSGeo wiki is recommended for this page. A page should answer the OSGeo [[#Criteria]].<br /> # List the project under the appropriate heading on this page.<br /> # Announce and discuss the project on the [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss] email list.<br /> # Move the project toward incubation.<br /> <br /> ===Incubation Committee===<br /> The OSGeo Incubation Committee is responsible for:<br /> # Investigate, then possibly remove a project from OSGeo Labs if it doesn't follow OSGeo Labs [[#Criteria]].<br /> # Periodically (at least annually), review projects in OSGeo labs and remove projects which have &quot;died&quot; or don't follow OSGeo Labs [[#Criteria]].<br /> <br /> == Helpful Resource ==<br /> # Get your project a mailing-list and a bug tracker<br /> ## [http://sourceforge.net/ SourceForge] provides code repository, mailing list and bug tracker services. (contact [mailto:sunburned.surveyor@gmail.com Landon Blake] to get help on SourceForge service)<br /> # Approach the [[Spotlights]] editors about doing a spotlight interview about your project.<br /> <br /> ===Assigning Copyright to OSGeo===<br /> Many graduated OSGeo projects choose to assign their copyright to OSGeo. A young project can assign its copyright to OSGeo by:<br /> * TBD: As of 15 April 2009, the process for assigning copyright has not been resolved, it is being discussed on the OSGeo discuss email list. It may involve the following:<br /> ** Asking the incubation committee and doing it<br /> ** Having a graduated OSGeo project mentor yours<br /> <br /> ===Using OSGeo infrastructure===<br /> It's possible to use OSGeo infrastructure to host your project or to have a trac and subversion server. You can get help if your project respond to criterias above and ask the right person for it.<br /> <br /> == Disclosure ==<br /> <br /> OSGeo or any of its affiliates do not take responsibility or endorse any of the software listed here. OSGeo doesn't guarantee the integrity of the code or any other aspect of the above softwares.<br /> <br /> = References =<br /> * [http://www.freegis.org/ FreeGIS list]<br /> <br /> [[Category: Software Stack]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Project_Graduation_Checklist&diff=43974 2009-12-29T22:00:41Z

<p>Wiki-Danames: small typo &quot;achieved&quot; versus &quot;archived&quot; fixed...</p> <hr /> <div>'''The official copy of this document lives at http://www.osgeo.org/incubator/process/project_graduation_checklist.html'''<br /> <br /> = Document Status =<br /> <br /> '''IncCom Document Number''': X<br /> <br /> '''Version''': &lt;font color=&quot;red&quot;&gt;1.1. Updates since 1.0 are in red.&lt;/font&gt;<br /> <br /> '''Last Updated''': &lt;font color=&quot;red&quot;&gt;December 2008.&lt;/font&gt;<br /> <br /> '''Status''': draft<br /> <br /> = Purpose =<br /> <br /> The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.<br /> <br /> A project should have institutionalized the processes in this list or provide justification why the process is not used.<br /> <br /> = Terms and Definitions =<br /> <br /> ; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.<br /> ; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)]''<br /> <br /> = Checklist =<br /> <br /> == License ==<br /> <br /> # The code has been adequately vetted to assure it is all properly licensed (a.k.a [http://www.osgeo.org/incubator/process/codereview.html provenance review]).<br /> # All code contributors have agreed to abide by the project's license policy.<br /> <br /> == Processes ==<br /> <br /> # The project has a suitable governance policy and project management committee established that ensures decisions are made, documented and adhered to?<br /> # The developer community works in a healthy way, open to input, new members and reaching consensus on decisions. Ideally, the developers come from a diversity of backgrounds as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving. <br /> # The project has documented its management processes. This is typically done within a Developers Guide or Project Management Plan.<br /> # The project has user documentation.<br /> # The project has developer documentation.<br /> # The project has code under configuration control. Eg, subversion.<br /> # The project uses an issue tracker.<br /> # The project uses public communication channels. Eg archived email lists.<br /> # The project has an automated build process.<br /> # The project manages quality. Ideally, this includes an automated test system.<br /> # The project has a defined release process.<br /> <br /> == Marketing ==<br /> <br /> # &lt;font color=&quot;red&quot;&gt;Appropriate marketing material has been created, and relevant web pages have been updated with project status as identified in [[Project Mentions]].&lt;/font&gt;<br /> <br /> [[Category: Incubation]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=FOSS4G_2009_Scientific_committee_expertises&diff=39429 2009-06-26T22:21:04Z

<p>Wiki-Danames: </p> <hr /> <div>== Purposes of this page ==<br /> <br /> Members of the scientific committee of the FOSS4G 2009 academic track have different research interests. In order to assign papers for reviewing to an appropriate specialist in the fields each paper deals with, this page tries to gather all domains of expertise or of interest for each member of the committee.<br /> <br /> So, members of the scientific committee, please edit the table below and add 5 to 10 keywords that summarize your expertise or your research interests.<br /> <br /> == Domains of interest ==<br /> <br /> {| border=&quot;1&quot; cellpadding=&quot;5&quot; cellspacing=&quot;0&quot;<br /> |+ align=&quot;center&quot; style=&quot;color:#e76700;&quot;|<br /> ! Member<br /> ! Expertise / research interests<br /> |-<br /> |Thierry Badard<br /> |Geospatial BI (Business Intelligence), Spatial OLAP, spatial ETL and datawarehousing, geo-analytical tools and services, decision support, Services Oriented Architectures (SOA), geospatial web services, Location Based Services (LBS), Mobile and context-aware applications, geospatial standards<br /> |-<br /> |Jorge Gustavo Rocha<br /> |...<br /> |-<br /> |Venkatesh Raghavan<br /> |... <br /> |- <br /> | Maria Antonia Brovelli<br /> |Cartography, Geodesy, Geospatial web services, geospatial standards, LIDAR, DTM, HR Satellites imagery, geoprocessing algorithms<br /> |- <br /> |Ari Jolma <br /> |...<br /> |- <br /> |Frédéric Hubert <br /> |...<br /> |- <br /> |Suchith Anand <br /> |cartography, automated map generalization, geohydroinformatics, location based services, asset management<br /> |- <br /> |Tyler Erickson <br /> |geostatistics, inverse modeling, geospatial web services, relational database design, decision support, remote sensing algorithm development<br /> |- <br /> |Serena Coetzee <br /> |...<br /> |- <br /> |Dimitris Kotzinos <br /> |Semantic Web, Semantics in Geographic Information (Geospatial Semantic Web), Geospatial Web Services, Service Oriented Atchitectures (SOA), Spatial Databases, Spatially Enabled Mashups, Spatially Enabled RSS, Spatial Decision Support Systems, Location Based Services (LBS), Standards<br /> |- <br /> |Dan Ames <br /> |hydrologic modeling, terrain analysis, environmental modeling, probabalistic modeling, object oriented GIS, custom GIS software, .NET applications<br /> |- <br /> |Bénédicte Bucher <br /> |Services Oriented Architectures (SOA), geospatial web services, styles, schema transformation and integration, user interfaces, geospatial semantic Web<br /> |- <br /> |Christoph Stasch <br /> |Geosensor Networks, Sensor Web, SOA, geospatial web services, spatial databases, web standards<br /> |- <br /> |Barend Köbben <br /> |Cartography, Visualization, Services Oriented Architectures (SOA), geospatial web services<br /> |- <br /> |Cyril de Runz <br /> |spatial data mining, management of uncertainty, data visualization, image processing, <br /> |- <br /> |Vlad Tanasescu <br /> |knowledge representation, geotagging, geospatial web services, geospatial semantic web, Web maps<br /> |- <br /> |Johannes Brauner <br /> |...<br /> |- <br /> |Charlie Schweik <br /> |...GIS education, GIS and public policy, Web 2.0-based collaboration, web services, GIS in government<br /> |- <br /> |Mike Jackson <br /> |...SDI, LBS, geospatial standards and interoperability, test-beds, ubiquitous positioning.<br /> |- <br /> |William Cartwright <br /> |...<br /> |- <br /> |Jochen Albrecht <br /> |...<br /> |- <br /> |Guy Johnson <br /> |...<br /> |- <br /> |François Pinet <br /> |...<br /> |- <br /> |Lars Bodum <br /> |geovisulization, 3D geoinfo, city models, sdi, spatial planning app., geospatial standards<br /> |- <br /> |Philip James <br /> |Grid and GI, geo-processing architectures (web services), Earth System's application of Geo (transport, climate, water, the environment), Education (tertiary), geospatial standards<br /> |- <br /> |Oliver Shine <br /> |earth observation systems, OGC web services (CSW, WMS, WFS, WCS, SOS), spatial data management, geoprocessing for environmental decision making, geo ICT, SDI, INSPIRE<br /> |- <br /> |Mark Ware <br /> |...<br /> |- <br /> |Simon Abele <br /> |...<br /> |- <br /> |Clara Tattoni <br /> |GIS, wildlife management, wildlife modelling, ecology, landscape change, decision support, forestry, education<br /> |- <br /> |Hans-Jörg Stark <br /> |Volunteered Geographic Information, Open Geo-data, GIS education, business geography, Web 2.0-based collaboration, web mapping<br /> |- <br /> |Sandro Bimonte <br /> |OLAP, Spatial OLAP, data warehouse, spatial data warehouse, GIS, spatial database, visual language for GIS<br /> |- <br /> |Theodor Foerster <br /> |Geoprocessing, standards, web services, SOA, WPS, generalization, web mapping<br /> |- <br /> |Eric Wolf <br /> |Automated generalization, critical cartography, spatial data infrastructures, kite aerial photography, cartograms<br /> |- <br /> |Sidonie Christophe <br /> |...<br /> |- <br /> |Carson Farmer <br /> |...<br /> |- <br /> |Didier Leibovici <br /> |Spatial Data Mining, Spatial pattern &amp; interactions, multiscale data, uncertainty, integrated modelling, interoperability, environmental &amp; epidemiological applications<br /> |- <br /> |Erwan Bocher <br /> |...<br /> |- <br /> |Hervé Parmentier <br /> |...<br /> |- <br /> |Olivier Ertz <br /> |...<br /> |- <br /> |Stefan Steiniger <br /> |cartography, automated map generalization, pattern recognition, machine learning, cognition and perception, web (processing) services, general desktop GIS software developments, landscape ecology, GIS in education, geodesy<br /> |- <br /> |Bruce Ralston <br /> |...<br /> |- <br /> |Brandon Whitehead <br /> |...<br /> |- <br /> |Stefanie Andrae <br /> |volunteered geography, neogeography, personalized LBS, OGC web services (WMS, WFS, WCS, SOS), spatial databases<br /> |- <br /> |Harald Schernthanner <br /> |Geoprocessing, image processing, remote sensing, OS GIS in higher education<br /> |- <br /> |Rita Engemaier <br /> |cartography &amp; geovisualisation, multimedia design, web-mapping, cartographic animation, atlasinformation systems, OSS in higher education<br /> |- <br /> |Georg Gartner <br /> |cartography, LBS, web mapping<br /> |- <br /> |Artur Seara (GESLIG) <br /> |Cartography, Photogrammetry, Remote sensing, Cadastre, GIS, webmapping<br /> |- <br /> |Nadia Namini <br /> |...<br /> |- <br /> |Robert Feick <br /> |...<br /> |- <br /> |Bernd Resch <br /> |embedded geo-sensing, open standards for sensor webs, real-time data integration, web-based data analysis (incl. OGC WPS), (geo-)web services and standards<br /> |- <br /> |Marco Ciolli <br /> |Forest management and planning, Forest ecology, Tropical ecology, Dendrochronology, Landscape change, GIS in Forestry and ecology, FOSS in all education levels.<br /> |- <br /> |Paolo Zatelli <br /> |Signal and image processing, cartography, geodesy, geospatial web services, GIS software development, GIS education.<br /> |}<br /> <br /> <br /> [[Category:FOSS4G2009]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=FOSS4G_2009_Logo_Designs&diff=27008 2008-07-02T17:46:38Z

<p>Wiki-Danames: </p> <hr /> <div>These are the final options for FOSS4G Sydney logos.<br /> <br /> Could all FOSS4G2009 parties please add your votes before Friday 4 July 2008.<br /> <br /> =Logo Option 1=<br /> <br /> [http://www.tourhosts.com.au/download/foss4g/Option-1.gif Logo Option 1]<br /> <br /> Votes:<br /> * +1 Simon Hope<br /> * +1 [[User: Torsten Brassat | Torsten Brassat]]<br /> * +1 [[User: Astrid Emde]]<br /> * +1 [[User: Verena Diewald]]<br /> * +1 [[User: jmckenna | Jeff McKenna]]<br /> <br /> =Logo Option 2=<br /> <br /> [http://www.tourhosts.com.au/download/foss4g/foss4g_logo4a_whiteAU.gif Logo Option 2]<br /> <br /> Votes:<br /> * +1 Cameron Shorter<br /> * +1 [[User: danames | Dan Ames]] - Suggestion: use this one when a large logo is needed, and the other when a small logo is needed...</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=User:Danames&diff=25387 2008-05-28T20:38:16Z

<p>Wiki-Danames: </p> <hr /> <div>'''Daniel P. Ames, Ph.D., P.E.''' is a Professor of Geosciences at [http://www.isu.edu Idaho State University] at the Idaho Falls, Idaho campus. Dr. Ames is the program director for the ISU [http://giscenter.isu.edu/geotech/ Master's of Science] in Geographic Information Science and is the project leader for the open source [http://www.mapwindow.org/ MapWindow GIS] project. MapWindow GIS is a Microsoft .NET based, extensible desktop application used heavily in environmental modeling decision support systems in the United States and elsewhere. The MapWindow GIS project is working towards preparing an application for OSGeo incubator status. In the mean time, Dr. Ames is also helping with the [http://www.osgeo.org/journal OSGeo Journal] as associate editor for peer review. Dan's research and contact page is [http://www.hydromap.com www.hydromap.com].</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Dan_Ames&diff=25386 2008-05-28T20:37:44Z

<p>Wiki-Danames: Redirecting to User:Danames</p> <hr /> <div>#redirect[[User:Danames]]<br /> [[Category:OSGeo Member]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=User:Danames&diff=25385 2008-05-28T20:35:32Z

<p>Wiki-Danames: </p> <hr /> <div>'''Daniel P. Ames, Ph.D., P.E.''' is a Professor of Geosciences at [http://www.isu.edu Idaho State University] at the Idaho Falls, Idaho campus. Dr. Ames is the program director for the ISU [http://giscenter.isu.edu/geotech/ Master's of Science] in Geographic Information Science and is the project leader for the open source [http://www.mapwindow.org/ MapWindow GIS] project. MapWindow GIS is a Microsoft .NET based, extensible desktop application used heavily in environmental modeling decision support systems in the United States and elsewhere. The MapWindow GIS project is working towards preparing an application for OSGeo incubator status. In the mean time, Dr. Ames is also helping with the [http://www.osgeo.org/journal OSGeo Journal] as associate editor for peer review. Dan's research and contact page is [http://www.hydromap.com www.hydromap.com].<br /> <br /> [[Category:OSGeo Member]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=GeoConnexion_Column&diff=24989 2008-05-15T12:38:06Z

<p>Wiki-Danames: Added user link and submission date for Dan Ames article.</p> <hr /> <div>This is the home page for &quot;Open Sources&quot;, the OSGeo column in [http://www.geoconnexion.com/ GeoConnexion magazine]. Contact mpg if you're interested in helping out.<br /> <br /> <br /> ==Editorial Calender ==<br /> <br /> * (1) introductory column (Michael P. Gerlek) <br /> ** ''published May 2007'' [http://www.geoconnexion.com/uploads/opensources_intv6i5.pdf PDF]<br /> <br /> * (2) ossimPlanet (Mark Lucas)<br /> ** ''published June 2007'' [http://www.geoconnexion.com/uploads/opensources_intv6i6.pdf PDF]<br /> <br /> * (3) BigTIFF (Frank Warmerdam)<br /> ** ''published July/August 2007'' [http://www.geoconnexion.com/uploads/opensource_intv6i7.pdf PDF]<br /> <br /> * (4) TOPP/GeoServer (Chris Holmes)<br /> ** ''published September 2007'' [http://www.geoconnexion.com/uploads/opensources_intv6i8.pdf PDF]<br /> <br /> * (5) &quot;The Gift Economy Ain't Free: Getting Help with Open Source Software&quot; (Howard Butler and Chris Schmidt)<br /> ** ''published, October (or November?) 2007'' [http://www.geoconnexion.com/uploads/opensource_intv6i9.pdf PDF]<br /> <br /> * (6) OpenLayers + TileCache (Schuyler Erle)<br /> ** ''published, December 2007/January 2008'' [http://www.geoconnexion.com/uploads/opensource_intv7i1.pdf PDF]<br /> <br /> * (7) Mapbender ([[User:Arnulf Christl | Arnulf Christl]])<br /> ** ''published, February 2008'' [http://www.geoconnexion.com/uploads/mapbender_intv7i2.pdf PDF]<br /> <br /> * (8) GRASS ([[User:maltehm | Malte Halbey-Martin]])<br /> ** ''published, March 2008'' [http://www.geoconnexion.com/uploads/opensource_intv7i3.pdf PDF]<br /> <br /> * (9) MapServer (Steve Lime)<br /> ** ''published, April 2008'' [http://www.geoconnexion.com/uploads/opensource_intv7i4.pdf PDF]<br /> <br /> * (10) May 2008 -- GeoNetwork (Jeroen Ticheler)<br /> ** ''to be published, May 2008'' [http://www.geoconnexion.com/uploads/opensource_intv7i5.pdf PDF]<br /> <br /> * (11) June 2008 -- Public GeoData (Jo Walsh)<br /> ** ''to be published, May 2008'' (link not yet available)<br /> <br /> <br /> * (12) July 2008 -- MapBuilder, or maybe OpenSource/OpenStandards (Cameron Shorter)<br /> ** final copy due roughly 15 May 2008<br /> ** ''not yet started''<br /> <br /> * (13) August 2008 -- Commercial Models around Open Source (Dave McIlhagga)<br /> ** final copy due roughly 15 June 2008<br /> ** ''not yet started''<br /> <br /> * (14) September 2008 -- &quot;MapWindow GIS: Developer Tools for the .NET Platform&quot; ([[User:Danames | Daniel P. Ames]])<br /> ** final copy due roughly 15 July 2008<br /> ** ''Article submitted on May 14, 2008''<br /> <br /> * (15) October 2008 -- deegree and Spatial Data Infrastructues using FOSS (Markus Lupp and Jens Fitzke)<br /> ** final copy due roughly 15 August 2008<br /> ** ''not yet started''<br /> <br /> <br /> * Other Future Topics<br /> ** ChrisH: &quot;I could also do something like show how GeoTools fosters uDig and GeoServer and how play in to one another, advances in one get picked up by the others, in a virtuous circle.&quot;<br /> ** MapGuide, Bob Bray (did not respond to initial publication date)<br /> ** Education, PuneetK (did not respond to initial publication date)<br /> <br /> <br /> ==Editorial Notes==<br /> <br /> The following guidelines are from the GeoConnexions Editor (currently Roger Longhorn).<br /> <br /> '''(1)''' A column in our magazine is 1 page in length. An example is [http://www.geoconnexion.com/uploads/kevinpomfret_intv6i1.pdf here]. Total number of words is about 800. It can be less but not more. If you wish to add an image, then shoot for around 600 words. Try to include the writer's pic at 300 dpi and their affiliation and email - this lets readers identify with the person writing and provides a point of contact.<br /> <br /> '''(2)''' Images are a big issue for hardcopy print, especially computer images because they are only 72 dpi usually. Print quality is 300 dpi. That means 300 pixels per square inch for the print process. Most screen captures are reduced to 1/5th their original size when printed - usually causing us to throw them out because they represent the content poorly. Stretching a 72 dpi image to resize it means one still ends up with a 72 dpi image, only bigger. Please aim for 300 dpi if submitting images.<br /> <br /> '''(3)''' Content - My policy is to support expression. Someone writes it, I'll support it. I only edit for spelling, grammar and what I consider to be outright libelous. The writer should stand behind their expression. As I mentioned earlier, I am not a programmer. I need your help to peer review programming content (which is why the 'contact point' ) will work well. Ultimately everything in the column will reflect on OSGeo. It's your column, you choose the content. Our Media Pack describes Themes for issues by edition throughout the year. I use these as a guideline.<br /> <br /> '''(4)''' Reprint - I am a supporter of the creator maintaining all rights. Whomever submits material owns it as far as I am concerned. All I ask is that we have first right to print (we compete on the basis originality). Once printed, you may do whatever you wish with the material, you own it. We usually archive it online and columns are available for distribution online. Since hardcopy prints are a fixed cost, they can be purchased if anyone wants a few hundred. I don't know the cost, a marketing person can help if needed. Our Media Pack is [http://www.geoconnexion.com/downloads/media_pack2007.pdf here].<br /> <br /> '''(5)''' Timeline - I am usually working 90-100 days ahead of time. Be aware that there is delay in hardcopy and get material in early. On the flip side, we publish our articles to online almost immediately after hardcopy production.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal&diff=23685 2008-03-21T23:33:50Z

<p>Wiki-Danames: /* Submission of articles */</p> <hr /> <div>The [http://www.osgeo.org/journal '''OSGeo Journal'''] is a publication highlighting open source projects, news, event and other OSGeo Foundation updates. This is the working page for the Journal project and its future editions. See the official [http://www.osgeo.org/journal/ OSGeo Journal homepage] for links to the published journal and articles.<br /> <br /> [[Journal Volume 4]] is in preparation, edit [[Journal Volume 5]] page if you would like to submit an article. An editor will contact you when it is time to prepare for the publication.<br /> <br /> == Content Sections and Editors ==<br /> The Journal has several volunteers that collect, edit, format articles and design/proof layout. Because layout is currently done using [http://www.latex-project.org/ LaTeX], more volunteers familiar with it are always appreciated. By having several editors and categories we spread the word out and reduce the overall load for each volunteer.<br /> <br /> Editorial duties include:<br /> <br /> * looking through submitted articles<br /> * doing a brief review and perhaps fwd. them to another more experienced user/developer or other Reviewer<br /> * asking certain projects to submit articles (for volumes covering one subject)<br /> * check for layout errors, so that the final files can easily be merged with all other sections<br /> * optionally converting content to LaTeX if needed<br /> <br /> This is the typical outline for an edition:<br /> {|class=&quot;toccolours&quot; style=&quot;border:1px solid #a3bfb1; background:#cef2e0;&quot; <br /> |-<br /> ! width=&quot;150&quot; | Section<br /> ! width=&quot;100&quot; | Editor<br /> ! Length<br /> ! Description<br /> |-<br /> | Editorial<br /> | [[User:Tmitchell | Tyler Mitchell]]<br /> | 1/2 page<br /> | Written by Editor in Chief or invited guest<br /> |-<br /> | News<br /> | [[User:Jfournier | Jason Fournier]]<br /> | 1 page<br /> | Past 6 months or news items<br /> |-<br /> | Event Reports<br /> | [[User:jmckenna | Jeff McKenna]]<br /> | 750 words<br /> | Brief article about meetings/conferences<br /> |-<br /> | Project Introductions<br /> | [[User:Wegmann | Martin Wegmann]]<br /> | 1500 words<br /> | General introduction to one software project or particular new features of a project<br /> |-<br /> | Case Studies<br /> | [mailto:micha@arava.co.il Micha Silver]<br /> | 1500 words<br /> | Highlighting specific application of technologies to a certain problem, user community or developer needs<br /> |-<br /> | Integration Studies<br /> | [[User:Wegmann | Martin Wegmann]]<br /> | 2500 words<br /> | Articles showing how many projects can work together in an integrated fashion, e.g. the power of GRASS, QGIS and GDAL all working together<br /> |-<br /> | Topical Studies<br /> | [[User:MarkusLupp | Dr. Markus Lupp]]<br /> | 1500 words<br /> | Introductions to concepts and theories, e.g. what something means, how to work with certain types of things<br /> |-<br /> | Programming Tutorials<br /> | [mailto:sunburned.surveyor@gmail.com Landon Blake] <br /> | 1500 words<br /> | Tutorials showing how to use a library or application at a programmatic level<br /> |-<br /> | Interviews<br /> | ''vacant''<br /> | 1000 words<br /> | Introducing open source community members or organisations<br /> |- <br /> | Sponsor Perspectives<br /> | ''vacant''<br /> | 1500 words<br /> | Introducing open source community members or organisations<br /> |-<br /> | Developer Announcements<br /> | [[User:Kotzino | Dimitris Kotzinos]]<br /> | 750 words<br /> | Announcements about recent changes/improvements to projects<br /> |-<br /> | Local Chapter Reports<br /> | [[User:Mleslie | Mark Leslie]]<br /> | 750 words<br /> | Reports submitted by representatives of local chapters<br /> |-<br /> | Proof Reading<br /> | [[User:Acarr | Angus Carr]]<br /> |<br /> | Proofing finals, along with other reviewers (below)<br /> |-<br /> | Peer Review<br /> | [[User:Danames | Dan Ames]]<br /> |<br /> | Editor in charge of peer review<br /> |-<br /> | Layout/Design<br /> | Kevin Yam<br /> |<br /> |<br /> |-<br /> |}<br /> <br /> === Open Positions ===<br /> Interested in helping? This section lists current positions that need filling. If you have other interests, you are also welcome to add them for discussion.<br /> * '''Editor, Interviews'''<br /> * '''Editor, Sponsor Perspectives'''<br /> * '''Spell/grammer-checker'''<br /> * '''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.<br /> * '''Formatting/Conversion''' - moving non-LaTeX content into LaTeX forms (each author/section Edt.has to check for latex errors etc.)<br /> * '''Sponsor''' - interested in sponsoring the newsletter creation?<br /> <br /> == Reviewers ==<br /> <br /> Please list yourself below with name, e-mail and field of expertise to review certain articles - individual editors will contact you if necessary:<br /> <br /> * [mailto:sunburned.surveyor@gmail.com Landon Blake] - Coordinate Geometry, Geodesy, Surveying, Applications of GIS to Public Works and Parcel/Cadastral Records Management<br /> * [mailto:micha@arava.co.il Micha Silver] - Using GIS and GPS in agricultural pest control projects; watershed analysis<br /> * [mailto:dan.putler@sauder.ubc.ca Dan Putler] - Application of GIS to marketing, retailing, and other business problems; geo-statistics.<br /> * [mailto:yann.chemin@gmail.com Yann Chemin] - Satellite image processing, evapotranspiration/crop models, multi-temporal/scale, spatio-temporal, data assimilation.<br /> * [[User:MarkusLupp | Dr. Markus Lupp]] - Spatial Data Infrastructures (SDI), standards and processes of the OGC, Application of GIS to disaster management, urban planning and natural resource management.<br /> * [mailto:ploewe@gfz-potsdam.de Dr. Peter Löwe] - GRASS GIS, Sensor Web Enablement, Ontologies, Expert Systems, (Distributed) Artificial Intelligence, Nature Interpretation.<br /> * [[User:Smitch | Dr. Scott Mitchell]] - GRASS GIS, environmental modelling (especially biogeochemical, habitat, land use/land cover), spatial data analysis, spatial aggregation, decision support.<br /> * [mailto:kotzino@csd.uoc.gr Dr. Dimitris Kotzinos] - Web GIS, mobile GIS, development of GIS and for GIS packages, semantic web and semantics in GIS, decision support systems.<br /> <br /> == Submission of articles ==<br /> Please start by reading our [http://wiki.osgeo.org/index.php/Journal_License_and_Guidelines guidlelines] for details about licensing and content.<br /> <br /> Your article should be written in [http://www.latex-project.org/ Latex]. For instructions which format/style shall be used, please have a look at this working [http://grass.itc.it/newsletter/GRASSnewsletter_template.tar.gz 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 [http://www.stdout.org/~winston/latex/ Latex Cheat Sheet] to get to know a few commands, e.g. how to enumerate, make tables etc.<br /> Please send your zipped document to the respective Editors (see above).<br /> <br /> If Latex is a problem for you or your article, please discuss it with your editor. At their discretion, editors can choose to help you convert your content into a suitable format for publishing.<br /> <br /> '''Original Research and Technical Papers'''<br /> <br /> All Original Research and Technical Papers are peer reviewed by volunteer reviewers in the OSGeo community. Please consider submitting your manuscripts for publication in OSGeo Journal. Original Research and Technical Papers should be submitted through the [OJS system http://www.osgeo.org/ojs].<br /> <br /> == Newsletter Software ==<br /> <br /> Based on GRASS-News (which was based on R News) Latex is recommended, but other publishing packages might be considered for forthcoming issues. (For example, [http://www.scribus.net Scribus] has been recommended.)<br /> <br /> 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):<br /> <br /> '''links to templates will go here'''<br /> * template for article<br /> ** template for inserting images<br /> ** template for inserting tables<br /> <br /> They can be copied from [http://grass.itc.it/newsletter/GRASSnewsletter_template.tar.gz GRASS-News LaTex template].<br /> <br /> == Process ==<br /> # Confirm editors/volunteers<br /> # Set deadlines<br /> # Solicit articles<br /> # Collect/edit/review articles<br /> # Format to LaTeX<br /> # Produce draft<br /> # Set deadline for review<br /> # Revisions<br /> # Final production<br /> # Press Release and promotion<br /> <br /> == Online Location ==<br /> OSGeo Journal team uses a subversion code repository for managing content for the publication.<br /> It can be accessed publicly [http://svn.osgeo.org/osgeo/journal here].<br /> <br /> == Background ==<br /> The OSGeo Journal builds on top of the successful history of the [http://grass.itc.it/newsletter/index.php GRASS-News] production. [http://osgeo.org/files/news/GRASS_OSGeo_News_vol4.pdf Volume 4] (5.8MB) of that production was a joint GRASS/OSGeo effort. Subsequent editions are broader and branded as OSGeo Journal.<br /> <br /> [[Category:Newsletter]]<br /> [[Category:Journal]]<br /> [[Category:Advocacy]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal_Volume_5&diff=23684 2008-03-21T23:31:31Z

<p>Wiki-Danames: Updated information under Original Research and Technical Papers</p> <hr /> <div>This is the planning and work page for the OSGeo [[Journal]] - Volume 5 publication. <br /> <br /> If you want to contribute an article, add it to this list in the appropriate category. <br /> <br /> '''Please review the [[Journal License and Guidelines]] page before adding your article to either article list.'''<br /> <br /> ------<br /> <br /> == Deadlines ==<br /> '''Deadlines will be set after [[Journal Volume 4]] is completed and published.''' &lt;br&gt;There will also be a break/review/re-grouping period for the [[Journal]] team of 2-3 months beforehand.<br /> * Articles welcome: '''Now'''<br /> * Articles requiring peer review, Submission Ends: '''TBD'''<br /> * Article Submission Ends: '''TBD'''<br /> * First Draft: '''TBD'''<br /> * Final Publication: '''TBD'''<br /> <br /> ------<br /> <br /> == Contributors / Topics ==<br /> See [[Journal]] for definition of the following categories. Add yourself if you are interested. Note that all categories don't have to be filled, so this serves as a rough outline for the types of content we generally hope to have.<br /> <br /> === Editorials ===<br /> # Tyler Mitchell: '''General updates'''<br /> <br /> === News ===<br /> # Editor: Jason Fournier<br /> # Author: ...<br /> # ...<br /> <br /> === Event Reports (2-3 articles) ===<br /> # ...<br /> <br /> === Project Introductions (1-2 articles) ===<br /> # ...<br /> <br /> === Case Studies (2-3 articles) ===<br /> # ...<br /> <br /> === Integration Studies (2-3 articles) ===<br /> # ...<br /> <br /> === Topical Studies (1-2 articles) ===<br /> # Markus Neteler: '''Open Source Quality Assessment System: The GRASS Case''' (about [http://grass.itc.it/devel/index.php#quality GRASS-QA])<br /> # ...<br /> <br /> === Programming Tutorials (1-2 articles) ===<br /> # ...<br /> <br /> === Interview(s) ===<br /> # ...<br /> <br /> === Developer Announcements ===<br /> # OSGeo project summaries<br /> # OSGeo Local Chapter updates<br /> # ...<br /> <br /> === Original Research and Technical Papers ===<br /> All Original Research and Technical Papers are peer reviewed by volunteer reviewers in the OSGeo community. Please consider submitting your manuscripts for publication in OSGeo Journal. Original Research and Technical Papers should be submitted through the [OJS system http://www.osgeo.org/ojs].<br /> <br /> [[Category:Journal]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal&diff=23394 2008-03-10T21:33:47Z

<p>Wiki-Danames: Added user link to Ames</p> <hr /> <div>The [http://www.osgeo.org/journal '''OSGeo Journal'''] is a publication highlighting open source projects, news, event and other OSGeo Foundation updates. This is the working page for the Journal project and its future editions. See the official [http://www.osgeo.org/journal/ OSGeo Journal homepage] for links to the published journal and articles.<br /> <br /> [[Journal Volume 4]] is in preparation, edit [[Journal Volume 5]] page if you would like to submit an article. An editor will contact you when it is time to prepare for the publication.<br /> <br /> == Content Sections and Editors ==<br /> The Journal has several volunteers that collect, edit, format articles and design/proof layout. Because layout is currently done using [http://www.latex-project.org/ LaTeX], more volunteers familiar with it are always appreciated. By having several editors and categories we spread the word out and reduce the overall load for each volunteer.<br /> <br /> Editorial duties include:<br /> <br /> * looking through submitted articles<br /> * doing a brief review and perhaps fwd. them to another more experienced user/developer or other Reviewer<br /> * asking certain projects to submit articles (for volumes covering one subject)<br /> * check for layout errors, so that the final files can easily be merged with all other sections<br /> * optionally converting content to LaTeX if needed<br /> <br /> This is the typical outline for an edition:<br /> {|class=&quot;toccolours&quot; style=&quot;border:1px solid #a3bfb1; background:#cef2e0;&quot; <br /> |-<br /> ! width=&quot;150&quot; | Section<br /> ! width=&quot;100&quot; | Editor<br /> ! Length<br /> ! Description<br /> |-<br /> | Editorial<br /> | [[User:Tmitchell | Tyler Mitchell]]<br /> | 1/2 page<br /> | Written by Editor in Chief or invited guest<br /> |-<br /> | News<br /> | [[User:Jfournier | Jason Fournier]]<br /> | 1 page<br /> | Past 6 months or news items<br /> |-<br /> | Event Reports<br /> | [[User:jmckenna | Jeff McKenna]]<br /> | 750 words<br /> | Brief article about meetings/conferences<br /> |-<br /> | Project Introductions<br /> | [[User:Wegmann | Martin Wegmann]]<br /> | 1500 words<br /> | General introduction to one software project or particular new features of a project<br /> |-<br /> | Case Studies<br /> | [mailto:micha@arava.co.il Micha Silver]<br /> | 1500 words<br /> | Highlighting specific application of technologies to a certain problem, user community or developer needs<br /> |-<br /> | Integration Studies<br /> | [[User:Wegmann | Martin Wegmann]]<br /> | 2500 words<br /> | Articles showing how many projects can work together in an integrated fashion, e.g. the power of GRASS, QGIS and GDAL all working together<br /> |-<br /> | Topical Studies<br /> | [[User:MarkusLupp | Dr. Markus Lupp]]<br /> | 1500 words<br /> | Introductions to concepts and theories, e.g. what something means, how to work with certain types of things<br /> |-<br /> | Programming Tutorials<br /> | [mailto:sunburned.surveyor@gmail.com Landon Blake] <br /> | 1500 words<br /> | Tutorials showing how to use a library or application at a programmatic level<br /> |-<br /> | Interviews<br /> | ''vacant''<br /> | 1000 words<br /> | Introducing open source community members or organisations<br /> |- <br /> | Sponsor Perspectives<br /> | ''vacant''<br /> | 1500 words<br /> | Introducing open source community members or organisations<br /> |-<br /> | Developer Announcements<br /> | [[User:Kotzino | Dimitris Kotzinos]]<br /> | 750 words<br /> | Announcements about recent changes/improvements to projects<br /> |-<br /> | Local Chapter Reports<br /> | [[User:Mleslie | Mark Leslie]]<br /> | 750 words<br /> | Reports submitted by representatives of local chapters<br /> |-<br /> | Proof Reading<br /> | [[User:Acarr | Angus Carr]]<br /> |<br /> | Proofing finals, along with other reviewers (below)<br /> |-<br /> | Peer Review<br /> | [[User:Danames | Dan Ames]]<br /> |<br /> | Editor in charge of peer review<br /> |-<br /> | Layout/Design<br /> | Kevin Yam<br /> |<br /> |<br /> |-<br /> |}<br /> <br /> === Open Positions ===<br /> Interested in helping? This section lists current positions that need filling. If you have other interests, you are also welcome to add them for discussion.<br /> * '''Editor, Interviews'''<br /> * '''Editor, Sponsor Perspectives'''<br /> * '''Spell/grammer-checker'''<br /> * '''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.<br /> * '''Formatting/Conversion''' - moving non-LaTeX content into LaTeX forms (each author/section Edt.has to check for latex errors etc.)<br /> * '''Sponsor''' - interested in sponsoring the newsletter creation?<br /> <br /> == Reviewers ==<br /> <br /> Please list yourself below with name, e-mail and field of expertise to review certain articles - individual editors will contact you if necessary:<br /> <br /> * [mailto:sunburned.surveyor@gmail.com Landon Blake] - Coordinate Geometry, Geodesy, Surveying, Applications of GIS to Public Works and Parcel/Cadastral Records Management<br /> * [mailto:micha@arava.co.il Micha Silver] - Using GIS and GPS in agricultural pest control projects; watershed analysis<br /> * [mailto:dan.putler@sauder.ubc.ca Dan Putler] - Application of GIS to marketing, retailing, and other business problems; geo-statistics.<br /> * [mailto:yann.chemin@gmail.com Yann Chemin] - Satellite image processing, evapotranspiration/crop models, multi-temporal/scale, spatio-temporal, data assimilation.<br /> * [[User:MarkusLupp | Dr. Markus Lupp]] - Spatial Data Infrastructures (SDI), standards and processes of the OGC, Application of GIS to disaster management, urban planning and natural resource management.<br /> * [mailto:ploewe@gfz-potsdam.de Dr. Peter Löwe] - GRASS GIS, Sensor Web Enablement, Ontologies, Expert Systems, (Distributed) Artificial Intelligence, Nature Interpretation.<br /> * [[User:Smitch | Dr. Scott Mitchell]] - GRASS GIS, environmental modelling (especially biogeochemical, habitat, land use/land cover), spatial data analysis, spatial aggregation, decision support.<br /> * [mailto:kotzino@csd.uoc.gr Dr. Dimitris Kotzinos] - Web GIS, mobile GIS, development of GIS and for GIS packages, semantic web and semantics in GIS, decision support systems.<br /> <br /> == Submission of articles ==<br /> Please start by reading our [http://wiki.osgeo.org/index.php/Journal_License_and_Guidelines guidlelines] for details about licensing and content.<br /> <br /> Your article should be written in [http://www.latex-project.org/ Latex]. For instructions which format/style shall be used, please have a look at this working [http://grass.itc.it/newsletter/GRASSnewsletter_template.tar.gz 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 [http://www.stdout.org/~winston/latex/ Latex Cheat Sheet] to get to know a few commands, e.g. how to enumerate, make tables etc.<br /> Please send your zipped document to the respective Editors (see above).<br /> <br /> If Latex is a problem for you or your article, please discuss it with your editor. At their discretion, editors can choose to help you convert your content into a suitable format for publishing.<br /> <br /> == Newsletter Software ==<br /> <br /> Based on GRASS-News (which was based on R News) Latex is recommended, but other publishing packages might be considered for forthcoming issues. (For example, [http://www.scribus.net Scribus] has been recommended.)<br /> <br /> 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):<br /> <br /> '''links to templates will go here'''<br /> * template for article<br /> ** template for inserting images<br /> ** template for inserting tables<br /> <br /> They can be copied from [http://grass.itc.it/newsletter/GRASSnewsletter_template.tar.gz GRASS-News LaTex template].<br /> <br /> == Process ==<br /> # Confirm editors/volunteers<br /> # Set deadlines<br /> # Solicit articles<br /> # Collect/edit/review articles<br /> # Format to LaTeX<br /> # Produce draft<br /> # Set deadline for review<br /> # Revisions<br /> # Final production<br /> # Press Release and promotion<br /> <br /> == Online Location ==<br /> OSGeo Journal team uses a subversion code repository for managing content for the publication.<br /> It can be accessed publicly [http://svn.osgeo.org/osgeo/journal here].<br /> <br /> == Background ==<br /> The OSGeo Journal builds on top of the successful history of the [http://grass.itc.it/newsletter/index.php GRASS-News] production. [http://osgeo.org/files/news/GRASS_OSGeo_News_vol4.pdf Volume 4] (5.8MB) of that production was a joint GRASS/OSGeo effort. Subsequent editions are broader and branded as OSGeo Journal.<br /> <br /> [[Category:Newsletter]]<br /> [[Category:Journal]]<br /> [[Category:Advocacy]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=User:Danames&diff=23393 2008-03-10T21:31:52Z

<p>Wiki-Danames: New user page for Dan Ames</p> <hr /> <div>'''Daniel P. Ames, Ph.D., P.E.''' is a Professor of Geosciences at [http://www.isu.edu Idaho State University] at the Idaho Falls, Idaho campus. Dr. Ames is the program director for the ISU [http://giscenter.isu.edu/geotech/ Master's of Science] in Geographic Information Science and is the project leader for the open source [http://www.mapwindow.org/ MapWindow GIS] project. MapWindow GIS is a Microsoft .NET based, extensible desktop application used heavily in environmental modeling decision support systems in the United States and elsewhere. The MapWindow GIS project is working towards preparing an application for OSGeo incubator status. In the mean time, Dr. Ames is also helping with the [http://www.osgeo.org/journal OSGeo Journal] as associate editor for peer review. Dan's research and contact page is [http://www.hydromap.com www.hydromap.com].</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Talk:Jobs_Board&diff=22823 2008-02-18T21:13:04Z

<p>Wiki-Danames: New page: I'm not sure if I'm reading this right, but the one job that is posted is under the &quot;resume's&quot; sub heading. Is that intentional? Seems it should be under the other heading. - Dan</p> <hr /> <div>I'm not sure if I'm reading this right, but the one job that is posted is under the &quot;resume's&quot; sub heading. Is that intentional? Seems it should be under the other heading. - Dan</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal_Volume_2&diff=16054 2007-07-06T20:29:15Z

<p>Wiki-Danames: /* Project Introductions (1-2 articles) */</p> <hr /> <div>This is the planning and work page for the OSGeo [[Journal]] - Volume 2 publication. <br /> <br /> If you want to contribute an article, add it to this list in the appropriate category. Please review the [[Journal License and Guidelines]] page first.<br /> <br /> ------<br /> <br /> == Deadlines ==<br /> * Articles welcome: Now<br /> * Article drafts: June 22, 2007<br /> * Article Submission Ends: July 3, 2007 (~30 days to submit)<br /> * First Draft: July 22, 2007<br /> * Final Publication: August 1, 2007 (~30 days from article close)<br /> <br /> == Contributors / Topics ==<br /> See [[Journal]] for definition of the following categories. Add yourself if you are interested. Also review our [http://wiki.osgeo.org/index.php/Journal_License_and_Guidelines guidelines] for contributors. Note that all categories don't have to be filled, so this serves as a rough outline for the types of content we generally hope to have.<br /> <br /> === Editorials === <br /> # Tyler Mitchell: '''General updates'''<br /> <br /> === News ===<br /> # Editor:[[User:jfournier | Jason Fournier]]<br /> # Jeff McKenna: '''FOSS4G 2008 Venue''': announcing conference committee event updates<br /> # Additional contributors welcome...<br /> <br /> === Event Reports (2-3 articles) ===<br /> # Editor: [[User:jmckenna | Jeff McKena]]<br /> # Ravi Kumar: '''FOSS GIS in India''': A Report from the first meeting of the India chapter of OSGeo<br /> # Yves Jacolin: '''GeoEvenement 2007''': A [http://wiki.osgeo.org/index.php/GeoEvenement2007 summary] of OSGeo promotion at a french geomatics tradeshow<br /> <br /> === Project Introductions (1-2 articles) ===<br /> # Editor: [[User:Wegmann | Martin Wegmann]]<br /> # Schuyler Erle: '''OpenLayers''' ('''confirmed''')<br /> # Scott Emmons: '''Flexible Internet Spatial Template (FIST)''': a MapServer-based web mapping framework (title TBD)<br /> # Daniel P. Ames: '''MapWindow''': Introducing the MapWindow GIS project ('''confirmed''')<br /> # Jeroen Ticheler: '''GeoNetwork OpenSource''': The FAO GeoNetwork ('''confirmed''')<br /> <br /> === Case Studies (2-3 articles) ===<br /> # Editor: [mailto:micha@arava.co.il Micha Silver]<br /> # Joel Schlagel: title TBD<br /> # [mailto:shamimakhterATgmail.com Shamim Akhter] &amp; [mailto:yann.cheminATgmail.com Yann Chemin]: Porting a GRASS raster module to distributed computing<br /> # Rafael Sperb: Fisheries Tracking System (title TBD)<br /> # David Enns: MapServer-related project example (title TBD)<br /> # Giuliano Cecchi and Raffaele C. Mattioli: The role of FAO GeoNetwork in a multinational development programme: the case of the Programme Against African Trypanosomiasis<br /> # Sina Ayanlade: Geospatial Data Acquisition Problems in Sub-Saharan Africa<br /> # ...<br /> <br /> === Integration Studies (2-3 articles) ===<br /> # Editor: [[User:Wegmann | Martin Wegmann]]<br /> # <br /> <br /> === Topical Studies (1-2 articles) ===<br /> # Acting Editor: [[User:tmitchell | Tyler Mitchell]]<br /> # Landon Blake: '''Spatial Relationships - An Introduction to Topology'''<br /> # ...<br /> <br /> === Programming Tutorials (1-2 articles) ===<br /> # Editor: Landon Blake<br /> # Tim Sutton: Programming Using the QGIS API (title TBD)<br /> <br /> === Interview(s) ===<br /> # Acting Editor: [[User:tmitchell | Tyler Mitchell]]<br /> # Matthew Fleagle and Michael P. Gerlek, LizardTech: '''Why We Use and Support Free and Open Source Software'''<br /> <br /> === Developer Announcements ===<br /> # Acting Editor: [[User:tmitchell | Tyler Mitchell]]<br /> # OSGeo project summaries<br /> # Markus Mueller: So simple to install: deegree releases 2.1 demos as WAR archives (before or after Local chapter updates?)<br /> # ...<br /> <br /> === Local Chapter Updates ===<br /> # Acting Editor: [[User:tmitchell | Tyler Mitchell]]<br /> # OSGeo Local Chapter updates<br /> ## [[Journal Volume 2 Spanish Local Chapter| Spanish Local Chapter]]<br /> ## [[Journal Volume 2 Ottawa Local Chapter| Ottawa Local Chapter]]<br /> ## [[Journal Volume 2 Francophone Local Chapter|Francophone Local Chapter]]<br /> <br /> [[Category:Newsletter]]<br /> [[Category:Journal]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal_Peer_Review&diff=14820 2007-05-27T00:01:15Z

<p>Wiki-Danames: </p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> == Paper Identification ==<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence a simple header or footer will be added to any peer reviewed papers indicating this, but these papers will be integrated within other sections of the Journal as determined by the Editor.<br /> <br /> == Review Process ==<br /> For the peer reviewed papers, the following review process is proposed:<br /> <br /> # OSGeo Journal Editor in Chief and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an Associate Editor, Peer Review.<br /> # Call for papers is posted on the OSGeo discuss and announcement mailing lists and web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. In general, the same types of papers are invited as usually fits the Journal criteria, but in this case the author can choose whether to opt-in for peer review, if available.<br /> # A [[call for reviewers]] is also posted, and a list of potential reviewers is maintained on the WIKI (this will likely not be a comprehensive list since some reviewers may prefer total anonymity).<br /> # Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration). This can be the same wiki page used for a Journal issue's list of articles.<br /> # AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> #Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as: <br /> ## &quot;Does the paper fit within the scope of OSGeo Journal?&quot; <br /> ## &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot;<br /> ## &quot;Is the paper well written?&quot; <br /> ## &quot;Does the paper use correct English spelling, syntax and grammar?&quot; <br /> ## &quot;Is the title appropriate?&quot;<br /> ## &quot;Is the abstract succinct of the correct length and appropriate?&quot; <br /> ## &quot;Are the citations complete and correct?&quot; <br /> ## &quot;Are all of the figures and tables necessary, clear and informative?&quot; <br /> ## &quot;Do you have any suggestions for the authors that would improve the paper?&quot; <br /> ## &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> # Reviewers are given four weeks to submit reviews.<br /> # The AE notifies the authors of the reviewers decision as follows: <br /> ## If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> ## If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> ## If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> ## If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> == Specifics for OSGeo Journal Volume 1, Issue 2 ==<br /> <br /> A test peer review process for the second issue of OSGeo Journal will track the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Call_for_reviewers&diff=14819 2007-05-26T23:59:09Z

<p>Wiki-Danames: initial entry.</p> <hr /> <div>== Call for OSGeo Journal Reviewers ==<br /> <br /> Attention OSGeo Community! We need your help. Please list yourself below if you are willing to be an anonymous peer reviewer for OSGeo peer reviewed papers. Please list your areas of expertise in parentheses and create an external link to your personal contact information web page. Journal reviewers will be asked to review papers that fit within their expertise areas and with which they have no direct conflict of interest. Generally this means that the reviewer is not a coauthor or funding source for the paper. Beyond this, please use your own judgment as to when it is appropriate to self eliminate yourself as a reviewer. Indeed, it is hoped that rather than simply accepting all review requests, you will also suggest alternative reviewers who might be willing and qualified. In this way, it is hoped that the following list will grow rapidly to include a large community of willing and able reviewers for this journal.<br /> <br /> == List of Reviewers ==<br /> <br /> Note: This list is not comprehensive and it is likely that any particular manuscript will be reviewed by some combination of individuals on this list and others who are willing to review, but prefer not to be listed. If you are a new reviewer, please consider listing yourself and your expertise below, perhaps in alphabetical order by surname. <br /> <br /> * [http://www.hydromap.com/ Ames, Daniel] - Acting Associate Editor, Peer Review (Hydrology, Modeling, MapWindow GIS, .NET Development)</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal_Peer_Review&diff=14818 2007-05-26T23:41:02Z

<p>Wiki-Danames: /* Review Process */</p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> == Paper Identification ==<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence a simple header or footer will be added to any peer reviewed papers indicating this, but these papers will be integrated within other sections of the Journal as determined by the Editor.<br /> <br /> == Review Process ==<br /> For the peer reviewed papers, the following review process is proposed:<br /> <br /> # OSGeo Journal Editor in Chief and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an Associate Editor, Peer Review.<br /> # Call for papers is posted on the OSGeo discuss and announcement mailing lists and web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. In general, the same types of papers are invited as usually fits the Journal criteria, but in this case the author can choose whether to opt-in for peer review, if available.<br /> # A [[call for reviewers]] is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> # Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration). This can be the same wiki page used for a Journal issue's list of articles.<br /> # AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> #Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as: <br /> ## &quot;Does the paper fit within the scope of OSGeo Journal?&quot; <br /> ## &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot;<br /> ## &quot;Is the paper well written?&quot; <br /> ## &quot;Does the paper use correct English spelling, syntax and grammar?&quot; <br /> ## &quot;Is the title appropriate?&quot;<br /> ## &quot;Is the abstract succinct of the correct length and appropriate?&quot; <br /> ## &quot;Are the citations complete and correct?&quot; <br /> ## &quot;Are all of the figures and tables necessary, clear and informative?&quot; <br /> ## &quot;Do you have any suggestions for the authors that would improve the paper?&quot; <br /> ## &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> # Reviewers are given four weeks to submit reviews.<br /> # The AE notifies the authors of the reviewers decision as follows: <br /> ## If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> ## If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> ## If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> ## If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> == Specifics for OSGeo Journal Volume 1, Issue 2 ==<br /> <br /> A test peer review process for the second issue of OSGeo Journal will track the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal_Peer_Review&diff=14817 2007-05-26T23:33:00Z

<p>Wiki-Danames: /* Specifics for OSGeo Journal Volume 1, Issue 2 */</p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> == Paper Identification ==<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence a simple header or footer will be added to any peer reviewed papers indicating this, but these papers will be integrated within other sections of the Journal as determined by the Editor.<br /> <br /> == Review Process ==<br /> For the peer reviewed papers, the following review process is proposed:<br /> <br /> # OSGeo Journal Editor in Chief and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an Associate Editor, Peer Review.<br /> # Call for papers is posted on the OSGeo discuss and announcement mailing lists and web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. In general, the same types of papers are invited as usually fits the Journal criteria, but in this case the author can choose whether to opt-in for peer review, if available.<br /> # A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> # Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration). This can be the same wiki page used for a Journal issue's list of articles.<br /> # AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> #Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as: <br /> ## &quot;Does the paper fit within the scope of OSGeo Journal?&quot; <br /> ## &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot;<br /> ## &quot;Is the paper well written?&quot; <br /> ## &quot;Does the paper use correct English spelling, syntax and grammar?&quot; <br /> ## &quot;Is the title appropriate?&quot;<br /> ## &quot;Is the abstract succinct of the correct length and appropriate?&quot; <br /> ## &quot;Are the citations complete and correct?&quot; <br /> ## &quot;Are all of the figures and tables necessary, clear and informative?&quot; <br /> ## &quot;Do you have any suggestions for the authors that would improve the paper?&quot; <br /> ## &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> # Reviewers are given four weeks to submit reviews.<br /> # The AE notifies the authors of the reviewers decision as follows: <br /> ## If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> ## If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> ## If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> ## If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> == Specifics for OSGeo Journal Volume 1, Issue 2 ==<br /> <br /> A test peer review process for the second issue of OSGeo Journal will track the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal_Peer_Review&diff=14816 2007-05-26T23:30:58Z

<p>Wiki-Danames: /* Paper Categorization */</p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> == Paper Identification ==<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence a simple header or footer will be added to any peer reviewed papers indicating this, but these papers will be integrated within other sections of the Journal as determined by the Editor.<br /> <br /> == Review Process ==<br /> For the peer reviewed papers, the following review process is proposed:<br /> <br /> # OSGeo Journal Editor in Chief and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an Associate Editor, Peer Review.<br /> # Call for papers is posted on the OSGeo discuss and announcement mailing lists and web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. In general, the same types of papers are invited as usually fits the Journal criteria, but in this case the author can choose whether to opt-in for peer review, if available.<br /> # A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> # Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration). This can be the same wiki page used for a Journal issue's list of articles.<br /> # AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> #Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as: <br /> ## &quot;Does the paper fit within the scope of OSGeo Journal?&quot; <br /> ## &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot;<br /> ## &quot;Is the paper well written?&quot; <br /> ## &quot;Does the paper use correct English spelling, syntax and grammar?&quot; <br /> ## &quot;Is the title appropriate?&quot;<br /> ## &quot;Is the abstract succinct of the correct length and appropriate?&quot; <br /> ## &quot;Are the citations complete and correct?&quot; <br /> ## &quot;Are all of the figures and tables necessary, clear and informative?&quot; <br /> ## &quot;Do you have any suggestions for the authors that would improve the paper?&quot; <br /> ## &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> # Reviewers are given four weeks to submit reviews.<br /> # The AE notifies the authors of the reviewers decision as follows: <br /> ## If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> ## If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> ## If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> ## If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> == Specifics for OSGeo Journal Volume 1, Issue 2 ==<br /> <br /> I think it is possible that we could initiate a test peer review process for the second issue of OSGeo Journal and would propose the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal_Peer_Review&diff=14815 2007-05-26T23:30:04Z

<p>Wiki-Danames: </p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> == Paper Categorization ==<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence a simple header or footer will be added to any peer reviewed papers indicating this, but these papers will be integrated within other sections of the Journal as determined by the Editor.<br /> <br /> == Review Process ==<br /> For the peer reviewed papers, the following review process is proposed:<br /> <br /> # OSGeo Journal Editor in Chief and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an Associate Editor, Peer Review.<br /> # Call for papers is posted on the OSGeo discuss and announcement mailing lists and web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. In general, the same types of papers are invited as usually fits the Journal criteria, but in this case the author can choose whether to opt-in for peer review, if available.<br /> # A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> # Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration). This can be the same wiki page used for a Journal issue's list of articles.<br /> # AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> #Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as: <br /> ## &quot;Does the paper fit within the scope of OSGeo Journal?&quot; <br /> ## &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot;<br /> ## &quot;Is the paper well written?&quot; <br /> ## &quot;Does the paper use correct English spelling, syntax and grammar?&quot; <br /> ## &quot;Is the title appropriate?&quot;<br /> ## &quot;Is the abstract succinct of the correct length and appropriate?&quot; <br /> ## &quot;Are the citations complete and correct?&quot; <br /> ## &quot;Are all of the figures and tables necessary, clear and informative?&quot; <br /> ## &quot;Do you have any suggestions for the authors that would improve the paper?&quot; <br /> ## &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> # Reviewers are given four weeks to submit reviews.<br /> # The AE notifies the authors of the reviewers decision as follows: <br /> ## If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> ## If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> ## If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> ## If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> == Specifics for OSGeo Journal Volume 1, Issue 2 ==<br /> <br /> I think it is possible that we could initiate a test peer review process for the second issue of OSGeo Journal and would propose the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Talk:Journal&diff=14814 2007-05-26T23:26:32Z

<p>Wiki-Danames: moved peer review discussion to a new page.</p> <hr /> <div></div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal_Peer_Review&diff=14813 2007-05-26T23:24:50Z

<p>Wiki-Danames: </p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> == Paper Categorization ==<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence it could be useful to categorize the articles in OSGeo Journal as:<br /> <br /> # Editorials and Discussion Articles<br /> # Announcements and Project Status Reports<br /> # Peer Reviewed Papers<br /> <br /> == Review Process ==<br /> For the peer reviewed papers, the following review process is proposed:<br /> <br /> # OSGeo Journal Editor in Chief and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an Associate Editor, Peer Review.<br /> # Call for papers is posted on the OSGeo discuss and announcement mailing lists and web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. In general, the same types of papers are invited as usually fits the Journal criteria, but in this case the author can choose whether to opt-in for peer review, if available.<br /> # A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> # Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration). This can be the same wiki page used for a Journal issue's list of articles.<br /> # AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> #Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as: <br /> ## &quot;Does the paper fit within the scope of OSGeo Journal?&quot; <br /> ## &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot;<br /> ## &quot;Is the paper well written?&quot; <br /> ## &quot;Does the paper use correct English spelling, syntax and grammar?&quot; <br /> ## &quot;Is the title appropriate?&quot;<br /> ## &quot;Is the abstract succinct of the correct length and appropriate?&quot; <br /> ## &quot;Are the citations complete and correct?&quot; <br /> ## &quot;Are all of the figures and tables necessary, clear and informative?&quot; <br /> ## &quot;Do you have any suggestions for the authors that would improve the paper?&quot; <br /> ## &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> # Reviewers are given four weeks to submit reviews.<br /> # The AE notifies the authors of the reviewers decision as follows: <br /> ## If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> ## If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> ## If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> ## If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> == Specifics for OSGeo Journal Volume 1, Issue 2 ==<br /> <br /> I think it is possible that we could initiate a test peer review process for the second issue of OSGeo Journal and would propose the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Journal_Peer_Review&diff=14812 2007-05-26T23:24:00Z

<p>Wiki-Danames: Initial material added.</p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> === Paper Categorization ===<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence it could be useful to categorize the articles in OSGeo Journal as:<br /> <br /> # Editorials and Discussion Articles<br /> # Announcements and Project Status Reports<br /> # Peer Reviewed Papers<br /> <br /> === Review Process ===<br /> For the peer reviewed papers, the following review process is proposed:<br /> <br /> # OSGeo Journal Editor in Chief and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an Associate Editor, Peer Review.<br /> # Call for papers is posted on the OSGeo discuss and announcement mailing lists and web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. In general, the same types of papers are invited as usually fits the Journal criteria, but in this case the author can choose whether to opt-in for peer review, if available.<br /> # A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> # Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration). This can be the same wiki page used for a Journal issue's list of articles.<br /> # AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> #Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as: <br /> ## &quot;Does the paper fit within the scope of OSGeo Journal?&quot; <br /> ## &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot;<br /> ## &quot;Is the paper well written?&quot; <br /> ## &quot;Does the paper use correct English spelling, syntax and grammar?&quot; <br /> ## &quot;Is the title appropriate?&quot;<br /> ## &quot;Is the abstract succinct of the correct length and appropriate?&quot; <br /> ## &quot;Are the citations complete and correct?&quot; <br /> ## &quot;Are all of the figures and tables necessary, clear and informative?&quot; <br /> ## &quot;Do you have any suggestions for the authors that would improve the paper?&quot; <br /> ## &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> # Reviewers are given four weeks to submit reviews.<br /> # The AE notifies the authors of the reviewers decision as follows: <br /> ## If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> ## If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> ## If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> ## If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> === Specifics for OSGeo Journal Volume 1, Issue 2 ===<br /> <br /> I think it is possible that we could initiate a test peer review process for the second issue of OSGeo Journal and would propose the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Talk:Journal&diff=14759 2007-05-25T23:08:05Z

<p>Wiki-Danames: </p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> <br /> '''Proposed Paper Categorization'''<br /> <br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence it could be useful to categorize the articles in OSGeo Journal as:<br /> <br /> 1) Editorials and Discussion Articles<br /> <br /> 2) Announcements and Project Status Reports<br /> <br /> 3) Peer Reviewed Papers<br /> <br /> <br /> '''Proposed Review Process'''<br /> <br /> For the peer reviewed papers, the following review process is proposed:<br /> <br /> <br /> * 1) OSGeo Journal Senior Editor (Tyler?) and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an associate editor - AE. (I've agreed to take a shot at this - or someone else can do it. - dpa)<br /> <br /> <br /> * 2) Call for papers is posted on the OSGeo.com web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. (This text still needs to be worked out). <br /> <br /> <br /> * 3) A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> <br /> <br /> * 4) Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration)<br /> <br /> <br /> * 5) AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> <br /> <br /> * 6) Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as &quot;Does the paper fit within the scope of OSGeo Journal?&quot; &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot; &quot;Is the paper well written?&quot; &quot;Does the paper use correct English spelling, syntax and grammar?&quot; &quot;Is the title appropriate?&quot; &quot;Is the abstract succinct of the correct length and appropriate?&quot; &quot;Are the citations complete and correct?&quot; &quot;Are all of the figures and tables necessary, clear and informative?&quot; &quot;Do you have any suggestions for the authors that would improve the paper?&quot; &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> <br /> <br /> * 7) Reviewers are given four weeks to submit reviews.<br /> <br /> <br /> * 8) The AE notifies the authors of the reviewers decision as follows: <br /> <br /> - If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> <br /> - If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> <br /> - If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> <br /> - If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> <br /> '''Specifics for OSGeo Journal Volume 1, Issue 2'''<br /> <br /> I think it is possible that we could initiate a test peer review process for the second issue of OSGeo Journal and would propose the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.<br /> <br /> <br /> == Article Length ==<br /> We need to define article lengths - do you have any past experience setting lengths or have you left them wide open? I think we should add them to the categories on this page. [[User:tmitchell|Tyler]]<br /> === Previous editions ===<br /> I just did a quick skim through the last GRASS News volume and came up with some rough word counts. The following also include several screenshots, on average 1.5 images per page:<br /> * Event Reports - 750 words (1 page)<br /> * Short updates - 1200 words (2.5 pages)<br /> * Short Reports - 1500 words (3 pages)<br /> * Extended Reports - 2500 words (5 pages)<br /> * Interview - 3000 words (4 pages, only 1 image)<br /> * Project Reports/Announcements - 500-1000 words (0.5-1 page) (GRASS report was several pages in past, probably should reduce to make room for others)<br /> <br /> Do these make sense?<br /> <br /> == main non-Wiki page for submission ==<br /> <br /> shall we add a non-Wiki page for authors who want to submit articles?<br /> Just instructions and contact e-mail add. of Edt.? [[User:Wegmann|Wegmann]] 13:50, 28 February 2007 (CET)<br /> : Good idea - Tyler<br /> :: Who do we have to contact to have a non-wiki OSGeo page for contact, download of templates + releases? [[User:Wegmann|Wegmann]] 18:05, 1 March 2007 (CET)<br /> <br /> == call for volunteers ==<br /> Here is my call for volunteers, focused on building our team:<br /> ------<br /> <br /> <br /> Hi all,<br /> As you may be aware, last year the GRASS News production offered to transition their great production into a brand new OSGeo Newsletter. Although branded as OSGeo, all open source projects are welcome to be part of it.<br /> <br /> For those of you who are unfamiliar with the last volume, have a look at this:<br /> http://osgeo.org/files/news/GRASS_OSGeo_News_vol4.pdf (5.3MB). As you can see it is much more than just some news clippings!<br /> <br /> Well, now is the time to get a new team together to help make a great production. You are invited to be part of that team! Want some exercise for your writing skills? Would you like to get some more exposure for your project? Want to learn the ins and outs of some publication software? Or do you just want to help spread the word about some projects or case studies that you love?<br /> <br /> There are several positions available for any volunteer who would help to coordinate collecting articles, writing content, reviewing content, helping with layout or graphics, and more. Want to sign up just for one volume or to test the waters first? That is fine too.<br /> <br /> Please see the Newsletter wiki page for a list of open positions and categories for content that need editors:<br /> http://wiki.osgeo.org/index.php/Newsletter<br /> <br /> If you have any reservations, comments, questions or concerns please just let me know! As we will work as a team, please do not be shy about your interests, even if you are going to need some help getting started.<br /> <br /> After the team is gathered and production deadlines are finalised, then we will make a more general call for contributors. If you already have something that you would like to contribute, you are welcome to sign up now on the page:<br /> http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> <br /> Hope you will join us in putting this together!<br /> <br /> Tyler<br /> <br /> Following needs to be forwarded to more lists. Copy raw text from edit more to get something that works well in an email.<br /> -----<br /> From: tylermitchell@shaw.ca<br /> Subject: Call for articles - OSGeo Newsletter<br /> Date: March 5, 2007 11:14:56 AM PST (CA)<br /> To: discuss@lists.osgeo.org<br /> <br /> The OSGeo Newsletter development team invites you to contribute news, articles, event summaries, programming tutorials and more for the upcoming OSGeo News - Volume 1. There are several sections planned for the newsletter. General descriptions of each category can be found on the Newsletter wiki page [1]. Specific committed articles are listed on the Newsletter Volume 1 wiki page [2].<br /> <br /> There has been already been a lot of interest to contribute articles and some sections are already quite full. You are welcome to propose an article for any section, but we are specifically looking for more articles in the following categories:<br /> <br /> * News - any particularly newsworthy items you would like to pass along<br /> * Event Reports - have a conference summary that you would like to share?<br /> * Topical Studies - introduce a theoretical topic that is of general interest<br /> * Programming Tutorials - serving as an introduction to coding an application or task<br /> * Interview - conduct an interview with someone in the community<br /> * Developer Announcements - brief summaries of what your project team has been doing recently and future outlook for the project<br /> <br /> To volunteer for an article add your name and article title to the Volume 1 wiki page in the appropriate category, along with contact information. Or join the Newsletter mailing list [3] and tell us about your idea. An editor will follow-up with you to arrange delivery and timing. Articles need to be delivered by March 23st. Length can vary depending on type of article and should be discussed with the editor for your category. If you want to contribute but a particular category is full (or you need more time), you are more than welcome to add yourself to the list of articles for the subsequent volume, Volume 2 [4].<br /> <br /> We look forward to working with you on producing a great newsletter that is of interest to everyone in our communities and beyond.<br /> <br /> Sincerely,<br /> Tyler<br /> <br /> [1] Newsletter general wiki page: http://wiki.osgeo.org/index.php/Newsletter<br /> [2] Newsletter Volume 1 wiki page: http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> [3] Newsletter development mailing list: http://lists.osgeo.org/mailman/listinfo/newsletter<br /> [4] Newsletter Volume 2 (future): http://wiki.osgeo.org/index.php/Newsletter_Volume_2</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Talk:Journal&diff=14758 2007-05-25T22:59:35Z

<p>Wiki-Danames: </p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> '''Proposed Paper Categorization'''<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence it could be useful to categorize the articles in OSGeo Journal as:<br /> 1) Editorials and Discussion Articles<br /> 2) Announcements and Project Status Reports<br /> 3) Peer Reviewed Papers<br /> <br /> '''Proposed Review Process'''<br /> For the peer reviewed papers, the following review process is proposed:<br /> 1) OSGeo Journal Senior Editor (Tyler?) and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an associate editor - AE. (I've agreed to take a shot at this - or someone else can do it. - dpa)<br /> 2) Call for papers is posted on the OSGeo.com web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. (This text still needs to be worked out). <br /> 3) A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> 4) Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration)<br /> 5) AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> 6) Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as &quot;Does the paper fit within the scope of OSGeo Journal?&quot; &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot; &quot;Is the paper well written?&quot; &quot;Does the paper use correct English spelling, syntax and grammar?&quot; &quot;Is the title appropriate?&quot; &quot;Is the abstract succinct of the correct length and appropriate?&quot; &quot;Are the citations complete and correct?&quot; &quot;Are all of the figures and tables necessary, clear and informative?&quot; &quot;Do you have any suggestions for the authors that would improve the paper?&quot; &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> 7) Reviewers are given four weeks to submit reviews.<br /> 8) The AE notifies the authors of the reviewers decision as follows: <br /> <br /> If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> <br /> If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> <br /> If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> <br /> If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> '''Specifics for OSGeo Journal Volume 1, Issue 2'''<br /> <br /> I think it is possible that we could initiate a test peer review process for the second issue of OSGeo Journal and would propose the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.<br /> <br /> <br /> == Article Length ==<br /> We need to define article lengths - do you have any past experience setting lengths or have you left them wide open? I think we should add them to the categories on this page. [[User:tmitchell|Tyler]]<br /> === Previous editions ===<br /> I just did a quick skim through the last GRASS News volume and came up with some rough word counts. The following also include several screenshots, on average 1.5 images per page:<br /> * Event Reports - 750 words (1 page)<br /> * Short updates - 1200 words (2.5 pages)<br /> * Short Reports - 1500 words (3 pages)<br /> * Extended Reports - 2500 words (5 pages)<br /> * Interview - 3000 words (4 pages, only 1 image)<br /> * Project Reports/Announcements - 500-1000 words (0.5-1 page) (GRASS report was several pages in past, probably should reduce to make room for others)<br /> <br /> Do these make sense?<br /> <br /> == main non-Wiki page for submission ==<br /> <br /> shall we add a non-Wiki page for authors who want to submit articles?<br /> Just instructions and contact e-mail add. of Edt.? [[User:Wegmann|Wegmann]] 13:50, 28 February 2007 (CET)<br /> : Good idea - Tyler<br /> :: Who do we have to contact to have a non-wiki OSGeo page for contact, download of templates + releases? [[User:Wegmann|Wegmann]] 18:05, 1 March 2007 (CET)<br /> <br /> == call for volunteers ==<br /> Here is my call for volunteers, focused on building our team:<br /> ------<br /> <br /> <br /> Hi all,<br /> As you may be aware, last year the GRASS News production offered to transition their great production into a brand new OSGeo Newsletter. Although branded as OSGeo, all open source projects are welcome to be part of it.<br /> <br /> For those of you who are unfamiliar with the last volume, have a look at this:<br /> http://osgeo.org/files/news/GRASS_OSGeo_News_vol4.pdf (5.3MB). As you can see it is much more than just some news clippings!<br /> <br /> Well, now is the time to get a new team together to help make a great production. You are invited to be part of that team! Want some exercise for your writing skills? Would you like to get some more exposure for your project? Want to learn the ins and outs of some publication software? Or do you just want to help spread the word about some projects or case studies that you love?<br /> <br /> There are several positions available for any volunteer who would help to coordinate collecting articles, writing content, reviewing content, helping with layout or graphics, and more. Want to sign up just for one volume or to test the waters first? That is fine too.<br /> <br /> Please see the Newsletter wiki page for a list of open positions and categories for content that need editors:<br /> http://wiki.osgeo.org/index.php/Newsletter<br /> <br /> If you have any reservations, comments, questions or concerns please just let me know! As we will work as a team, please do not be shy about your interests, even if you are going to need some help getting started.<br /> <br /> After the team is gathered and production deadlines are finalised, then we will make a more general call for contributors. If you already have something that you would like to contribute, you are welcome to sign up now on the page:<br /> http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> <br /> Hope you will join us in putting this together!<br /> <br /> Tyler<br /> <br /> Following needs to be forwarded to more lists. Copy raw text from edit more to get something that works well in an email.<br /> -----<br /> From: tylermitchell@shaw.ca<br /> Subject: Call for articles - OSGeo Newsletter<br /> Date: March 5, 2007 11:14:56 AM PST (CA)<br /> To: discuss@lists.osgeo.org<br /> <br /> The OSGeo Newsletter development team invites you to contribute news, articles, event summaries, programming tutorials and more for the upcoming OSGeo News - Volume 1. There are several sections planned for the newsletter. General descriptions of each category can be found on the Newsletter wiki page [1]. Specific committed articles are listed on the Newsletter Volume 1 wiki page [2].<br /> <br /> There has been already been a lot of interest to contribute articles and some sections are already quite full. You are welcome to propose an article for any section, but we are specifically looking for more articles in the following categories:<br /> <br /> * News - any particularly newsworthy items you would like to pass along<br /> * Event Reports - have a conference summary that you would like to share?<br /> * Topical Studies - introduce a theoretical topic that is of general interest<br /> * Programming Tutorials - serving as an introduction to coding an application or task<br /> * Interview - conduct an interview with someone in the community<br /> * Developer Announcements - brief summaries of what your project team has been doing recently and future outlook for the project<br /> <br /> To volunteer for an article add your name and article title to the Volume 1 wiki page in the appropriate category, along with contact information. Or join the Newsletter mailing list [3] and tell us about your idea. An editor will follow-up with you to arrange delivery and timing. Articles need to be delivered by March 23st. Length can vary depending on type of article and should be discussed with the editor for your category. If you want to contribute but a particular category is full (or you need more time), you are more than welcome to add yourself to the list of articles for the subsequent volume, Volume 2 [4].<br /> <br /> We look forward to working with you on producing a great newsletter that is of interest to everyone in our communities and beyond.<br /> <br /> Sincerely,<br /> Tyler<br /> <br /> [1] Newsletter general wiki page: http://wiki.osgeo.org/index.php/Newsletter<br /> [2] Newsletter Volume 1 wiki page: http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> [3] Newsletter development mailing list: http://lists.osgeo.org/mailman/listinfo/newsletter<br /> [4] Newsletter Volume 2 (future): http://wiki.osgeo.org/index.php/Newsletter_Volume_2</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Talk:Journal&diff=14757 2007-05-25T22:57:19Z

<p>Wiki-Danames: </p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> '''Proposed Paper Categorization'''<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence it could be useful to categorize the articles in OSGeo Journal as:<br /> 1) Editorials and Discussion Articles<br /> 2) Announcements and Project Status Reports<br /> 3) Peer Reviewed Papers<br /> <br /> '''Proposed Review Process'''<br /> For the peer reviewed papers, the following review process is proposed:<br /> 1) OSGeo Journal Senior Editor (Tyler?) and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an associate editor - AE. (I've agreed to take a shot at this - or someone else can do it. - dpa)<br /> 2) Call for papers is posted on the OSGeo.com web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. (This text still needs to be worked out). <br /> 3) A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> 4) Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration)<br /> 5) AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> 6) Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as &quot;Does the paper fit within the scope of OSGeo Journal?&quot; &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot; &quot;Is the paper well written?&quot; &quot;Does the paper use correct English spelling, syntax and grammar?&quot; &quot;Is the title appropriate?&quot; &quot;Is the abstract succinct of the correct length and appropriate?&quot; &quot;Are the citations complete and correct?&quot; &quot;Are all of the figures and tables necessary, clear and informative?&quot; &quot;Do you have any suggestions for the authors that would improve the paper?&quot; &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> 7) Reviewers are given four weeks to submit reviews.<br /> 8) The AE notifies the authors of the reviewers decision as follows: <br /> <br /> If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> <br /> If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> <br /> If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> <br /> If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> [[Specifics for OSGeo Journal Volume 1, Issue 2]]<br /> I believe it is possible that we could initiate a test peer review process for the second issue of OSGeo Journal and would propose the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.<br /> <br /> <br /> == Article Length ==<br /> We need to define article lengths - do you have any past experience setting lengths or have you left them wide open? I think we should add them to the categories on this page. [[User:tmitchell|Tyler]]<br /> === Previous editions ===<br /> I just did a quick skim through the last GRASS News volume and came up with some rough word counts. The following also include several screenshots, on average 1.5 images per page:<br /> * Event Reports - 750 words (1 page)<br /> * Short updates - 1200 words (2.5 pages)<br /> * Short Reports - 1500 words (3 pages)<br /> * Extended Reports - 2500 words (5 pages)<br /> * Interview - 3000 words (4 pages, only 1 image)<br /> * Project Reports/Announcements - 500-1000 words (0.5-1 page) (GRASS report was several pages in past, probably should reduce to make room for others)<br /> <br /> Do these make sense?<br /> <br /> == main non-Wiki page for submission ==<br /> <br /> shall we add a non-Wiki page for authors who want to submit articles?<br /> Just instructions and contact e-mail add. of Edt.? [[User:Wegmann|Wegmann]] 13:50, 28 February 2007 (CET)<br /> : Good idea - Tyler<br /> :: Who do we have to contact to have a non-wiki OSGeo page for contact, download of templates + releases? [[User:Wegmann|Wegmann]] 18:05, 1 March 2007 (CET)<br /> <br /> == call for volunteers ==<br /> Here is my call for volunteers, focused on building our team:<br /> ------<br /> <br /> <br /> Hi all,<br /> As you may be aware, last year the GRASS News production offered to transition their great production into a brand new OSGeo Newsletter. Although branded as OSGeo, all open source projects are welcome to be part of it.<br /> <br /> For those of you who are unfamiliar with the last volume, have a look at this:<br /> http://osgeo.org/files/news/GRASS_OSGeo_News_vol4.pdf (5.3MB). As you can see it is much more than just some news clippings!<br /> <br /> Well, now is the time to get a new team together to help make a great production. You are invited to be part of that team! Want some exercise for your writing skills? Would you like to get some more exposure for your project? Want to learn the ins and outs of some publication software? Or do you just want to help spread the word about some projects or case studies that you love?<br /> <br /> There are several positions available for any volunteer who would help to coordinate collecting articles, writing content, reviewing content, helping with layout or graphics, and more. Want to sign up just for one volume or to test the waters first? That is fine too.<br /> <br /> Please see the Newsletter wiki page for a list of open positions and categories for content that need editors:<br /> http://wiki.osgeo.org/index.php/Newsletter<br /> <br /> If you have any reservations, comments, questions or concerns please just let me know! As we will work as a team, please do not be shy about your interests, even if you are going to need some help getting started.<br /> <br /> After the team is gathered and production deadlines are finalised, then we will make a more general call for contributors. If you already have something that you would like to contribute, you are welcome to sign up now on the page:<br /> http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> <br /> Hope you will join us in putting this together!<br /> <br /> Tyler<br /> <br /> Following needs to be forwarded to more lists. Copy raw text from edit more to get something that works well in an email.<br /> -----<br /> From: tylermitchell@shaw.ca<br /> Subject: Call for articles - OSGeo Newsletter<br /> Date: March 5, 2007 11:14:56 AM PST (CA)<br /> To: discuss@lists.osgeo.org<br /> <br /> The OSGeo Newsletter development team invites you to contribute news, articles, event summaries, programming tutorials and more for the upcoming OSGeo News - Volume 1. There are several sections planned for the newsletter. General descriptions of each category can be found on the Newsletter wiki page [1]. Specific committed articles are listed on the Newsletter Volume 1 wiki page [2].<br /> <br /> There has been already been a lot of interest to contribute articles and some sections are already quite full. You are welcome to propose an article for any section, but we are specifically looking for more articles in the following categories:<br /> <br /> * News - any particularly newsworthy items you would like to pass along<br /> * Event Reports - have a conference summary that you would like to share?<br /> * Topical Studies - introduce a theoretical topic that is of general interest<br /> * Programming Tutorials - serving as an introduction to coding an application or task<br /> * Interview - conduct an interview with someone in the community<br /> * Developer Announcements - brief summaries of what your project team has been doing recently and future outlook for the project<br /> <br /> To volunteer for an article add your name and article title to the Volume 1 wiki page in the appropriate category, along with contact information. Or join the Newsletter mailing list [3] and tell us about your idea. An editor will follow-up with you to arrange delivery and timing. Articles need to be delivered by March 23st. Length can vary depending on type of article and should be discussed with the editor for your category. If you want to contribute but a particular category is full (or you need more time), you are more than welcome to add yourself to the list of articles for the subsequent volume, Volume 2 [4].<br /> <br /> We look forward to working with you on producing a great newsletter that is of interest to everyone in our communities and beyond.<br /> <br /> Sincerely,<br /> Tyler<br /> <br /> [1] Newsletter general wiki page: http://wiki.osgeo.org/index.php/Newsletter<br /> [2] Newsletter Volume 1 wiki page: http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> [3] Newsletter development mailing list: http://lists.osgeo.org/mailman/listinfo/newsletter<br /> [4] Newsletter Volume 2 (future): http://wiki.osgeo.org/index.php/Newsletter_Volume_2</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Talk:Journal&diff=14756 2007-05-25T22:56:40Z

<p>Wiki-Danames: </p> <hr /> <div>== Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> '''<br /> [[Proposed Paper Categorization]]'''<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence it could be useful to categorize the articles in OSGeo Journal as:<br /> 1) Editorials and Discussion Articles<br /> 2) Announcements and Project Status Reports<br /> 3) Peer Reviewed Papers<br /> '''<br /> [[Proposed Review Process]]'''<br /> For the peer reviewed papers, the following review process is proposed:<br /> 1) OSGeo Journal Senior Editor (Tyler?) and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an associate editor - AE. (I've agreed to take a shot at this - or someone else can do it. - dpa)<br /> 2) Call for papers is posted on the OSGeo.com web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. (This text still needs to be worked out). <br /> 3) A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> 4) Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration)<br /> 5) AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> 6) Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as &quot;Does the paper fit within the scope of OSGeo Journal?&quot; &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot; &quot;Is the paper well written?&quot; &quot;Does the paper use correct English spelling, syntax and grammar?&quot; &quot;Is the title appropriate?&quot; &quot;Is the abstract succinct of the correct length and appropriate?&quot; &quot;Are the citations complete and correct?&quot; &quot;Are all of the figures and tables necessary, clear and informative?&quot; &quot;Do you have any suggestions for the authors that would improve the paper?&quot; &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> 7) Reviewers are given four weeks to submit reviews.<br /> 8) The AE notifies the authors of the reviewers decision as follows: <br /> <br /> If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> <br /> If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> <br /> If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> <br /> If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> [[Specifics for OSGeo Journal Volume 1, Issue 2]]<br /> I believe it is possible that we could initiate a test peer review process for the second issue of OSGeo Journal and would propose the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.<br /> <br /> <br /> == Article Length ==<br /> We need to define article lengths - do you have any past experience setting lengths or have you left them wide open? I think we should add them to the categories on this page. [[User:tmitchell|Tyler]]<br /> === Previous editions ===<br /> I just did a quick skim through the last GRASS News volume and came up with some rough word counts. The following also include several screenshots, on average 1.5 images per page:<br /> * Event Reports - 750 words (1 page)<br /> * Short updates - 1200 words (2.5 pages)<br /> * Short Reports - 1500 words (3 pages)<br /> * Extended Reports - 2500 words (5 pages)<br /> * Interview - 3000 words (4 pages, only 1 image)<br /> * Project Reports/Announcements - 500-1000 words (0.5-1 page) (GRASS report was several pages in past, probably should reduce to make room for others)<br /> <br /> Do these make sense?<br /> <br /> == main non-Wiki page for submission ==<br /> <br /> shall we add a non-Wiki page for authors who want to submit articles?<br /> Just instructions and contact e-mail add. of Edt.? [[User:Wegmann|Wegmann]] 13:50, 28 February 2007 (CET)<br /> : Good idea - Tyler<br /> :: Who do we have to contact to have a non-wiki OSGeo page for contact, download of templates + releases? [[User:Wegmann|Wegmann]] 18:05, 1 March 2007 (CET)<br /> <br /> == call for volunteers ==<br /> Here is my call for volunteers, focused on building our team:<br /> ------<br /> <br /> <br /> Hi all,<br /> As you may be aware, last year the GRASS News production offered to transition their great production into a brand new OSGeo Newsletter. Although branded as OSGeo, all open source projects are welcome to be part of it.<br /> <br /> For those of you who are unfamiliar with the last volume, have a look at this:<br /> http://osgeo.org/files/news/GRASS_OSGeo_News_vol4.pdf (5.3MB). As you can see it is much more than just some news clippings!<br /> <br /> Well, now is the time to get a new team together to help make a great production. You are invited to be part of that team! Want some exercise for your writing skills? Would you like to get some more exposure for your project? Want to learn the ins and outs of some publication software? Or do you just want to help spread the word about some projects or case studies that you love?<br /> <br /> There are several positions available for any volunteer who would help to coordinate collecting articles, writing content, reviewing content, helping with layout or graphics, and more. Want to sign up just for one volume or to test the waters first? That is fine too.<br /> <br /> Please see the Newsletter wiki page for a list of open positions and categories for content that need editors:<br /> http://wiki.osgeo.org/index.php/Newsletter<br /> <br /> If you have any reservations, comments, questions or concerns please just let me know! As we will work as a team, please do not be shy about your interests, even if you are going to need some help getting started.<br /> <br /> After the team is gathered and production deadlines are finalised, then we will make a more general call for contributors. If you already have something that you would like to contribute, you are welcome to sign up now on the page:<br /> http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> <br /> Hope you will join us in putting this together!<br /> <br /> Tyler<br /> <br /> Following needs to be forwarded to more lists. Copy raw text from edit more to get something that works well in an email.<br /> -----<br /> From: tylermitchell@shaw.ca<br /> Subject: Call for articles - OSGeo Newsletter<br /> Date: March 5, 2007 11:14:56 AM PST (CA)<br /> To: discuss@lists.osgeo.org<br /> <br /> The OSGeo Newsletter development team invites you to contribute news, articles, event summaries, programming tutorials and more for the upcoming OSGeo News - Volume 1. There are several sections planned for the newsletter. General descriptions of each category can be found on the Newsletter wiki page [1]. Specific committed articles are listed on the Newsletter Volume 1 wiki page [2].<br /> <br /> There has been already been a lot of interest to contribute articles and some sections are already quite full. You are welcome to propose an article for any section, but we are specifically looking for more articles in the following categories:<br /> <br /> * News - any particularly newsworthy items you would like to pass along<br /> * Event Reports - have a conference summary that you would like to share?<br /> * Topical Studies - introduce a theoretical topic that is of general interest<br /> * Programming Tutorials - serving as an introduction to coding an application or task<br /> * Interview - conduct an interview with someone in the community<br /> * Developer Announcements - brief summaries of what your project team has been doing recently and future outlook for the project<br /> <br /> To volunteer for an article add your name and article title to the Volume 1 wiki page in the appropriate category, along with contact information. Or join the Newsletter mailing list [3] and tell us about your idea. An editor will follow-up with you to arrange delivery and timing. Articles need to be delivered by March 23st. Length can vary depending on type of article and should be discussed with the editor for your category. If you want to contribute but a particular category is full (or you need more time), you are more than welcome to add yourself to the list of articles for the subsequent volume, Volume 2 [4].<br /> <br /> We look forward to working with you on producing a great newsletter that is of interest to everyone in our communities and beyond.<br /> <br /> Sincerely,<br /> Tyler<br /> <br /> [1] Newsletter general wiki page: http://wiki.osgeo.org/index.php/Newsletter<br /> [2] Newsletter Volume 1 wiki page: http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> [3] Newsletter development mailing list: http://lists.osgeo.org/mailman/listinfo/newsletter<br /> [4] Newsletter Volume 2 (future): http://wiki.osgeo.org/index.php/Newsletter_Volume_2</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Talk:Journal&diff=14755 2007-05-25T22:55:31Z

<p>Wiki-Danames: Peer review discussion</p> <hr /> <div><br /> == Peer Review ==<br /> Many people in industry, academia, research, and government institutions need to build a record of peer reviewed publications. Because of this, it's been proposed that we initiate a formal process of peer review for a subset of OSGeo Journal articles. This would add an additional level of credibility to these particular papers and will also make them more citable and so forth. <br /> <br /> [[Proposed Paper Categorization]]<br /> While the peer review process can be useful for some papers, it should not necessarily be a requirement for everything that gets published in OSGeo Journal. Hence it could be useful to categorize the articles in OSGeo Journal as:<br /> 1) Editorials and Discussion Articles<br /> 2) Announcements and Project Status Reports<br /> 3) Peer Reviewed Papers<br /> <br /> [[Proposed Review Process]]<br /> For the peer reviewed papers, the following review process is proposed:<br /> 1) OSGeo Journal Senior Editor (Tyler?) and the Journal Review Board have final say on the number of peer reviewed papers that will be accepted in any given edition as well as timing requirements and so forth, but generally assign responsibility for the peer review process to an associate editor - AE. (I've agreed to take a shot at this - or someone else can do it. - dpa)<br /> 2) Call for papers is posted on the OSGeo.com web site. This call is on-going and describes the intended scope of the journal with respect to peer reviewed papers, types of papers sought, etc. (This text still needs to be worked out). <br /> 3) A call for reviewers is also posted, and a list of potential reviewers is maintained on the WIKI (hopefully this is a long enough list to maintain individual anonymity on specific reviews).<br /> 4) Authors send their manuscripts to the AE who goes on the WIKI and lists the title and authors (just as an FYI to the community - and also lets the authors know that their paper is under consideration)<br /> 5) AE contacts a few potential reviewers from the list of willing reviewers and sends them the manuscript electronically.<br /> 6) Reviewers are also given a link to the web site where a list of review considerations are posted. These will follow generally accepted considerations such as &quot;Does the paper fit within the scope of OSGeo Journal?&quot; &quot;Does the paper make a new or original contribution to the field of geoinformatics and specifically the development of and/or application of FOSS4G software?&quot; &quot;Is the paper well written?&quot; &quot;Does the paper use correct English spelling, syntax and grammar?&quot; &quot;Is the title appropriate?&quot; &quot;Is the abstract succinct of the correct length and appropriate?&quot; &quot;Are the citations complete and correct?&quot; &quot;Are all of the figures and tables necessary, clear and informative?&quot; &quot;Do you have any suggestions for the authors that would improve the paper?&quot; &quot;Would you rate this paper as acceptable as is, requires minor changes (no re-review necessary), requires major changes (re-review necessary), or not-acceptable?&quot;<br /> 7) Reviewers are given four weeks to submit reviews.<br /> 8) The AE notifies the authors of the reviewers decision as follows: <br /> <br /> If two or more recommend &quot;Accept as is&quot; then the paper will be placed on the queue for publication in an upcoming edition with no further review required. <br /> <br /> If two or more recommend at least &quot;Accept with minor changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications within a short time period. The associated editor will verify that the changes were made and then pass the paper on to the editor for addition to the publication queue <br /> <br /> If two or more recommend at least &quot;Major changes&quot; then the authors will be sent the reviewers' notes and encouraged to make the requested modifications and then resubmit the paper for a follow-on review by the original reviewers. This would probably need to have a time associated with it so that the paper stays relatively fresh for the reviewers. Perhaps 4 weeks would be an appropriate time for turn-around. <br /> <br /> If two or more recommend &quot;Reject&quot; then the authors would be sent a nice note indicating that the paper was found unsuitable for the journal and thanked for their effort, etc. They would also be sent the reviewers' comments.<br /> <br /> [[Specifics for OSGeo Journal Volume 1, Issue 2]]<br /> I believe it is possible that we could initiate a test peer review process for the second issue of OSGeo Journal and would propose the following time line:<br /> <br /> * June 1 - Call for papers<br /> * June 15 - Deadline for papers (its expected that for this tight deadline we'll only receive a handful of papers which is probably good for this first effort).<br /> * June 22 - Target date for finding reviewers for the papers<br /> * July 22 - Four week deadline for reviews from reviewers. <br /> * July 27 - Final deadline for reviews from reviewers.<br /> * August 3 - Deadline for acceptable manuscripts (accept as is, accept with minor changes) to be submitted in final form.<br /> <br /> <br /> == Article Length ==<br /> We need to define article lengths - do you have any past experience setting lengths or have you left them wide open? I think we should add them to the categories on this page. [[User:tmitchell|Tyler]]<br /> === Previous editions ===<br /> I just did a quick skim through the last GRASS News volume and came up with some rough word counts. The following also include several screenshots, on average 1.5 images per page:<br /> * Event Reports - 750 words (1 page)<br /> * Short updates - 1200 words (2.5 pages)<br /> * Short Reports - 1500 words (3 pages)<br /> * Extended Reports - 2500 words (5 pages)<br /> * Interview - 3000 words (4 pages, only 1 image)<br /> * Project Reports/Announcements - 500-1000 words (0.5-1 page) (GRASS report was several pages in past, probably should reduce to make room for others)<br /> <br /> Do these make sense?<br /> <br /> == main non-Wiki page for submission ==<br /> <br /> shall we add a non-Wiki page for authors who want to submit articles?<br /> Just instructions and contact e-mail add. of Edt.? [[User:Wegmann|Wegmann]] 13:50, 28 February 2007 (CET)<br /> : Good idea - Tyler<br /> :: Who do we have to contact to have a non-wiki OSGeo page for contact, download of templates + releases? [[User:Wegmann|Wegmann]] 18:05, 1 March 2007 (CET)<br /> <br /> == call for volunteers ==<br /> Here is my call for volunteers, focused on building our team:<br /> ------<br /> <br /> <br /> Hi all,<br /> As you may be aware, last year the GRASS News production offered to transition their great production into a brand new OSGeo Newsletter. Although branded as OSGeo, all open source projects are welcome to be part of it.<br /> <br /> For those of you who are unfamiliar with the last volume, have a look at this:<br /> http://osgeo.org/files/news/GRASS_OSGeo_News_vol4.pdf (5.3MB). As you can see it is much more than just some news clippings!<br /> <br /> Well, now is the time to get a new team together to help make a great production. You are invited to be part of that team! Want some exercise for your writing skills? Would you like to get some more exposure for your project? Want to learn the ins and outs of some publication software? Or do you just want to help spread the word about some projects or case studies that you love?<br /> <br /> There are several positions available for any volunteer who would help to coordinate collecting articles, writing content, reviewing content, helping with layout or graphics, and more. Want to sign up just for one volume or to test the waters first? That is fine too.<br /> <br /> Please see the Newsletter wiki page for a list of open positions and categories for content that need editors:<br /> http://wiki.osgeo.org/index.php/Newsletter<br /> <br /> If you have any reservations, comments, questions or concerns please just let me know! As we will work as a team, please do not be shy about your interests, even if you are going to need some help getting started.<br /> <br /> After the team is gathered and production deadlines are finalised, then we will make a more general call for contributors. If you already have something that you would like to contribute, you are welcome to sign up now on the page:<br /> http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> <br /> Hope you will join us in putting this together!<br /> <br /> Tyler<br /> <br /> Following needs to be forwarded to more lists. Copy raw text from edit more to get something that works well in an email.<br /> -----<br /> From: tylermitchell@shaw.ca<br /> Subject: Call for articles - OSGeo Newsletter<br /> Date: March 5, 2007 11:14:56 AM PST (CA)<br /> To: discuss@lists.osgeo.org<br /> <br /> The OSGeo Newsletter development team invites you to contribute news, articles, event summaries, programming tutorials and more for the upcoming OSGeo News - Volume 1. There are several sections planned for the newsletter. General descriptions of each category can be found on the Newsletter wiki page [1]. Specific committed articles are listed on the Newsletter Volume 1 wiki page [2].<br /> <br /> There has been already been a lot of interest to contribute articles and some sections are already quite full. You are welcome to propose an article for any section, but we are specifically looking for more articles in the following categories:<br /> <br /> * News - any particularly newsworthy items you would like to pass along<br /> * Event Reports - have a conference summary that you would like to share?<br /> * Topical Studies - introduce a theoretical topic that is of general interest<br /> * Programming Tutorials - serving as an introduction to coding an application or task<br /> * Interview - conduct an interview with someone in the community<br /> * Developer Announcements - brief summaries of what your project team has been doing recently and future outlook for the project<br /> <br /> To volunteer for an article add your name and article title to the Volume 1 wiki page in the appropriate category, along with contact information. Or join the Newsletter mailing list [3] and tell us about your idea. An editor will follow-up with you to arrange delivery and timing. Articles need to be delivered by March 23st. Length can vary depending on type of article and should be discussed with the editor for your category. If you want to contribute but a particular category is full (or you need more time), you are more than welcome to add yourself to the list of articles for the subsequent volume, Volume 2 [4].<br /> <br /> We look forward to working with you on producing a great newsletter that is of interest to everyone in our communities and beyond.<br /> <br /> Sincerely,<br /> Tyler<br /> <br /> [1] Newsletter general wiki page: http://wiki.osgeo.org/index.php/Newsletter<br /> [2] Newsletter Volume 1 wiki page: http://wiki.osgeo.org/index.php/Newsletter_Volume_1<br /> [3] Newsletter development mailing list: http://lists.osgeo.org/mailman/listinfo/newsletter<br /> [4] Newsletter Volume 2 (future): http://wiki.osgeo.org/index.php/Newsletter_Volume_2</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=GeoConnexion_Column&diff=14036 2007-04-24T20:45:11Z

<p>Wiki-Danames: </p> <hr /> <div>This is the home page for &quot;Open Sources&quot;, the OSGeo column in [http://www.geoconnexion.com/ GeoConnexion magazine]. Contact mpg if you're interested in helping out.<br /> <br /> <br /> ==Editorial Calender ==<br /> <br /> * May 2007 - (1) introductory column (Michael P. Gerlek) <br /> ** ''completed''<br /> <br /> * June 2007 -- (2) ossimPlanet (Mark Lucas)<br /> ** final copy due April 25th<br /> ** ''waiting approval on copy edits''<br /> <br /> * July 2007 -- (3) BigTIFF (Frank Warmerdam)<br /> ** final copy due roughly May 25th<br /> ** &quot;This article would be mostly about bigtiff, but touching on it's development and deployment in the open source as well as proprietary world.&quot;<br /> ** ''in preparaion''<br /> <br /> * August 2007 -- (4) TOPP/GeoServer (Chris Holmes)<br /> ** final copy due roughly 25 June 2007<br /> ** ''not yet started''<br /> <br /> * September 2007 -- (5) MapGuide (Bob Bray)<br /> ** final copy due roughly 25 July 2007<br /> ** ''not yet started''<br /> <br /> * October 2007 -- (6) Education -- PuneetK<br /> ** final copy due roughly 25 August 2007<br /> ** ''not yet started''<br /> <br /> * November 2007 -- (7) OpenLayers + TileCache (Schuyler Erle)<br /> ** final copy due roughly 25 September 2007<br /> ** ''not yet started''<br /> <br /> * December 2007 -- (8) Mapbender ([[User:Arnulf Christl | Arnulf Christl]])<br /> ** final copy due roughly 25 October 2007<br /> ** ''not yet started''<br /> <br /> * January 2008 -- (9) MapServer (Steve Lime)<br /> ** final copy due roughly 25 November 2007<br /> ** ''not yet started''<br /> <br /> * February 2008 -- (10) GRASS (Markus Neteler)<br /> ** final copy due roughly 25 December 2007<br /> ** ''not yet started''<br /> <br /> * March 2008 -- (11) GeoNetwork (Jeroen Ticheler)<br /> ** final copy due roughly 25 January 2008<br /> ** ''not yet started''<br /> <br /> * April 2008 -- (12) Public GeoData (Jo Walsh)<br /> ** final copy due roughly 25 February 2008<br /> ** ''not yet started''<br /> <br /> * May 2008 -- (13) MapBuilder (Cameron Shorter)<br /> ** final copy due roughly 25 March 2008<br /> ** ''not yet started''<br /> <br /> * Other Future Topics<br /> ** ''[topic?]'' -- Gary Watry<br /> ** ''[topic?]'' -- Daniel Ames: &quot;MapWindow: Open Source GIS for the .NET Framework&quot; or &quot;MapWindow GIS and the BASINS Watershed Modeling System&quot;<br /> <br /> ** ChrisH: &quot;I could also do something like show how GeoTools fosters uDig and GeoServer and how play in to one another, advances in one get picked up by the others, in a virtuous circle.&quot;<br /> <br /> <br /> <br /> ==Editorial Notes (from Jeff Thurston)==<br /> <br /> '''(1)''' A column in our magazine is 1 page in length. An example is [http://www.geoconnexion.com/uploads/kevinpomfret_intv6i1.pdf here]. Total number of words is about 800. It can be less but not more. If you wish to add an image, then shoot for around 600 words. Try to include the writer's pic at 300 dpi and their affiliation and email - this lets readers identify with the person writing and provides a point of contact.<br /> <br /> '''(2)''' Images are a big issue for hardcopy print, especially computer images because they are only 72 dpi usually. Print quality is 300 dpi. That means 300 pixels per square inch for the print process. Most screen captures are reduced to 1/5th their original size when printed - usually causing us to throw them out because they represent the content poorly. Stretching a 72 dpi image to resize it means one still ends up with a 72 dpi image, only bigger. Please aim for 300 dpi if submitting images.<br /> <br /> '''(3)''' Content - My policy is to support expression. Someone writes it, I'll support it. I only edit for spelling, grammar and what I consider to be outright libelous. The writer should stand behind their expression. As I mentioned earlier, I am not a programmer. I need your help to peer review programming content (which is why the 'contact point' ) will work well. Ultimately everything in the column will reflect on OSGeo. It's your column, you choose the content. Our Media Pack describes Themes for issues by edition throughout the year. I use these as a guideline.<br /> <br /> '''(4)''' Reprint - I am a supporter of the creator maintaining all rights. Whomever submits material owns it as far as I am concerned. All I ask is that we have first right to print (we compete on the basis originality). Once printed, you may do whatever you wish with the material, you own it. We usually archive it online and columns are available for distribution online. Since hardcopy prints are a fixed cost, they can be purchased if anyone wants a few hundred. I don't know the cost, a marketing person can help if needed. Our Media Pack is [http://www.geoconnexion.com/downloads/media_pack2007.pdf here].<br /> <br /> '''(5)''' Timeline - I am usually working 90-100 days ahead of time. Be aware that there is delay in hardcopy and get material in early. On the flip side, we publish our articles to online almost immediately after hardcopy production.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=GeoConnexion_Column&diff=14035 2007-04-24T20:42:04Z

<p>Wiki-Danames: </p> <hr /> <div>This is the home page for &quot;Open Sources&quot;, the OSGeo column in [http://www.geoconnexion.com/ GeoConnexion magazine]. Contact mpg if you're interested in helping out.<br /> <br /> <br /> ==Editorial Calender ==<br /> <br /> * May 2007 - (1) introductory column (Michael P. Gerlek) <br /> ** ''completed''<br /> <br /> * June 2007 -- (2) ossimPlanet (Mark Lucas)<br /> ** final copy due April 25th<br /> ** ''waiting approval on copy edits''<br /> <br /> * July 2007 -- (3) BigTIFF (Frank Warmerdam)<br /> ** final copy due roughly May 25th<br /> ** &quot;This article would be mostly about bigtiff, but touching on it's development and deployment in the open source as well as proprietary world.&quot;<br /> ** ''in preparaion''<br /> <br /> * August 2007 -- (4) TOPP/GeoServer (Chris Holmes)<br /> ** final copy due roughly 25 June 2007<br /> ** ''not yet started''<br /> <br /> * September 2007 -- (5) MapGuide (Bob Bray)<br /> ** final copy due roughly 25 July 2007<br /> ** ''not yet started''<br /> <br /> * October 2007 -- (6) Education -- PuneetK<br /> ** final copy due roughly 25 August 2007<br /> ** ''not yet started''<br /> <br /> * November 2007 -- (7) OpenLayers + TileCache (Schuyler Erle)<br /> ** final copy due roughly 25 September 2007<br /> ** ''not yet started''<br /> <br /> * December 2007 -- (8) Mapbender ([[User:Arnulf Christl | Arnulf Christl]])<br /> ** final copy due roughly 25 October 2007<br /> ** ''not yet started''<br /> <br /> * January 2008 -- (9) MapServer (Steve Lime)<br /> ** final copy due roughly 25 November 2007<br /> ** ''not yet started''<br /> <br /> * February 2008 -- (10) GRASS (Markus Neteler)<br /> ** final copy due roughly 25 December 2007<br /> ** ''not yet started''<br /> <br /> * March 2008 -- (11) GeoNetwork (Jeroen Ticheler)<br /> ** final copy due roughly 25 January 2008<br /> ** ''not yet started''<br /> <br /> * April 2008 -- (12) Public GeoData (Jo Walsh)<br /> ** final copy due roughly 25 February 2008<br /> ** ''not yet started''<br /> <br /> * May 2008 -- (13) MapBuilder (Cameron Shorter)<br /> ** final copy due roughly 25 March 2008<br /> ** ''not yet started''<br /> <br /> * Other Future Topics<br /> ** ''[topic?]'' -- Gary Watry<br /> ** ''[topic?]'' -- Daniel Ames: MapWindow GIS and the BASINS Watershed Modeling System<br /> ** ChrisH: &quot;I could also do something like show how GeoTools fosters uDig and GeoServer and how play in to one another, advances in one get picked up by the others, in a virtuous circle.&quot;<br /> <br /> <br /> <br /> ==Editorial Notes (from Jeff Thurston)==<br /> <br /> '''(1)''' A column in our magazine is 1 page in length. An example is [http://www.geoconnexion.com/uploads/kevinpomfret_intv6i1.pdf here]. Total number of words is about 800. It can be less but not more. If you wish to add an image, then shoot for around 600 words. Try to include the writer's pic at 300 dpi and their affiliation and email - this lets readers identify with the person writing and provides a point of contact.<br /> <br /> '''(2)''' Images are a big issue for hardcopy print, especially computer images because they are only 72 dpi usually. Print quality is 300 dpi. That means 300 pixels per square inch for the print process. Most screen captures are reduced to 1/5th their original size when printed - usually causing us to throw them out because they represent the content poorly. Stretching a 72 dpi image to resize it means one still ends up with a 72 dpi image, only bigger. Please aim for 300 dpi if submitting images.<br /> <br /> '''(3)''' Content - My policy is to support expression. Someone writes it, I'll support it. I only edit for spelling, grammar and what I consider to be outright libelous. The writer should stand behind their expression. As I mentioned earlier, I am not a programmer. I need your help to peer review programming content (which is why the 'contact point' ) will work well. Ultimately everything in the column will reflect on OSGeo. It's your column, you choose the content. Our Media Pack describes Themes for issues by edition throughout the year. I use these as a guideline.<br /> <br /> '''(4)''' Reprint - I am a supporter of the creator maintaining all rights. Whomever submits material owns it as far as I am concerned. All I ask is that we have first right to print (we compete on the basis originality). Once printed, you may do whatever you wish with the material, you own it. We usually archive it online and columns are available for distribution online. Since hardcopy prints are a fixed cost, they can be purchased if anyone wants a few hundred. I don't know the cost, a marketing person can help if needed. Our Media Pack is [http://www.geoconnexion.com/downloads/media_pack2007.pdf here].<br /> <br /> '''(5)''' Timeline - I am usually working 90-100 days ahead of time. Be aware that there is delay in hardcopy and get material in early. On the flip side, we publish our articles to online almost immediately after hardcopy production.</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=Potential_Nominees_for_Next_Membership_Election&diff=12727 2007-03-16T00:57:47Z

<p>Wiki-Danames: Adding myself to the list of potential new charter members.</p> <hr /> <div>This is a list of potential nominees for the next general membership election. For now it's enough to put some brief indicator of what the nominees' claims to fame are. When the official nomination period opens up, be sure to submit the names you put here via the &quot;official&quot; process that will be announced then. <br /> <br /> * Gillies, Sean - MapServer, ZCO, PrimaGIS<br /> * Kralidis, Tom - MapServer, WMS clients, WMS Context clients<br /> * McNierney, Ed - MapServer, TopoZone.com<br /> * Mueller, Markus U. - deegree.org, lat/lon GmbH<br /> * Wagner, Jan-Oliver - Freegis.org, Thuban, Intevation.net<br /> * Ames, Daniel P. - MapWindow Project, Idaho State University <br /> <br /> [[Category:Membership]]</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=FOSS4G2007_Communication&diff=11665 2007-02-22T00:08:31Z

<p>Wiki-Danames: </p> <hr /> <div>[[FOSS4G2007]]<br /> <br /> == Marketing Events ==<br /> <br /> The text of announcements is stored on the [[FOSS4G2007_Announcements]] page. The following events should trigger a wave of e-mail marketing to the four corners of the open source world:<br /> <br /> * &lt;strike&gt;Call for Workshops&lt;/strike&gt;<br /> * Call for Presentations<br /> * Opening of Registration<br /> * End of Early Bird Registration<br /> <br /> == E-Mail Marketing ==<br /> <br /> Here is a list of lists and posters we should use to propagate this message:<br /> <br /> * postgis-users, Paul Ramsey<br /> * gmt, Paul Ramsey<br /> * freegis, Paul Ramsey<br /> * geotools-devel, Jody Garnett<br /> * gt2-users-list, Jody Garnett<br /> * udig-devel, Jody Garnett<br /> * geoserver-devel, Jody Garnett<br /> * mapserver-users, Steve Lime<br /> * mapguide-users, Bob Bray<br /> * qgis-user, Gary Sherman<br /> * grass-dev and grassuser, Markus Neteler<br /> * osgeo announce, Frank Warmerdam<br /> * gdal-dev, Frank Warmerdam<br /> * worldwind, Chad Zimmerman<br /> * openlayers, Chris Schmidt<br /> * mapbender, Arnulf Christl<br /> * ossim, Mark Lucus<br /> * jump (jump-users and openjump lists), Landon Blake<br /> * gvsig, trying gvsig at gva.es to start<br /> * opengis/geosptatial, Sam Bacharach<br /> * sharpmap?<br /> * mapnik, Artem Pavlenko<br /> * geowankers, Allan Doyle<br /> * kamap-users, -dev, Paul Spencer<br /> * mapbuilder-users, -dev, Cameron Shorter<br /> * eogeo, Allan Doyle<br /> * CEOS WGISS lists, Allan Doyle<br /> * NASA ESIP lists, Perry Nacionales<br /> * MapStorer lists, Sebastian Schmitz<br /> * Chameleon lists, Paul Spencer<br /> * Geonetwork lists, Jeroen Ticheler<br /> * osgeo discuss, Tyler Mitchell<br /> * mapserver-west, Tyler Mitchell<br /> * MapWindow announce list, Dan Ames<br /> * ''More Please...''<br /> <br /> == Paper Marketing ==<br /> <br /> We will be doing one mail-out coinciding with the opening of registration. This mail out will go to:<br /> <br /> * Some OSGIS 2005 attendees<br /> ** Students and folks we know will hear about the conference anyways need to be stripped from the list<br /> * Some FOSS4G 2006 attendees<br /> ** Students and folks we know will hear about the conference anyways need to be stripped from the list<br /> * GIS offices and companies in the Pacific Northwest<br /> ** Manually generated list<br /> * Some GeoWorld subscribers (?)<br /> ** Need to choose which states to send to. Entire list is too big.<br /> * Some Geospatial Solutions subscribers (?)<br /> ** Need to choose which states to send to. Entire list is too big.<br /> <br /> == Web Marketing ==<br /> <br /> Placing banner ads one some of the high-traffic open source project sites is a huge source of referrals. The conference web site already receives the majority of its referrals from open source web site announcements, with GRASS as the top site so far.<br /> <br /> Banner placement should probably proceed in earnest after the opening of registration.<br /> <br /> The following sites have committed to doing banner placement:<br /> <br /> * GRASS (Markus Neteler)<br /> * PostGIS (Paul Ramsey)<br /> * Mapserver (Steve Lime)<br /> * MapWindow (Dan Ames) - Banner added to [http://www.MapWindow.org wwww.MapWindow.org] main page 21 Feb 2007<br /> <br /> Here are some graphics. Please make up more and add them to this list:<br /> <br /> [[Image:Horz_banner_468_58.jpg]]<br /> <br /> [[Image:Horz_banner_728_90.jpg]]<br /> <br /> [[Image:Horz_foss4g_468_58.png]]<br /> <br /> [[Image:Vert_foss4g07_180_150.png]]<br /> <br /> This is the official conference logo, in PDF format, for use in creating new graphic elements:<br /> <br /> [[Media:FOSS4G_Logo_presentation_v2.pdf]]<br /> <br /> http://postgis.refractions.net/FOSS4G_Logo_Final.eps<br /> <br /> == Industry Event Calendars ==<br /> <br /> We have been adding ourselves to industry event calendars wherever possible. So far, we are on:<br /> <br /> * http://www.eoportal.org<br /> * http://www.opengeospatial.org/event<br /> * http://www.gsdi.org/events/upcnf.asp<br /> * http://gcmd.nasa.gov/ConferenceCalendar/calendar.html<br /> * http://www.gisdevelopment.net/events/index.asp<br /> * http://www.eogeo.org/events<br /> * http://www.allconferences.com/ (login as osgeo password incubate)<br /> * Mapserver web Event Calendar (Steve Lime)<br /> * GRASS web Event Calendar (Markus Neteler)<br /> * http://www.directionsmag.com/events/<br /> * http://www.GeoPlace.com<br /> * http://gita.org/events/events.asp<br /> * http://www.urisa.org/node/148 <br /> * http://events.geocomm.com/events/<br /> * http://www.giscafe.com<br /> * http://www.gim-international.com/<br /> * ''More Please...''</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=FOSS4G2007_Communication&diff=11664 2007-02-22T00:02:41Z

<p>Wiki-Danames: </p> <hr /> <div>[[FOSS4G2007]]<br /> <br /> == Marketing Events ==<br /> <br /> The text of announcements is stored on the [[FOSS4G2007_Announcements]] page. The following events should trigger a wave of e-mail marketing to the four corners of the open source world:<br /> <br /> * &lt;strike&gt;Call for Workshops&lt;/strike&gt;<br /> * Call for Presentations<br /> * Opening of Registration<br /> * End of Early Bird Registration<br /> <br /> == E-Mail Marketing ==<br /> <br /> Here is a list of lists and posters we should use to propagate this message:<br /> <br /> * postgis-users, Paul Ramsey<br /> * gmt, Paul Ramsey<br /> * freegis, Paul Ramsey<br /> * geotools-devel, Jody Garnett<br /> * gt2-users-list, Jody Garnett<br /> * udig-devel, Jody Garnett<br /> * geoserver-devel, Jody Garnett<br /> * mapserver-users, Steve Lime<br /> * mapguide-users, Bob Bray<br /> * qgis-user, Gary Sherman<br /> * grass-dev and grassuser, Markus Neteler<br /> * osgeo announce, Frank Warmerdam<br /> * gdal-dev, Frank Warmerdam<br /> * worldwind, Chad Zimmerman<br /> * openlayers, Chris Schmidt<br /> * mapbender, Arnulf Christl<br /> * ossim, Mark Lucus<br /> * jump (jump-users and openjump lists), Landon Blake<br /> * gvsig, trying gvsig at gva.es to start<br /> * opengis/geosptatial, Sam Bacharach<br /> * sharpmap?<br /> * mapnik, Artem Pavlenko<br /> * geowankers, Allan Doyle<br /> * kamap-users, -dev, Paul Spencer<br /> * mapbuilder-users, -dev, Cameron Shorter<br /> * eogeo, Allan Doyle<br /> * CEOS WGISS lists, Allan Doyle<br /> * NASA ESIP lists, Perry Nacionales<br /> * MapStorer lists, Sebastian Schmitz<br /> * Chameleon lists, Paul Spencer<br /> * Geonetwork lists, Jeroen Ticheler<br /> * osgeo discuss, Tyler Mitchell<br /> * mapserver-west, Tyler Mitchell<br /> * MapWindow announce list, Dan Ames<br /> * ''More Please...''<br /> <br /> == Paper Marketing ==<br /> <br /> We will be doing one mail-out coinciding with the opening of registration. This mail out will go to:<br /> <br /> * Some OSGIS 2005 attendees<br /> ** Students and folks we know will hear about the conference anyways need to be stripped from the list<br /> * Some FOSS4G 2006 attendees<br /> ** Students and folks we know will hear about the conference anyways need to be stripped from the list<br /> * GIS offices and companies in the Pacific Northwest<br /> ** Manually generated list<br /> * Some GeoWorld subscribers (?)<br /> ** Need to choose which states to send to. Entire list is too big.<br /> * Some Geospatial Solutions subscribers (?)<br /> ** Need to choose which states to send to. Entire list is too big.<br /> <br /> == Web Marketing ==<br /> <br /> Placing banner ads one some of the high-traffic open source project sites is a huge source of referrals. The conference web site already receives the majority of its referrals from open source web site announcements, with GRASS as the top site so far.<br /> <br /> Banner placement should probably proceed in earnest after the opening of registration.<br /> <br /> The following sites have committed to doing banner placement:<br /> <br /> * GRASS (Markus Neteler)<br /> * PostGIS (Paul Ramsey)<br /> * Mapserver (Steve Lime)<br /> * MapWindow (Dan Ames) - Banner added to www.mapwindow.org main page 21 Feb 2007<br /> <br /> Here are some graphics. Please make up more and add them to this list:<br /> <br /> [[Image:Horz_banner_468_58.jpg]]<br /> <br /> [[Image:Horz_banner_728_90.jpg]]<br /> <br /> [[Image:Horz_foss4g_468_58.png]]<br /> <br /> [[Image:Vert_foss4g07_180_150.png]]<br /> <br /> This is the official conference logo, in PDF format, for use in creating new graphic elements:<br /> <br /> [[Media:FOSS4G_Logo_presentation_v2.pdf]]<br /> <br /> http://postgis.refractions.net/FOSS4G_Logo_Final.eps<br /> <br /> == Industry Event Calendars ==<br /> <br /> We have been adding ourselves to industry event calendars wherever possible. So far, we are on:<br /> <br /> * http://www.eoportal.org<br /> * http://www.opengeospatial.org/event<br /> * http://www.gsdi.org/events/upcnf.asp<br /> * http://gcmd.nasa.gov/ConferenceCalendar/calendar.html<br /> * http://www.gisdevelopment.net/events/index.asp<br /> * http://www.eogeo.org/events<br /> * http://www.allconferences.com/ (login as osgeo password incubate)<br /> * Mapserver web Event Calendar (Steve Lime)<br /> * GRASS web Event Calendar (Markus Neteler)<br /> * http://www.directionsmag.com/events/<br /> * http://www.GeoPlace.com<br /> * http://gita.org/events/events.asp<br /> * http://www.urisa.org/node/148 <br /> * http://events.geocomm.com/events/<br /> * http://www.giscafe.com<br /> * http://www.gim-international.com/<br /> * ''More Please...''</div>

Wiki-Danames https://wiki.osgeo.org/w/index.php?title=FOSS4G2007_Communication&diff=11663 2007-02-22T00:01:37Z

<p>Wiki-Danames: Adding MapWindow to the email list</p> <hr /> <div>[[FOSS4G2007]]<br /> <br /> == Marketing Events ==<br /> <br /> The text of announcements is stored on the [[FOSS4G2007_Announcements]] page. The following events should trigger a wave of e-mail marketing to the four corners of the open source world:<br /> <br /> * &lt;strike&gt;Call for Workshops&lt;/strike&gt;<br /> * Call for Presentations<br /> * Opening of Registration<br /> * End of Early Bird Registration<br /> <br /> == E-Mail Marketing ==<br /> <br /> Here is a list of lists and posters we should use to propagate this message:<br /> <br /> * postgis-users, Paul Ramsey<br /> * gmt, Paul Ramsey<br /> * freegis, Paul Ramsey<br /> * geotools-devel, Jody Garnett<br /> * gt2-users-list, Jody Garnett<br /> * udig-devel, Jody Garnett<br /> * geoserver-devel, Jody Garnett<br /> * mapserver-users, Steve Lime<br /> * mapguide-users, Bob Bray<br /> * qgis-user, Gary Sherman<br /> * grass-dev and grassuser, Markus Neteler<br /> * osgeo announce, Frank Warmerdam<br /> * gdal-dev, Frank Warmerdam<br /> * worldwind, Chad Zimmerman<br /> * openlayers, Chris Schmidt<br /> * mapbender, Arnulf Christl<br /> * ossim, Mark Lucus<br /> * jump (jump-users and openjump lists), Landon Blake<br /> * gvsig, trying gvsig at gva.es to start<br /> * opengis/geosptatial, Sam Bacharach<br /> * sharpmap?<br /> * mapnik, Artem Pavlenko<br /> * geowankers, Allan Doyle<br /> * kamap-users, -dev, Paul Spencer<br /> * mapbuilder-users, -dev, Cameron Shorter<br /> * eogeo, Allan Doyle<br /> * CEOS WGISS lists, Allan Doyle<br /> * NASA ESIP lists, Perry Nacionales<br /> * MapStorer lists, Sebastian Schmitz<br /> * Chameleon lists, Paul Spencer<br /> * Geonetwork lists, Jeroen Ticheler<br /> * osgeo discuss, Tyler Mitchell<br /> * mapserver-west, Tyler Mitchell<br /> * MapWindow announce list, Dan Ames<br /> * ''More Please...''<br /> <br /> == Paper Marketing ==<br /> <br /> We will be doing one mail-out coinciding with the opening of registration. This mail out will go to:<br /> <br /> * Some OSGIS 2005 attendees<br /> ** Students and folks we know will hear about the conference anyways need to be stripped from the list<br /> * Some FOSS4G 2006 attendees<br /> ** Students and folks we know will hear about the conference anyways need to be stripped from the list<br /> * GIS offices and companies in the Pacific Northwest<br /> ** Manually generated list<br /> * Some GeoWorld subscribers (?)<br /> ** Need to choose which states to send to. Entire list is too big.<br /> * Some Geospatial Solutions subscribers (?)<br /> ** Need to choose which states to send to. Entire list is too big.<br /> <br /> == Web Marketing ==<br /> <br /> Placing banner ads one some of the high-traffic open source project sites is a huge source of referrals. The conference web site already receives the majority of its referrals from open source web site announcements, with GRASS as the top site so far.<br /> <br /> Banner placement should probably proceed in earnest after the opening of registration.<br /> <br /> The following sites have committed to doing banner placement:<br /> <br /> * GRASS (Markus Neteler)<br /> * PostGIS (Paul Ramsey)<br /> * Mapserver (Steve Lime)<br /> * MapWindow (Dan Ames)<br /> <br /> Here are some graphics. Please make up more and add them to this list:<br /> <br /> [[Image:Horz_banner_468_58.jpg]]<br /> <br /> [[Image:Horz_banner_728_90.jpg]]<br /> <br /> [[Image:Horz_foss4g_468_58.png]]<br /> <br /> [[Image:Vert_foss4g07_180_150.png]]<br /> <br /> This is the official conference logo, in PDF format, for use in creating new graphic elements:<br /> <br /> [[Media:FOSS4G_Logo_presentation_v2.pdf]]<br /> <br /> http://postgis.refractions.net/FOSS4G_Logo_Final.eps<br /> <br /> == Industry Event Calendars ==<br /> <br /> We have been adding ourselves to industry event calendars wherever possible. So far, we are on:<br /> <br /> * http://www.eoportal.org<br /> * http://www.opengeospatial.org/event<br /> * http://www.gsdi.org/events/upcnf.asp<br /> * http://gcmd.nasa.gov/ConferenceCalendar/calendar.html<br /> * http://www.gisdevelopment.net/events/index.asp<br /> * http://www.eogeo.org/events<br /> * http://www.allconferences.com/ (login as osgeo password incubate)<br /> * Mapserver web Event Calendar (Steve Lime)<br /> * GRASS web Event Calendar (Markus Neteler)<br /> * http://www.directionsmag.com/events/<br /> * http://www.GeoPlace.com<br /> * http://gita.org/events/events.asp<br /> * http://www.urisa.org/node/148 <br /> * http://events.geocomm.com/events/<br /> * http://www.giscafe.com<br /> * http://www.gim-international.com/<br /> * ''More Please...''</div>

Wiki-Danames