<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">On 1/8/19 12:11 am, Clarence Cromwell
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:729953BA-4A9B-4A15-BD57-C768C24E562A@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
+1
<div><br>
</div>
<div>What are the “types” of templates? That could mean that
they’re sorted by use case or by exact document (such as
QuickStart). <br>
</div>
</blockquote>
For our master repository, where we focus on quality over quantity,
I believe we sort by document type (such as Quickstart). <br>
<blockquote type="cite"
cite="mid:729953BA-4A9B-4A15-BD57-C768C24E562A@gmail.com">
<div><br>
</div>
<div>I’d suggest folders for each set of example templates
(provided by contributors) so that end users can refer to the
originals if they want to. They’ll also be worth preserving if
we decide to revisit our official versions later on.</div>
</blockquote>
<p>I suggest we additionally have a bunch of git branches, each
branch can focus on a use case, such as "Minimum Viable Docset for
Mobile Apps".</p>
<p>In future we could potentially add all good use cases into a
separate product, a suite of best practice examples. <br>
</p>
<p>Erin, I suggest you initially put your templates into a "dev" or
"development" branch, which we can then ruthlessly
review/trim/refine/merge with something else/...<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:729953BA-4A9B-4A15-BD57-C768C24E562A@gmail.com">
<div><br>
</div>
<div>Do we need more than one blessed template for any document
type? Can we cover various use cases either by describing a
different set of documents (a different minimum viable docset)
or by flexibility within the template? <br>
</div>
</blockquote>
<p>I think we should aim for one document per doctype, with
flexibility within the template. And that is what we produce for a
release 1.0.</p>
<p>But I expect that over time we will discover reasons to have a
few documents per doctype. (Similar to Creative Commons having
CC0, CC-By, CC-By-SA, ...)<br>
</p>
<blockquote type="cite"
cite="mid:729953BA-4A9B-4A15-BD57-C768C24E562A@gmail.com">
<div><br>
<br>
<div id="AppleMailSignature" dir="ltr">Sent from my iPhone</div>
<div dir="ltr"><br>
On Jul 31, 2019, at 4:45 AM, Jared Morgan <<a
href="mailto:jaredleonmorgan@gmail.com"
moz-do-not-send="true">jaredleonmorgan@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="auto">
<div>+1
<div dir="auto"><br>
</div>
<div dir="auto">This is going to be our "product" so it
needs to attract it's own repo stars and unique forks.</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed., 31 Jul.
2019, 07:46 Erin McKean, <<a
href="mailto:emckean@google.com"
moz-do-not-send="true">emckean@google.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi folks!
<div><br>
As discussed in today's meeting, should we have
a separate repo just for templates? This would
be CC-0 licensed and the "how-to" documentation
would link to it.</div>
<div><br>
</div>
<div>Structure TBD, but the general idea would be
to have folders for types of templates and then
'blessed' examples for each use case. </div>
<div><br>
</div>
<div>E.g. for READMEs, the structure would be: </div>
<div>-- Templates repo</div>
<div> -- CONTRIBUTING.md</div>
<div> -- LICENSE.md</div>
<div> -- READMEs folder</div>
<div> README.md (this is the blessed
template)</div>
<div> OTHER READMES folder (these would be
other examples)</div>
<div> README_README.md (the README for how to
use the README template ...🤔 perhaps this
wasn't a very clear example)</div>
<div> <br clear="all">
<div>Please +1/-1/0 to show your approval,
rejection, or 'meh' reactions before next
week's meeting if possible? </div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
Erin </div>
<div><br>
</div>
-- <br>
<div dir="ltr"
class="m_6868867341844553930gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div
style="line-height:1.5em;padding-top:10px;margin-top:10px;color:rgb(85,85,85);font-family:sans-serif"><span
style="border-width:2px 0px
0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2px;margin-top:2px">Erin
McKean |</span><span
style="border-width:2px 0px
0px;border-style:solid;border-color:rgb(51,105,232);padding-top:2px;margin-top:2px"> Developer
Relations Program Manager, Open
Source Strategy |</span><span
style="border-width:2px 0px
0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;margin-top:2px"> <a
href="mailto:emckean@google.com"
target="_blank" rel="noreferrer"
moz-do-not-send="true">emckean@google.com</a> |</span><span
style="border-width:2px 0px
0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;margin-top:2px"> she/her</span></div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org"
target="_blank" rel="noreferrer"
moz-do-not-send="true">SeasonOfDocs@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><span>_______________________________________________</span><br>
<span>SeasonOfDocs mailing list</span><br>
<span><a href="mailto:SeasonOfDocs@lists.osgeo.org"
moz-do-not-send="true">SeasonOfDocs@lists.osgeo.org</a></span><br>
<span><a
href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a></span><br>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
SeasonOfDocs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SeasonOfDocs@lists.osgeo.org">SeasonOfDocs@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</body>
</html>