<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jan 9, 2019 at 9:32 AM Peter von Kaehne <<a href="mailto:refdoc@gmx.net">refdoc@gmx.net</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">On Wed, 2019-01-09 at 14:53 +0000, David Haslam wrote:<br>
<br>
> Not sure if this was the wisest structure for what we are doing<br>
> here. <br>
<br>
No, possibly not. You start with one thing and then change it about<br>
until it fits. I have also created several other repos to which others<br>
only have access. <br></blockquote><div><br></div><div>If there is one repo per module, then it would become relatively simple to create automation to build and release modules into an alpha repository (or even have one-repo-per-module for an alpha build) that regenerates automatically every time the module's repository is pushed to. It also gives the easiest way to have access control on a per-module basis, giving one user ownership over their module without needing to have access to a shared repository. A shared repo for something that can potentially have so many owners can lead to a narrower bottleneck as you would have to approve every PR/MR for any module.</div><div><br></div><div>--Greg</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div></div>