Difference between revisions of "Marketing Pipeline"

From OSGeo
Jump to navigation Jump to search
Line 61: Line 61:
  
 
== Case Studies ==
 
== Case Studies ==
; [http://wiki.osgeo.org/wiki/Case_Studies 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).
:
 
  
; [http://www.osgeo.org/ojs/index.php/journal/search/titles OSGeo Journal]
+
Requirements from each project:
:
+
* Links to case studies. See[http://wiki.osgeo.org/wiki/Case_Studies Case Studies] and the [http://www.osgeo.org/ojs/index.php/journal/search/titles OSGeo Journal] for ideas.
 +
 
 +
== Training ==

Revision as of 15:55, 29 April 2010

OSGeo has access to a number of marketing pipelines. This page identifies what these pipelines are, which then enables us to define the packaging requirements needed from each project to effectively make use the pipeline.

Refer to this Pipeline overview for a description of a marketing pipeline and why it is valuable.

Packaging Pipelines

OSGeo Live
The OSGeo Live DVD and Virtual Machine bundles up a stack of the best GeoSpatial Open Source Software on an Ubuntu/Linux DVD. It is handed out at conferences, used as the basis for OSGeo training, and handed out by projects and companies wishing to promote their software to new users.
All OSGeo applications (excluding libraries) should be available on the LiveDVD.

OSGeo Live requires the following artifacts for each project:

  • Project Definition (as a paragraph)
  • Project Overview (one page HTML overview which includes:
    • Image, probably screen snapshot. (probably 600x800 pixels?)
    • Project logo (what resolution?)
osgeo4win
UbuntuGIS / DebianGIS

Conferences

Conference Booth

Since OSGeo inception, OSGeo boothes have been a regular feature at many international and local conferences, manned by local OSGeo volunteers. A standard exhibition pack is outlined at Exhibition_Pack.

The following artifacts are required from each project:

  • Project Overview, as a one page PDF which includes:
    • Image, probably screen snapshot. (What resolution?)
    • Project logo (what resolution?)

Presentations

OSGeo evangelists regularly provide OSGeo presentations at conferences. Conference attendees regularly give a report back to their workplace outlining what their learned at the conference. What we are looking for here is a base OSGeo presentation which can be easily picked up and used at various conferences.

OSGeo-Live Lightening talk
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 OGC standards being followed by the OSGeo Web Service packages)

Requirements from each project:

  • 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
    • Notes providing a 45 sec script for the presenter. Notes may also provide background information
Webinars

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.

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
  • Database Comparison (hopefully will start to be covered at foss4g 2010)
  • Web Processing Service Comparison (still wishware)
  • Mobile Application Comparison (still wishware)

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).

Requirements from each project:

Training