<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Felicity,<br>
</p>
<p>Re labels, I don't feel strongly about whether we use them or
not, but whatever we do, we aim to be consistent, and document our
decision in our Quickstart template. I'd probably err on:</p>
<p>1. Adopting whatever is commonly used by all projects.</p>
<p>2. Keeping our use of labels simple (ie, not have them if it is
not adding much value).</p>
<p>--</p>
<p>Your suggestions for raising 50 trac tickets and 50 pull requests
sound reasonable for me. I suggest doing one top-to-bottom and get
feedback before continuing with the rest.</p>
<p>Also, after reviewing a project's Quickstart, I suggest sending a
direct email to that project's point of contact(s). Most don't
monitor the OSGeoLive email list closely and will appreciate the
email.</p>
<p>You will also get a range of opinions on how hands on each person
will be with their project. Some will accept every suggestion you
make. Others will take it as guidance and then rewrite. <br>
</p>
<p>Cheers, Cameron<br>
</p>
<div class="moz-cite-prefix">On 7/10/19 6:10 pm, Nicolas Roelandt
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHbAjDRR3XTPSy1hvs0+4e6Qxv+ENaFz=YZSWVeN+PaH9qVo6Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi Felicity,
<div><br>
</div>
<div>Thanks for working on this and asking things !</div>
<div><br>
</div>
<div>For the Sphinx markup, I don't have a good response. I did
like it was made as it is part of the process.</div>
<div>But this can be questioned !</div>
<div><br>
</div>
<div>For your comments, if you don't want to change code and
make a PR, fill an issue in Trac so we can comment on it.</div>
<div><br>
</div>
<div>Trac is our main issue tracker so I think that it is better
to fill your projects tickets there too.</div>
<div><br>
</div>
<div>Thanks again,</div>
<div><br>
</div>
<div>Warm regards,</div>
<div><br>
</div>
<div>Nicolas Roelandt</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Le lun. 7 oct. 2019 à 06:57,
Felicity Brand <<a href="mailto:felicitybrand@gmail.com"
moz-do-not-send="true">felicitybrand@gmail.com</a>> a
écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello
all,<br>
<br>
I've been working on the Quick Start template and there are a
couple<br>
of questions I wanted to ask.<br>
<br>
I have come across the Sphinx markup :guilabel: and
:menuselection:<br>
What do we gain by using these? It seems to me something extra
to<br>
type. I understand we can then render them a particular way,
but if<br>
it's just going to be rendered bold it feels like more effort
than<br>
it's worth. But please let me know if I'm missing something in
my<br>
understanding here. Do we want to continue using this
convention?<br>
<br>
I'd like some guidance on my process next.<br>
At a previous meeting, we agreed that the best way for me to
give<br>
feedback would be GitHub comments. I think I need to raise a
PR in<br>
order to be able to comment on the code. But I didn't intend
on making<br>
any changes...so I'm not sure what would go in my PR. Unless I
make<br>
some kind of nominal change that we all agree on beforehand? I
suppose<br>
we'll want a PR per project quick start - so that would be
maybe 50<br>
PRs. Is that cool with everyone?<br>
<br>
My intention was to also create about 50 trac tickets, one for
each<br>
project. These would include the details of my rating score of
the<br>
quick start and perhaps a link to the relevant GitHub PR. I
thought it<br>
would be appropriate to have trac as well as GitHub so that
anyone<br>
could look at the trac ticket and pick up from there. What do
folk<br>
think about that?<br>
<br>
I'm not ready to start any GitHub work yet, but I wanted to
get<br>
discussion on this rolling so that I know what to do when that
time<br>
comes.<br>
<br>
Thanks<br>
Felicity<br>
_______________________________________________<br>
osgeolive mailing list<br>
<a href="mailto:osgeolive@lists.osgeo.org" target="_blank"
moz-do-not-send="true">osgeolive@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/osgeolive"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/osgeolive</a><br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>
<div>
<div>
<div>Bien cordialement,<br>
<br>
</div>
Nicolas Roelandt<br>
</div>
mail: <a href="mailto:roelandtn.pro@gmail.com"
target="_blank" moz-do-not-send="true">roelandtn.pro@gmail.com</a><br>
</div>
mobile: +33 (0)6 42 40 42 55<br>
</div>
twitter: <span dir="ltr"><a
href="https://twitter.com/RoelandtN42" rel="noopener"
target="_blank" moz-do-not-send="true"><span dir="ltr">@<b>RoelandtN42</b></span></a></span>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
osgeolive mailing list
<a class="moz-txt-link-abbreviated" href="mailto:osgeolive@lists.osgeo.org">osgeolive@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/osgeolive">https://lists.osgeo.org/mailman/listinfo/osgeolive</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>