<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Jody,</p>
<p>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: <br>
</p>
<p><a class="moz-txt-link-freetext" href="irc://freenode.net#osgeolive">irc://freenode.net#osgeolive</a><br>
</p>
<p><a class="moz-txt-link-freetext" href="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">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</a><br>
</p>
<p>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.</p>
<p>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).<br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 24/7/17 9:40 am, Jody Garnett wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOhbgAmXJ3YBBdTJYjds63+54Rm6HUh3p1iMvgcof3s7-AtEqw@mail.gmail.com">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.)<br>
<br>
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. <br>
<br>
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). <br>
<br>
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. <br>
<br>
<div class="gmail_quote">
<div dir="ltr">On Mon, Jul 24, 2017 at 12:31 AM Cameron Shorter
<<a href="mailto:cameron.shorter@gmail.com"
moz-do-not-send="true">cameron.shorter@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>All,</p>
<p>There is good content in these forms. I recognise a lot
of as being derived from prior initiatives. Great.</p>
<p>I suggest taking a step back, and asking:</p>
<p>What is OSGeo's content creation and distribution
pipeline? <br>
</p>
<p>What product(s) are being created with this content?<br>
</p>
<p>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?<br>
</p>
<p>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? <br>
</p>
<p>Documentation processes which have potential to be
aligned are:</p>
<p>* OSGeo-Live documentation guide: <a
class="m_-8105122450586240251moz-txt-link-freetext"
href="https://wiki.osgeo.org/wiki/Live_GIS_Disc#Documentation"
target="_blank" moz-do-not-send="true">https://wiki.osgeo.org/wiki/Live_GIS_Disc#Documentation</a></p>
<p>* Project application to join OSGeo-Live:
<a class="m_-8105122450586240251moz-txt-link-freetext"
href="https://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive"
target="_blank" moz-do-not-send="true">https://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive</a></p>
<p>* OSGeo incubation checklist: <a
class="m_-8105122450586240251moz-txt-link-freetext"
href="http://www.osgeo.org/incubator/process/project_graduation_checklist.html"
target="_blank" moz-do-not-send="true">http://www.osgeo.org/incubator/process/project_graduation_checklist.html</a><br>
</p>
<p><br>
</p>
<p>Cheers, Cameron<br>
</p>
<br>
<div class="m_-8105122450586240251moz-cite-prefix">On
22/7/17 10:44 pm, Jody Garnett wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<blockquote class="gmail_quote" style="margin:0px 0px
0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">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 <a href="mailto:discuss@osgeo.org"
target="_blank" moz-do-not-send="true">discuss@osgeo.org</a>
at the end of the day).</blockquote>
</div>
</blockquote>
</div>
<div text="#000000" bgcolor="#FFFFFF">
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>The first form is now ready, but I am not quite
sure how to provide a sharable URL:</div>
<div><br>
<div class="gmail_chip gmail_drive_chip"
style="width:396px;height:18px;max-height:18px;background-color:#f5f5f5;padding:5px;color:#222;font-family:arial;font-style:normal;font-weight:bold;font-size:13px;border:1px
solid #ddd;line-height:1"><a
href="https://docs.google.com/forms/d/1zOVOTtbGzIuhcfwHg9GYrJ-NErxl_DmFnTlBM3qBndE/edit?usp=drive_web"
style="display:inline-block;overflow:hidden;text-overflow:ellipsis;white-space:nowrap;text-decoration:none;padding:1px
0px;border:none;width:100%" target="_blank"
moz-do-not-send="true"><img
style="vertical-align:bottom;border:none"
src="https://drive-thirdparty.googleusercontent.com/16/type/application/vnd.google-apps.form"
moz-do-not-send="true"> <span dir="ltr"
style="color:#15c;text-decoration:none;vertical-align:bottom">Software
Projects</span></a></div>
<br>
</div>
</div>
</blockquote>
</div>
<div text="#000000" bgcolor="#FFFFFF">
<blockquote type="cite">
<pre>_______________________________________________
Marketing mailing list
<a class="m_-8105122450586240251moz-txt-link-abbreviated" href="mailto:Marketing@lists.osgeo.org" target="_blank" moz-do-not-send="true">Marketing@lists.osgeo.org</a>
<a class="m_-8105122450586240251moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/marketing" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/marketing</a></pre>
</blockquote>
</div>
<div text="#000000" bgcolor="#FFFFFF"> <br>
<pre class="m_-8105122450586240251moz-signature" cols="72">--
Cameron Shorter
M +61 419 142 254</pre>
</div>
_______________________________________________<br>
Live-demo mailing list<br>
<a href="mailto:Live-demo@lists.osgeo.org" target="_blank"
moz-do-not-send="true">Live-demo@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/live-demo"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/live-demo</a><br>
<a href="http://live.osgeo.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://live.osgeo.org</a><br>
<a href="http://wiki.osgeo.org/wiki/Live_GIS_Disc"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a></blockquote>
</div>
<div dir="ltr">-- <br>
</div>
<div data-smartmail="gmail_signature">
<div dir="ltr">--
<div>Jody Garnett</div>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
M +61 419 142 254</pre>
</body>
</html>