On Thursday, March 9, 2017 2:59:33 PM CET Nikos Mavrogiannopoulos wrote: > On Thu, Mar 9, 2017 at 2:38 PM, Tim Ruehsen <tim.rueh...@gmx.de> wrote: > >> Hi, > >> > >> I've created the libidn group in gitlab.com in order to host the > >> > >> images used for the CI [0]. Does it make sense to move the source > >> code there as well, to avoid having the code in private repositories? > >> (in that case I'll leave the group and stay only in the build-images > >> repo). > > > > *scratch* Not sure if I get it :-) > > > > libidn2 sources -> libidn group ? (I don't mind, it is Simon's project) > > CI image sources -> libidn group ? I am absolutely not into that, but > > sounds good. > > We currently have: > https://gitlab.com/libidn/build-images (images) > https://gitlab.com/jas/libidn2 (source) > > and I propose to do: > https://gitlab.com/libidn/build-images (images) > https://gitlab.com/libidn/libidn2 (source) > > so the both the images and source are under the 'libidn' group. > > To complete that, while preserving history it would require to move > the jas/libidn2 repo to libidn/libidn2. An alternative is to create a > copy under libidn, but this will not have the issues/merge requests of > the original.
Consolidation is good. Also equally puts the responsibility for the project on several shoulders. That might also be in the interest of Simon. Regards, Tim
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Help-libidn mailing list Help-libidn@gnu.org https://lists.gnu.org/mailman/listinfo/help-libidn
