[Live-demo] [Marketing] code sprint, content migration, generation starts now

[Jody Garnett]

Cameron please check meeting history; your current suggestions are counter
productive.

I understand you would like the osgeo live team to be respected (they are)
and combine forces long term to reduce overall effort. This team of
volunteer is focused on a very short three week deadline - and only has
time for your help.

Quickly:
- we are creating a template for information sheets (geoforall and osgeo
only at this time). Project teams  and others are welcome to use this
template.
- the forms are for the website/rebranding
- long term maintenance is out of scope; project teams will have edit
accesss to the website.

On Mon, Jul 24, 2017 at 5:20 AM Cameron Shorter <cameron.shorter at gmail.com>
wrote:

> Hi Jody,
>
> I think it might be helpful to discuss this in real time online. The
> osgeo-live weekly meeting will be in ~ 10 hours if you want to drop by:
>
> irc://freenode.net#osgeolive
>
>
> https://www.timeanddate.com/worldclock/meetingdetails.html?hour=20&min=30&sec=0&p1=179&p2=189&p3=224&p4=22&p5=240&p6=196&p7=215
>
> If I understand correctly, there is currently budget and intent to create
> project write ups, without a strategy for long term maintenance. If that is
> the case, I suggest not creating such material at all. Rather just create a
> list of projects which references either the projects directly, or
> OSGeo-Live project overviews. I'm ok with Project Overviews being copied
> verbatim, but I'm not ok with creating slight variant on the Project
> Overviews.
>
> For projects (such as some community projects, which haven't created a
> project overview for OSGeo-Live,) I suggest using the OSGeo-Live format
> initially. Then on a future iteration of OSGeo-Live, adopt a new template
> (as proposed by the marketing committee).
>
>
>
> On 24/7/17 9:40 am, Jody Garnett wrote:
>
> Cameron this is just a stop gap as we do not have login to the beta
> website. In addition to these forms the existing osgeo live overview are
> also a source of information (perhaps these forms could add a link to osgeo
> live overview if available.)
>
> The key new information appears to be screen snaps and team photo and the
> level 1 level 2 category information (which would be interesting for osgeo
> live to adopt) and what service providers are considered contributors.
>
> The osgeo live team has been working very hard on the latest release and
> has not had capacity to work on this initiative, by the same token the
> content being gathered was established in June (the scope of this project
> is fixed and we do not have volunteers to establish consider process -
> unless you are interested).
>
> The best idea I have heard is about.yaml or similar being committee into
> each repo and used to generate one page flyers, overviews and these web
> pages. However given the deadlines (some of which have passed) this idea
> has not been pursued.
>
> On Mon, Jul 24, 2017 at 12:31 AM Cameron Shorter <
> cameron.shorter at gmail.com> wrote:
>
>> All,
>>
>> There is good content in these forms. I recognise a lot of as being
>> derived from prior initiatives. Great.
>>
>> I suggest taking a step back, and asking:
>>
>> What is OSGeo's content creation and distribution pipeline?
>>
>> What product(s) are being created with this content?
>>
>> How are we going to ensure the content is being kept up to date? (The
>> original 1 page PDF fliers created for OSGeo projects was created once,
>> then became very out of date and collectively become unusable as a source
>> of truth). OSGeo-Live has a process for updating documentation with each
>> release, how can we lever that?
>>
>> How can we minimise the duplication of content creation? Duplication
>> leads to multiple points of truth getting out of date, and increases
>> maintenance. Can we extend OSGeo-Live content creation process rather than
>> creating another? Or alternatively have OSGeo-Live extend a newly created
>> process?
>>
>> Documentation processes which have potential to be aligned are:
>>
>> * OSGeo-Live documentation guide:
>> https://wiki.osgeo.org/wiki/Live_GIS_Disc#Documentation
>>
>> * Project application to join OSGeo-Live:
>> https://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
>>
>> * OSGeo incubation checklist:
>> http://www.osgeo.org/incubator/process/project_graduation_checklist.html
>>
>>
>> Cheers, Cameron
>>
>> On 22/7/17 10:44 pm, Jody Garnett wrote:
>>
>> 1) Jeffrey has started some google forms to quicklcy stage content for
>>> beta website. I will review, add descriptions and ask the people here to
>>> play test (and we can share with discuss at osgeo.org at the end of the
>>> day).
>>
>>
>> The first form is now ready, but I am not quite sure how to provide a
>> sharable URL:
>> ​
>>  Software Projects
>> <https://docs.google.com/forms/d/1zOVOTtbGzIuhcfwHg9GYrJ-NErxl_DmFnTlBM3qBndE/edit?usp=drive_web>
>> ​
>>
>> _______________________________________________
>> Marketing mailing listMarketing at lists.osgeo.orghttps://lists.osgeo.org/mailman/listinfo/marketing
>>
>>
>> --
>> Cameron Shorter
>> M +61 419 142 254
>>
>> _______________________________________________
>> Live-demo mailing list
>> Live-demo at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/live-demo
>> http://live.osgeo.org
>> http://wiki.osgeo.org/wiki/Live_GIS_Disc
>
> --
> --
> Jody Garnett
>
>
> --
> Cameron Shorter
> M +61 419 142 254
>
> --
--
Jody Garnett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/live-demo/attachments/20170724/e891cc0f/attachment.html>