[cip-dev] [RFC] isar-cip-core

[nobuhiro.iwamatsu@miraclelinux.com (Nobuhiro Iwamatsu)]

Hi, Agustin.

Non-members can not access newly created subgroups.
Previously, since cip-core was published, I think that it is a setting
problem, but how do you do?

Best regards,
  Nobuhiro

2019?1?31?(?) 17:03 Agust?n Benito Bethencourt <agustin.benito@codethink.co.uk>:
>
> Hi jan and Daniel,
>
> On Thursday, 31 January 2019 06:33:53 CET daniel.sangorrin at toshiba.co.jp wrote:
> > Hi Agustin,
> >
> > I need to create the following hierarchy on gitlab:
> >
> > > > > >>> cip-core/ <-- group
> > > > > >>>       tiny/ <-- subgroup
> > > > > >>>           deby <-- git repo (current cip-core.git)
> > > > > >>>       generic/ <-- subgroup
> > > > > >>>           isar <-- git repo
>
> I just created the new subgroup called "cip-core". I moved the project cip-core from the root tree to the new subgroup. I gave both of you owner rights in this new subgroup so you can configure it as you please. Please take a few minutes to go over the configurations so you guys can decide merge request, merge, tickets... strategies. I will be traveling the coming days but feel free to ask me through mail or IRC if you want a second opinion on how to set up the subgroup/projects. I have done it several times with a variety of use cases over the years.
>
> We defined a policy in which each Member company has a person as Owner of the whole CIP Group. If you think there should be two people per company to make things more fluid, please propose it. I would be fine with it. I understand sometimes it is not ideal to depend on somebody else for these things.
>
> I think it would be useful to agree on basic topics across the different subgroups like some common labels, milestones. boards... so we start to apply some consistency across the different groups on very basic thinks. If you think it might be a good idea I can make a proposal in the coming days.
>
> Best Regards
>
>
> --
> Agust?n Benito Bethencourt
> Principal Consultant
> Codethink Ltd
> We respect your privacy.   See https://www.codethink.co.uk/privacy.html
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev