<div id="__MailbirdStyleContent" style="font-size: 8pt;font-family: Arial;color: #000000">
It has always been the rule that minor changes that you feel confident about is just pushed.<div><br></div><div>Changes to architecture or user experience should be put up for review, and possibly even discussion.</div><div>We have never required complete approval, but should carefully listen to objections and not do changes before there is at least acceptance.</div><div><br></div><div>You are co-maintainer of Words already so that gives you a big voice in how things should go</div><div><br></div><div>As for my own co-maintainership - I'm willing to give it up if you like as I will probably not have time to do actual coding. On the other hand I do continue to monitor as long as you don't ask me to step down</div><div><br></div><div>Camilla.<br><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">On 13/02/2021 11.20.55, Pierre <pinaraf@pinaraf.info> wrote:</p><div style="font-family:Arial,Helvetica,sans-serif">Hi
<br>
<br>Since the tickets and things I want to do may have varying duration, I would
<br>like to know if there is any schedule/plan set for the next major release.
<br>Depending on the timeframe, I could switch from small tickets to bigger ones
<br>more easily.
<br>On a side note, is there any rule regarding the merge requests in the project?
<br>I'm not used to this kind of tool outside company projects where there are
<br>rules like 'another contributor approval is needed' or 'every single change
<br>must go through a merge request'. For the small fixes I am pushing so far,
<br>asking for a review may be overkill…
<br>
<br>Regards
<br>
<br> Pierre</div></blockquote>
</div></div>