<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi <br>
</p>
<div class="moz-cite-prefix">On 6/21/19 9:03 AM, Tim Sutton wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0CAC131A-CFB0-456C-880B-19A13B404377@kartoza.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Hi
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 21 Jun 2019, at 08:50, Matthias Kuhn <<a
href="mailto:matthias@opengis.ch" class=""
moz-do-not-send="true">matthias@opengis.ch</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><br style="caret-color: rgb(0, 0, 0);
font-family: Menlo-Regular; font-size: 14px; font-style:
normal; font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<span style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">Yes, I think it would make a lot
of sense to integrate the changelog creation directly
with labels into pull requests.</span><br
style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<br style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<span style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">Since projecta is also based on
markdown this should all play nicely together. And we
could even add an (optional) #Changelog section to the
pull requests and some other tags to automatically set
funder etc. so one could already write the whole
changelog entry during the development cycle. That
should easily pay back with all the volunteer time that
is saved during the already busy run up time to release!</span><br
style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<br style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<span style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">Resource wise, most the allocated
time in the grant proposal is for getting the service up
and running and integrating with all the notification
hooks. Parsing the content and sending it to another API
should be pretty much straightforward. The main question
would rather be if creation of new versions can also be
automated and how to decide to which version a new
feature should be sent (i.e. find out the "current"
version). The best match for this would probably be to
use github milestones. In the end I would say that this
should increase the offer by 20%.</span><br
style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<br style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none;" class="">
<span style="caret-color: rgb(0, 0, 0); font-family:
Menlo-Regular; font-size: 14px; font-style: normal;
font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
text-decoration: none; float: none; display: inline
!important;" class="">Tim, is everything ready on your
end for that?</span><br style="caret-color: rgb(0, 0,
0); font-family: Menlo-Regular; font-size: 14px;
font-style: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; text-decoration: none;"
class="">
</div>
</blockquote>
<div><br class="">
</div>
<div>So yes we would be happy to pitch in to help here. Admire
can help more immediately by getting this changelog ready
and we can work with Anita (Hapsari) to get things in place
to support PR githook thing-a-me-doodahs. (See my reply to
OP)</div>
</div>
</div>
</blockquote>
<p>Great! I started with the changelog, but it's not even close to
finished, so whatever Admire gets too on Monday will be
appreciated. And of course whatever others get to meanwhile!</p>
<p>Concerning the changelog, I think there are too possibilities:</p>
<p> * Integrate it into the service we are going to set up if the
grant proposal is accepted. This will already have some logic
builtin to cover things like also reacting to labels added after
the PR is merged etc.</p>
<p> * Bypass the grant proposal service and directly hook into the
github webhooks, which I think is what you propose.<br>
</p>
<p>I think the main advantage of the first one would be that it
could be integrated in a single tool and since we would be working
on it already it would be less effort. The second one would add
some value to projecta if it can be used for other projects too.</p>
<p>I'm happy to step back if the second one is preferred.</p>
<p>Regards</p>
<p>Matthias<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:0CAC131A-CFB0-456C-880B-19A13B404377@kartoza.com">
<div class="">
<div>
<div><br class="">
</div>
<div>Regards</div>
<div><br class="">
</div>
<div>Tim</div>
<div><br class="">
</div>
<br class="">
</div>
</div>
</blockquote>
</body>
</html>