All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel.sangorrin@toshiba.co.jp (daniel.sangorrin at toshiba.co.jp)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [RFC] isar-cip-core
Date: Mon, 4 Feb 2019 09:25:21 +0000	[thread overview]
Message-ID: <OSAPR01MB37634A0812B8143C747A8B0FD06D0@OSAPR01MB3763.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAGDrK-a_UEaud04E7RwHJSxLy5-Fkc8npWdnRMgf6yBVaHw7iQ@mail.gmail.com>

Thanks Iwamatsu-san.
Jan: when you move your isar repo to cip-core please add two subgroups for tiny and generic if you want. Otherwise, we can have them on the same level and just mention on the wiki that each belongs to a different profile.

Thanks,
Daniel

> -----Original Message-----
> From: Nobuhiro Iwamatsu <nobuhiro.iwamatsu@miraclelinux.com>
> Sent: Monday, February 4, 2019 6:09 PM
> To: sangorrin daniel(????? ???? ????????) <daniel.sangorrin@toshiba.co.jp>
> Cc: agustin.benito at codethink.co.uk; jan.kiszka at siemens.com; cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] [RFC] isar-cip-core
> 
> Hi, Daniel.
> 
> I have confirmed that the cip-core group is displayed and I can show
> to the repository without login.
> Thanks for your work.
> 
> Best regards,
>   Nobuhiro
> 
> 2019?2?4?(?) 14:37 <daniel.sangorrin@toshiba.co.jp>:
> >
> > Iwamatsu-san,
> >
> > I have fixed the permissions. Could you try again and see if it works now?
> >
> > Thanks,
> > Daniel
> >
> > > -----Original Message-----
> > > From: Agustin Benito Bethencourt <agustin.benito@codethink.co.uk>
> > > Sent: Friday, February 1, 2019 5:36 PM
> > > To: Nobuhiro Iwamatsu <nobuhiro.iwamatsu@miraclelinux.com>
> > > Cc: sangorrin daniel(????? ???? ????????) <daniel.sangorrin@toshiba.co.jp>;
> > > jan.kiszka at siemens.com; cip-dev at lists.cip-project.org
> > > Subject: Re: [cip-dev] [RFC] isar-cip-core
> > >
> > > Hi,
> > >
> > > On 1 February 2019 02:35:51 CET, Nobuhiro Iwamatsu <nobuhiro.iwamatsu@miraclelinux.com> wrote:
> > > >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?
> > >
> > > the  new subgroup has inherited every group member. If you cannot access the new subgroup is because
> you
> > > were member of a different subgroup, not the top group.
> > >
> > > I am traveling and will not have access the next few hours (I rather do this on a laptop).
> > >
> > > Yo can be added by the new owners.
> > >
> > > @Daniel, @Jan there is a config option in the subgroup to allow people to request access.
> > >
> > > Best Regards
> > >
> > > >
> > > >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
> > >
> > > --
> > > Sent from my Android device with K-9 Mail. Please excuse my brevity.

      reply	other threads:[~2019-02-04  9:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 18:03 [cip-dev] [RFC] isar-cip-core Jan Kiszka
2019-01-04 16:50 ` Jan Kiszka
2019-01-07  0:30 ` Daniel Sangorrin
2019-01-07  5:40   ` Jan Kiszka
2019-01-07  6:45     ` Daniel Sangorrin
2019-01-07  6:59       ` Jan Kiszka
2019-01-07  7:31         ` Daniel Sangorrin
2019-01-31  5:33           ` daniel.sangorrin at toshiba.co.jp
2019-01-31  8:01             ` Agustín Benito Bethencourt
2019-01-31  8:52               ` daniel.sangorrin at toshiba.co.jp
2019-02-01  1:35               ` Nobuhiro Iwamatsu
2019-02-01  8:35                 ` Agustin Benito Bethencourt
2019-02-04  5:36                   ` daniel.sangorrin at toshiba.co.jp
2019-02-04  9:09                     ` Nobuhiro Iwamatsu
2019-02-04  9:25                       ` daniel.sangorrin at toshiba.co.jp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OSAPR01MB37634A0812B8143C747A8B0FD06D0@OSAPR01MB3763.jpnprd01.prod.outlook.com \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.