<div dir="ltr">I agree that using branches as a permanent store is problematic. <div><br></div><div>Many people unfamiliar with git find branches to be hard to find or don't know how to clone or fork a specific branch.<div><br></div><div>If we end up with too many use cases for a repo maybe we could split into new template repos by use case?<div><br></div><div>Thanks!</div><div><br></div><div>Erin</div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 1, 2019 at 1:58 PM Jared Morgan <<a href="mailto:jaredleonmorgan@gmail.com">jaredleonmorgan@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu., 1 Aug. 2019, 06:06 Cameron Shorter, <<a href="mailto:cameron.shorter@gmail.com" target="_blank">cameron.shorter@gmail.com</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><blockquote type="cite">
<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></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I disagree with this approach. Unless your suggestion was to iterate in the branches and then merge them into master we shouldn't be using branches as a permanent store. </div><div dir="auto"><br></div><div dir="auto">I'd prefer to just fork master and then have a consistent folder structure within each repo containing everything I need.</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
</blockquote></div></div></div>
_______________________________________________<br>
SeasonOfDocs mailing list<br>
<a href="mailto:SeasonOfDocs@lists.osgeo.org" target="_blank">SeasonOfDocs@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="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">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>