One of the OSGeo incubation questions is "Marketing material has been created about the project for the OSGeo Marketting Committee <http://wiki.osgeo.org/index.php/Marketing_Committee>\." [1]
However, us marketing committee could probably do a better job defining what we expect from projects in order to support marketing.
I've been thinking about this for a while, and I think part of our problem is that we have don't have a clear understanding about our marketing pipeline. Once we know what our pipeline looks like, we can then define the documents which fit that pipeline.
So attached is my thoughts on what I think our marketing pipeline is, and a start at defining what the documents should be for these deliverables.
I'm interested to hear feedback.
I see the next steps to be to build a matrix of projects and sources of documents where we can find this material. We can then prioritise which documents we expect from OSGeo projects, and which documents are desirable, or not required.
My interest is that we need a number of these documentation requirements for the LiveDVD (and we already have a definition and description for each project we support).
I'd like to expand out the level of documentation to include stock OSGeo powerpoints for the OSGeo stack. ... other material to follow.
The attached mind map was created using simplemind.
[1] http://www.osgeo.org/incubator/process/project_graduation_checklist.html
--
Cameron Shorter
Geospatial Systems Architect
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254
Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com
OSGeo Marketing.mm (4.19 KB)
OSGeo Marketing.pdf (225 KB)
Excellent Cameron, this isn't an approach I've worked through before. I
think it hits the target well.
For the matrix are you thinking of something along the lines of:
http://wiki.osgeo.org/wiki/Binary_Package_Listing - but for marketing
material?
Tyler
Cameron Shorter wrote:
One of the OSGeo incubation questions is "Marketing material has been
created about the project for the OSGeo Marketting Committee
<http://wiki.osgeo.org/index.php/Marketing_Committee>\." [1]
However, us marketing committee could probably do a better job defining
what we expect from projects in order to support marketing.
I've been thinking about this for a while, and I think part of our
problem is that we have don't have a clear understanding about our
marketing pipeline. Once we know what our pipeline looks like, we can
then define the documents which fit that pipeline.
So attached is my thoughts on what I think our marketing pipeline is,
and a start at defining what the documents should be for these
deliverables.
I'm interested to hear feedback.
I see the next steps to be to build a matrix of projects and sources of
documents where we can find this material. We can then prioritise which
documents we expect from OSGeo projects, and which documents are
desirable, or not required.
My interest is that we need a number of these documentation requirements
for the LiveDVD (and we already have a definition and description for
each project we support).
I'd like to expand out the level of documentation to include stock OSGeo
powerpoints for the OSGeo stack. ... other material to follow.
The attached mind map was created using simplemind.
[1]
http://www.osgeo.org/incubator/process/project_graduation_checklist.html
------------------------------------------------------------------------
_______________________________________________
Marketing mailing list
Marketing@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/marketing
Tyler Mitchell (OSGeo) wrote:
Excellent Cameron, this isn't an approach I've worked through before. I
think it hits the target well.
For the matrix are you thinking of something along the lines of:
http://wiki.osgeo.org/wiki/Binary_Package_Listing - but for marketing
material?
Yes,
That is the sort of matrix I'd be looking for.
We should probably merge these two table, and also combine with the LiveDVD table of packages:
http://spreadsheets.google.com/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc&hl=en_GB
I suggest we manage in a spreadsheet, because wiki tables are so painful and time consuming to update and maintain, and because from a spreadsheet we can lookup data from other sheets to gain more information.
Tyler
Cameron Shorter wrote:
One of the OSGeo incubation questions is "Marketing material has been
created about the project for the OSGeo Marketting Committee
<http://wiki.osgeo.org/index.php/Marketing_Committee>\." [1]
However, us marketing committee could probably do a better job defining
what we expect from projects in order to support marketing.
I've been thinking about this for a while, and I think part of our
problem is that we have don't have a clear understanding about our
marketing pipeline. Once we know what our pipeline looks like, we can
then define the documents which fit that pipeline.
So attached is my thoughts on what I think our marketing pipeline is,
and a start at defining what the documents should be for these
deliverables.
I'm interested to hear feedback.
I see the next steps to be to build a matrix of projects and sources of
documents where we can find this material. We can then prioritise which
documents we expect from OSGeo projects, and which documents are
desirable, or not required.
My interest is that we need a number of these documentation requirements
for the LiveDVD (and we already have a definition and description for
each project we support).
I'd like to expand out the level of documentation to include stock OSGeo
powerpoints for the OSGeo stack. ... other material to follow.
The attached mind map was created using simplemind.
[1]
http://www.osgeo.org/incubator/process/project_graduation_checklist.html
------------------------------------------------------------------------
_______________________________________________
Marketing mailing list
Marketing@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/marketing
--
Cameron Shorter
Geospatial Systems Architect
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254
Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com