On Thu, Dec 11, 2014 at 2:23 PM, VanCutsem, Geoffroy <geoffroy.vancut...@intel.com> wrote: > > >> -----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).
Ok thanks for clarification, let me add some extra idea I had In mind Since developer is allowed to submit sandboxes they should be able push "sandboxed" tags ie: sandbox/$USER/$branch/$profile branch is developper's choice (ie: devel) profile is the obs project to build (ie: tizen_common) (note we could also set arch name in the branch name) then the tag will be in submit/sandbox/$USER/$branch/$profile/YYYYMMDD.HHMMDD no need to use 99 prefixes since we know this is is a sandbox source It's assumed that RE will not be able to merge sandboxed submissions Also an obs's hook can delete the tag once project removed to keep the git clean if noone see objection I will move this to ed's wikipage Later and thank you for those efforts to get a more comfortable toolset -- mailto:philippe.co...@eurogiciel.fr -- gpg:0x467094BC xmpp:philippe.coval....@gmail.com https://dockr.eurogiciel.fr/blogs/embedded/author/pcl/ . _______________________________________________ Dev mailing list Dev@lists.tizen.org https://lists.tizen.org/listinfo/dev
