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.

= 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
 * A marketing overview of each application, targeted at a someone considering using GeoSpatial Open Source, who may be a GeoSpatial User, or Technical person without much geospatial expertise.
 * Each overview is to be available as HTML (for OSGeo Live and websites), as 1 a page PDF, (to hand out as a flier at conferences, and as a page in the OSGeo Book of projects), and as Word/OpenOffice (to be cut and pasted into project proposals and articles which usually use these formats)
 * Documentation should a structure similar to the following:
 * Overview: Address user questions of "What does the application do?", "When would I use it?", "Why would I use it over other applications?", "How mature is the application and how widely deployed is it?". Don't mention licence or open source in this section.
 * An image or 2, as per
 * Core Features: A list of the application's key features
 * Implemented Standards: List of standards
 * Application Details:
 * Licence: GPL, LGPL, BSD, ...
 * Maturity: 5 star rating as per
 * Commercial Support: URL to a web page listing companies which provide commercial support
 * URL: Url of the project

How to write an Application Overview is defined here: http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Application_Overview


 * Incubation Criteria
 * Proposed to be required for all projects


 * Responsibility
 * Project's team

= Logo =
 * 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 Quick Start =
 * Description
 * 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 run one core use case for the application.
 * It should be able to be run in 5 minutes.
 * Ideally, it will include screen snapshots, but this is not required yet.
 * It may additionally contain extra steps to cover all core functionality
 * Finishes with pointers to further training material or documentation.

How to write an Application Quick Start is defined here: Live_GIS_Add_Project


 * Incubation Criteria
 * Proposed OSGeo Incubation Requirement for non libraries from Sept 2010


 * Responsibility
 * Project's team

= OSGeo-Live Lightening Presentation = Description: This presentation is to be launched at FOSS4G 2010. It will provide a lightening overview of the (approx 40) applications and key OSGeo Libraries on the OSGeo Live DVD/Virtual Machine, with one slide/project. Each slide to take 30 to 60 seconds to present. It will also contain a few overview slides (eg: Explaining the relevant project categories)


 * Requirements from each project:
 * One slide which contains:
 * Image as per
 * 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. This should be derived from the


 * Responsibility
 * Project's team to provide project's slide
 * OSGeo Live Project to compile the remainder of the presentation


 * Incubation Criteria
 * Proposed OSGeo Incubation Requirement from Sept 2010

= Project Specific Presentation =
 * Description
 * Up to 20 min presentation for each specific project.


 * Responsibility
 * Project's team


 * Incubation Criteria
 * Not required for OSGeo Incubation

= Maturity Rating =
 * Description
 * A 5 star rating system to qualify the how established a project is. Rating is to be broken down as follows:
 * 5 stars: This rating is yet to be defined, and will not be allocated to projects yet. Project includes bundled software, regular builds, security updates, training, etc.
 * 4 stars (mature): Project has passed osgeo incubation as per: http://www.osgeo.org/incubator/process/project_graduation_checklist.html
 * 3.5 stars: Not to be used yet, but may later be introduced for projects which have entered incubation.
 * 3 stars (established): Project has Stable Software, a Stable community, is deployed in production systems, and is ready to pass criteria to enter incubation, as per: http://www.osgeo.org/incubator/process/evaluation.html
 * 2 stars (stable): Project has Stable Software.
 * Project produces periodic releases of stable software which is used in production systems.
 * 1 star (beta): Project has Beta software.


 * Responsibility
 * OSGeo Live team is responsible for ranking. (This responsibility may pass over to the incubation committee)


 * Incubation Criteria
 * Required for OSGeo Incubation

= 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

Glossary

 * Description
 * Table of acronyms, their expanded terms, and optionally one sentence explaining the term. Contains terms and accronyms used in the OSGeo Live documentation.


 * Responsibility
 * OGC and OSGeo Live team, with contributions from all documenters.

=OGC Artefacts=

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 page overview of an OGC standard to be available as 1 page pdf, 1 page word document and html
 * 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
 * Provide indication about how widely accepted the standard is. How widely has it been deployed, what applications have implemented support, etc.
 * (Hopefully to be introduced to the Live DVD from FOSS4G 2010)


 * Responsibility
 * OGC

= Technology Comparisons =
 * (Possible future OSGeo Incubation Requirement)
 * Description
 * 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.
 * Comparison projects:
 * Desktop Comparison
 * Web Mapping 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)


 * Incubation Criteria
 * Not required for incubation yet.

= Case Studies =
 * Description
 * 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).
 * Projects should link to case studies. SeeCase Studies and the OSGeo Journal for ideas.


 * Incubation Criteria
 * Not required for incubation yet.

= Training =
 * Description
 * Availability of training material for applications.
 * Training requirements and templates still to be defined.


 * Incubation Criteria
 * Not required for incubation yet.

Related Links
hvac technician