Marketing Artefacts

The page defines the Marketing Artefacts required to make effective use of the OSGeo Marketing Pipeline. This list is to be referenced during the OSGeo Incubation process to ensure a project supports OSGeo marketing requirements.

= OSGeo Live =
 * Description
 * A DVD and Virtual Machine containing Open Source GeoSpatial Software, handed out at conferences around the world.


 * Incubation Criteria
 * OSGeo supported client and server applications are expected to be packaged on the OSGeo Live DVD.
 * Libraries are not expected to be bundled into OSGeo Live, unless they are incorporated in other applications.


 * Responsibility
 * OSGeo Live Project team to create DVD
 * Projects teams responsible for packaging their software in accordance with packaging guidelines below

Install script

 * Description
 * A script to install an application onto the OSGeo Live DVD, as per: Live_GIS_Build


 * Responsibility
 * Project's team

Test Description

 * Description
 * Describe how to test if the application runs on the LiveDVD as per: Live_GIS_Disc_Testing (To be replaced by Quick Start from version 4 of the Live DVD in FOSS4G 2010)


 * Responsibility
 * Project's team

Test Results

 * Description
 * Results from running test procedures for the OSGeo Live DVD as per: Live_GIS_Disc_Testing


 * Responsibility
 * Project's team

OGC Standard Context Diagrams

 * Description
 * Probably 4 or 5 context diagrams visually demonstrating the relationship between standards
 * Hopefully to be introduced to the Live DVD from FOSS4G 2010


 * Responsibility
 * OGC

OGC Standard Definition

 * Description
 * 1 paragraph
 * Can be largely derived from: http://www.opengeospatial.org/standards (probably targeted as less technical audience)
 * Covers
 * What does the standard cover
 * When would you use the standard
 * Hopefully To be introduced to the Live DVD from FOSS4G 2010


 * Responsibility
 * OGC

OGC Standard Overview

 * Description


 * 1/2 to 1 page overview
 * Provide a diagram showing the standard in context with other standards
 * Provide background as to why the standard was developed, including history. What hole does it fill.
 * Provide examples of where the standard is used
 * Explain the differences between the different versions of the standard
 * What is the reference implementation of the standard
 * See Also: Mention other similar standards
 * Possibly: Reference list of implementations of the standard (This will quickly get out of date if not continually maintained)
 * (Hopefully to be introduced to the Live DVD from FOSS4G 2010)


 * Responsibility
 * OGC

= Logo = OSGeo Incubation Requirement
 * Description
 * For packaged software:
 * A 32x32-pixel XPM icon for use by the Debian menus
 * A 48x48-pixel PNG icon for use by freedesktop.org menus
 * Background color=transparent (not white)
 * Logo is also useful for incorporating into diagrams for presentations OSGeo project descriptions


 * A future requirement would be to provide the logo in larger formats in order to be cut into presentations and similar
 * SVG version of the icon(preferable)
 * Large PNG versions of the icon - standard size still To be Determined
 * GIF versions of the image (PNG images sometimes don't seem to have their background rendered correctly in MS Powerpoint)


 * Incubation Criteria
 * Proposed to be required for all projects

= Graphical Image =
 * Description
 * Each project needs to have a .gif image, usually a screen snapshot from a 1024x768 screen, minus desktop toolbars.
 * To be used in Project Overview, Powerpoint Presentations, etc.


 * Incubation Criteria
 * Proposed to be required for all projects


 * Responsibility
 * Project's team

= Application Definition =
 * Description
 * A one paragraph definition of the project, as per: Live_GIS_Build


 * Incubation Criteria
 * Proposed to be required for all projects


 * Responsibility
 * Project's team

= Application Overview =
 * Description
 * This previously was a one page HTML document without images as per: Live_GIS_Build
 * As of May 2010, we expect to improve this as per following:
 * Available as HTML (for OSGeo Live and websites), and as 1 page PDF, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects)
 * The document should include an image as per
 * A common document structure should be used for all projects, ideas to be included in the structure include:
 * What does the application do?
 * Why should users select this application over similar applications?
 * What standards or formats does the application support?
 * Help users determine how stable the application is? How long has the project been around? Is it deployed by high profile customers (summary only)?
 * Is the application still being maintained? Does the project have a periodic release process? Does the project have processes which address quality?
 * How big is the user and developer community?
 * Where can users find commercial support?


 * Incubation Criteria
 * Proposed to be required for all projects


 * Responsibility
 * Project's team

= Application Quick Start =
 * (Proposed OSGeo Incubation Requirement for non libraries from Sept 2010)
 * Proposed to be introduced for FOSS4G 2010 as part of OSGeo Live DVD 4. It will build upon the existing Test Description.
 * Contains detailed steps showing a newbie how to set up and run a simple working instance of the software.
 * It should be able to be run in 5 to 15 minutes
 * Ideally, it will include screen snapshots
 * It may additionally cotain extra steps to cover all core functionality

= OSGeo-Live Lightening Presentation = This presentation is to be launched at FOSS4G 2010. It will provide a lightening overview of the (approx 40) packages on the OSGeo Live DVD/Virtual Machine, with one slide/package. Each slide to take 30 to 60 seconds to present. It will also contain a few overview slides (eg: Explaining the relevant OGC standards) Requirements from each project:
 * (OSGeo Incubation Requirement from Sept 2010)
 * One slide which contains:
 * Image (probably screen snapshot. 600x800 pixels)
 * Bullet points explaining at a high level what the application does, how established the project is, and why you would select it
 * Text in notes providing a 45 sec script for the presenter to read. A reference to the one page project overview, to provide the presenter with background information.

= Project Specific Presentation =
 * (Desirable, but not an OSGeo Incubation requirement)
 * Up to 20 min presentation for each specific project.

= Technology Comparisons = Comparisons between similar projects ease the technology selection process for new users wishing to determine which technology is right for them. These technology comparison summaries provide tables list available features and key selection criteria against applications.
 * (Possible future OSGeo Incubation Requirement)

Requirements from each project:
 * Maintain up to date information for the latest stable release of software, in the relevant technology comparison table.
 * Ensure that updating this information is part of the project release process.

Comparison projects:
 * Desktop Comparison
 * Web Browser Comparison
 * Web Service Comparison
 * See the WMS Shootout. WFS/WCS comparison is still wishware.
 * Database Comparison (hopefully will start to be covered at foss4g 2010)
 * Web Processing Service Comparison (still wishware)
 * Mobile Application Comparison (hopefully introduced through a talk at foss4g2010)

= Case Studies = Systems architects and project directors reduce project risk by reviewing previous implementations of technologies they are considering. Hence, case studies which describe how Open Source Geospatial has been used in previous project are very valuable. Case Studies from risk adverse organisations (like government) are usually more valuable than those from R&D organisations (like University projects).
 * (Possible future OSGeo Incubation Requirement)

Requirements from each project:
 * Links to case studies. SeeCase Studies and the OSGeo Journal for ideas.

= Training =
 * (Possible future OSGeo Incubation Requirement)
 * Availability of training material for applications
 * Training requirements and templates still to be defined.