[Toaster] submission procedures and status update

[Alexander Kanevskiy]

On Thu, May 7, 2015 at 5:00 PM, Barros Pena, Belen <
belen.barros.pena at intel.com> wrote:


> >Now, about how submission tracking can be more automatic:
> >
> >
> >- every one has ability to fork your project easily (1 click). This
> >simplifies life of developers how to prepare set of patches to be sent.
>
> What would be the "project"? Toaster is part of the poky repo, and
> contributors normally develop on top of the poky master branch (Alex,
> please correct me if I am wrong). We don't really keep a toaster/master
> branch.
>
>
well, here there are couple of scenarios that I can think of:
1. start mirroring poky to github similarly like
https://github.com/openembedded/ mirrored.
 That way everyone can have their own "contrib" area where they can develop
set of patches before submitted to poky ML or upload to yp.org git as
currently.
2. separate toaster development into separate git tree, like bitbake is
separated from poky. And thus have it merged into poky via combo-layer
tool, as other pieces are merged.

maybe community might come up with some other scenarios :)




> >- each series of patches can be organised as pull request to main
> >repository.
>
> How would this impact our current development workflow? Right now we have
> a 2-step submission process where Alex is the upstream submission
> gatekeeper (he collects contributors' patches from the Toaster mailing
> list twice a week, makes sure nothing breaks and then sends them as a
> patch series to the bitbake mailing list).
>
>
 As noted above, for me having toaster on par with bitbake (separate repo,
merged to poky via combo-layer) sounds like the best approach.

However, first variant above, where toaster developed in copy of poky on
github+pull requests also might be a solution.
It would still require manual step of extracting set of patches from github
repo and sending it to bitbake or yocto mailing list and then tracking
status of them in mail client.

Of course it might be also option to open pull requests towards
https://github.com/openembedded/bitbake and ask folks to merge from where :)



-- 
br, Alexander Kanevskiy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20150507/3f5e178f/attachment.html>