> -----Original Message----- > From: Philippe Coval [mailto:philippe.co...@open.eurogiciel.org] > Sent: Thursday, December 11, 2014 2:15 PM > To: VanCutsem, Geoffroy > Cc: Bartosh, Eduard; jongwoo.c...@samsung.com; dev@lists.tizen.org; > Lehtonen, Markus; joon-sub....@samsung.com; k...@linux.intel.com; > Stephane Desneux > Subject: Re: [Dev] Enhancing development workflow > > On Thu, Dec 11, 2014 at 1:49 PM, VanCutsem, Geoffroy > <geoffroy.vancut...@intel.com> wrote: > > Hi folks, > > > > Does one need to be listed as a (M)aintainer, (A)rchitect, (I)ntegrator > and/or (R)eviewer in order to be able to run 'gbs submit'? > > > > I haven't tried lately but I seem to recall that 'standard' contributors > > (like > me) who do not have any special role cannot follow this procedure, is this > correct? > > I guess if you have +2 rights you should be able to submit this does not tell > me the difference between Integrator and Maintainer
I don't have +2 rights for most packages. > > You need to belong to one Domain then , > do you want to take care of Graphics ? > I can lead you and help to document the workflow My question was not triggered by a desire to get increased privileges (although I always try to help if/where I can) but I was more looking at the whole discussion from the point of view of an external 'unprivileged' contributors and my conclusion was that the workflow described does not apply to them. My understanding at the moment is that the only way an external contributor can verify a patch is by doing a local 'gbs build' on his dev environment. While it's fine in principle, there is an increased overhead as more architectures are added (and this is where OBS could be helpful, in that you throw it at OBS and it will very quickly tell you which target arch it fails to build for). Cheers, Geoffroy _______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
