<div dir="ltr">> It would be good to have a short page about infrastructure on <a href="http://ocaml.org">ocaml.org</a> as well -- would you (or anyone else on the thread) have suggestions for where to put this on the website?<div><br></div><div>I think it would fit best under Documentation.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 8, 2016 at 6:25 AM, Anil Madhavapeddy <span dir="ltr"><<a href="mailto:anil@recoil.org" target="_blank">anil@recoil.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear all,<br>
<br>
Thank you for all of your comments! To do a consolidated reply:<br>
<span class=""><br>
> On 7 December 2016 at 16:22, Amir Chaudhry <<a href="mailto:amc79@cam.ac.uk">amc79@cam.ac.uk</a>> wrote:<br>
><br>
</span><span class="">> The governance doc was specifically written for the <a href="http://ocaml.org" rel="noreferrer" target="_blank">ocaml.org</a> domain.<br>
> Of course, it can be modified and extended to cover other things but the management and policy around code repos was not part of the original scope.<br>
<br>
</span>Good point. It would be useful to clarify this scope though, since the governance doc makes several references to "code repositories" that are all hosted<br>
in the GitHub ocaml/ org. So it seems quite relevant to organise those code repositories under the same framework as the rest of the infrastructure that they eventually drive.<br>
<span class=""><br>
> I mention this in case anyone think it’ll be a trivial thing to add :)<br>
<br>
</span>What particular difficulties did you have in mind with extending it to cover the management of code?<br>
<span class=""><br>
> On 8 Dec 2016, at 09:28, Sylvain Le Gall <<a href="mailto:sylvain@le-gall.net">sylvain@le-gall.net</a>> wrote:<br>
><br>
> Just to make it clear to everyone:<br>
> The forge will be deprecated but I haven't made an official statement about it (pending). The official recommendation will be to migrate projects to Github, but I'll keep a STATIC website of the forge -- for the project that have no plan to migrate.<br>
</span><...><br>
<span class="">> Mass migration under an organisation is still an option for the Forge migration but:<br>
> - it will generate quite a lot of work<br>
> - lot of long discussions (some project may not want to be mass migrated to github, but would prefer GitLab or other)<br>
> - probably only 20 migrated repositories will be active afterward<br>
<br>
</span>Keeping a static copy of the existing Forge would be very useful. Regarding mass migration, I was thinking of simply git cloning the existing repositories into a mirror namespace on GitHub, and doing nothing further. Individual maintainers from the Forge could then be granted write access and/or the repositories transferred if they choose, but at a minimum simply keeping a copy of code, history and tags would provide OPAM with a useful mirror alternative to the Forge.<br>
<br>
If maintainers do want GitLab, they will have to host it themselves...<br>
<span class=""><br>
On 8 Dec 2016, at 12:55, Gemma Gordon <<a href="mailto:gg417@cl.cam.ac.uk">gg417@cl.cam.ac.uk</a>> wrote:<br>
><br>
> I wanted to help but wasn't sure how to begin with.<br>
<br>
</span>Thanks for jumping in here, Gemma! To be clear, we ("infrastructure") welcome anyone who wishes to help maintain the growing set of repositories, so please do feel free to ask clarification questions about anything that is undocumented or otherwise confusing.<br>
<span class=""><br>
> Based on comments here I've added a list of all of the repositories currently within the ocaml/ organisation to an /infrastructure/ wiki page: <a href="https://github.com/ocaml/infrastructure/wiki/OCaml-Project-Repositories" rel="noreferrer" target="_blank">https://github.com/ocaml/<wbr>infrastructure/wiki/OCaml-<wbr>Project-Repositories</a> so we can easily see what is there and where we might organise things.<br>
<br>
</span>I've edited this to add some more information. It would be good to have a short page about infrastructure on <a href="http://ocaml.org" rel="noreferrer" target="_blank">ocaml.org</a> as well -- would you (or anyone else on the thread) have suggestions for where to put this on the website? I'm keen to avoid wiki proliferation and have one place on <a href="http://ocaml.org" rel="noreferrer" target="_blank">ocaml.org</a> where people can be directed to this kind of information.<br>
<span class=""><br>
><br>
> The infrastructure wiki might be a good place to provide more of an overview of the OCaml ecosystem, and not just machine resources. Some ideas/questions:<br>
><br>
> * We can pin 6 of the main repositories to the OCaml organisation page as per the Mirage organisation page: <a href="https://github.com/mirage" rel="noreferrer" target="_blank">https://github.com/mirage</a><br>
<br>
</span>Sounds good; how about:<br>
<br>
ocaml<br>
ocaml-manual<br>
ocamlbuild<br>
opam<br>
opam-repository<br>
<a href="http://ocaml.org" rel="noreferrer" target="_blank">ocaml.org</a><br>
<br>
This covers the core compiler, OPAM and the website.<br>
<span class=""><br>
><br>
> * The wiki: <a href="https://github.com/ocaml/infrastructure/wiki" rel="noreferrer" target="_blank">https://github.com/ocaml/<wbr>infrastructure/wiki</a> is a little out of date - perhaps we could refresh/reorganise it?<br>
<br>
</span>My fault I'm afraid. I'll take a pass a bit later on...<br>
<span class=""><br>
> * Rather than migrating, we can link to other OCaml libraries that are relevant to the core <a href="http://ocaml.org" rel="noreferrer" target="_blank">ocaml.org</a> ecosystem such as <a href="https://github.com/ocaml-doc" rel="noreferrer" target="_blank">https://github.com/ocaml-doc</a>, <a href="https://github.com/the-lambda-church/merlin" rel="noreferrer" target="_blank">https://github.com/the-lambda-<wbr>church/merlin</a> that are incorporated within their own organisations<br>
> * Shall we link to other third party libraries that are important/relevant to the core compiler? e.g. Spacetime, AFL<br>
<br>
</span>This is a very good point. One of my concerns is that the various new features in OCaml are quite spread out now. Spacetime's implementation is on [either Leo or Jane Street] person repos, the ocaml-doc is its own organisation, and so on.<br>
<br>
Would there be any objection to also starting discussions with various maintainers about migrating in "headline" projects such as Spacetime UIs into the ocaml/ org? I'd suggest only doing this once the feature is in a released compiler distribution, since then the maintenance burden is established for some time.<br>
<br>
Thanks again for all the rapid and helpful responses, Amir, Sylvain and Gemma.<br>
<br>
regards,<br>
Anil<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
Infrastructure mailing list<br>
<a href="mailto:Infrastructure@lists.ocaml.org">Infrastructure@lists.ocaml.org</a><br>
<a href="http://lists.ocaml.org/listinfo/infrastructure" rel="noreferrer" target="_blank">http://lists.ocaml.org/<wbr>listinfo/infrastructure</a><br>
</div></div></blockquote></div><br></div>