* maintainer for imx53qsb @ 2014-03-07 17:11 Daiane.Angolini 2014-03-07 17:30 ` Otavio Salvador 2014-03-11 12:35 ` Trevor Woerner 0 siblings, 2 replies; 6+ messages in thread From: Daiane.Angolini @ 2014-03-07 17:11 UTC (permalink / raw) To: meta-freescale@yoctoproject.org I took a look in current maintainers of meta-fsl-arm layer and noticed that imx53qsb is still orphan. I am willing to adopt this board if no one else is interested to do so as I already maintain some other boards. So, please, let me know if you want to adopt this board. Daiane ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: maintainer for imx53qsb 2014-03-07 17:11 maintainer for imx53qsb Daiane.Angolini @ 2014-03-07 17:30 ` Otavio Salvador 2014-03-07 19:50 ` Daiane.Angolini 2014-03-11 12:35 ` Trevor Woerner 1 sibling, 1 reply; 6+ messages in thread From: Otavio Salvador @ 2014-03-07 17:30 UTC (permalink / raw) To: Daiane.Angolini@freescale.com, Lauren Post Cc: meta-freescale@yoctoproject.org Hello Daiane, On Fri, Mar 7, 2014 at 2:11 PM, Daiane.Angolini@freescale.com <Daiane.Angolini@freescale.com> wrote: > I took a look in current maintainers of meta-fsl-arm layer and noticed that imx53qsb is still orphan. > I am willing to adopt this board if no one else is interested to do so as I already maintain some other boards. > > So, please, let me know if you want to adopt this board. Good catch Daiane, it would indeed be good to have someone maintaining it. We also have some other important boards which are orphan, mainly imx6dlsabreauto, imx6solosabreauto which were added by Lauren in 3.10.9-1.0.0-alpha release. Could you adopt those as well? -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: maintainer for imx53qsb 2014-03-07 17:30 ` Otavio Salvador @ 2014-03-07 19:50 ` Daiane.Angolini 0 siblings, 0 replies; 6+ messages in thread From: Daiane.Angolini @ 2014-03-07 19:50 UTC (permalink / raw) To: Otavio Salvador, Lauren Post; +Cc: meta-freescale@yoctoproject.org > -----Original Message----- > From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On > Behalf Of Otavio Salvador > Sent: Friday, March 07, 2014 2:31 PM > To: Angolini Daiane-B19406; Post Lauren-RAA013 > Cc: meta-freescale@yoctoproject.org > Subject: Re: [meta-freescale] maintainer for imx53qsb > > Hello Daiane, > > On Fri, Mar 7, 2014 at 2:11 PM, Daiane.Angolini@freescale.com > <Daiane.Angolini@freescale.com> wrote: > > I took a look in current maintainers of meta-fsl-arm layer and noticed > that imx53qsb is still orphan. > > I am willing to adopt this board if no one else is interested to do so as > I already maintain some other boards. > > > > So, please, let me know if you want to adopt this board. > > Good catch Daiane, it would indeed be good to have someone maintaining it. > > We also have some other important boards which are orphan, mainly > imx6dlsabreauto, imx6solosabreauto which were added by Lauren in 3.10.9- > 1.0.0-alpha release. > > Could you adopt those as well? I wish I could! I don´t have the hardware, so I cannot test anything on those boards. Daiane > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.br http://code.ossystems.com.br > Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: maintainer for imx53qsb 2014-03-07 17:11 maintainer for imx53qsb Daiane.Angolini 2014-03-07 17:30 ` Otavio Salvador @ 2014-03-11 12:35 ` Trevor Woerner 2014-03-11 14:09 ` Daiane.Angolini 1 sibling, 1 reply; 6+ messages in thread From: Trevor Woerner @ 2014-03-11 12:35 UTC (permalink / raw) To: Daiane.Angolini@freescale.com, meta-freescale@yoctoproject.org Hi, Are there any published maintainer procedures/responsibilities? I realize it might be best to not be too stringent on these requirements, but on the other hand it seems as though maintainers are free to define whatever they feel is enough, which might be "nothing" ;-) More seriously, a maintainer could decide booting core-image-minimal and seeing a login prompt is enough. This would be setting the bar quite low. Maybe for each board a matrix could be maintained whereby the maintainer is free to do as few or as many things from the list of potential items? At the very least, we'd have a better definition of what "maintained" would mean for each board. Even better: if instructions were available describing how to build and test each line item, then everyone could benefit! Best regards, Trevor ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: maintainer for imx53qsb 2014-03-11 12:35 ` Trevor Woerner @ 2014-03-11 14:09 ` Daiane.Angolini 2014-03-13 13:33 ` Otavio Salvador 0 siblings, 1 reply; 6+ messages in thread From: Daiane.Angolini @ 2014-03-11 14:09 UTC (permalink / raw) To: Trevor Woerner, meta-freescale@yoctoproject.org > -----Original Message----- > From: Trevor Woerner [mailto:trevor.woerner@linaro.org] > Sent: Tuesday, March 11, 2014 9:36 AM > To: Angolini Daiane-B19406; meta-freescale@yoctoproject.org > Subject: Re: [meta-freescale] maintainer for imx53qsb > > Hi, > > Are there any published maintainer procedures/responsibilities? I´m happy you have questioned that! > > I realize it might be best to not be too stringent on these requirements, > but on the other hand it seems as though maintainers are free to define > whatever they feel is enough, which might be "nothing" ;-) > > More seriously, a maintainer could decide booting core-image-minimal and > seeing a login prompt is enough. This would be setting the bar quite low. The maintainer is the person that will have the Minerva/casting vote when we face a deadlock. S/he is responsible to keep the things working. For those boards in meta-fsl-arm-extra, it´s much more easy to understand, because maintainer is the one who keeps kernel updated, u-boot tested/working. For meta-fsl-arm boards it´s lightly different, as 'who' keeps kernel updated is Freescale. It´s not a matter of "what is supported", because anyone can add support for anything. But a matter of keeping the gears spinning. > > Maybe for each board a matrix could be maintained whereby the maintainer is > free to do as few or as many things from the list of potential items? > At the very least, we'd have a better definition of what "maintained" > would mean for each board. Even better: if instructions were available > describing how to build and test each line item, then everyone could > benefit! In addition, we want maintainers help for some "maintainer work" we face in our day-by-day, as example: Keep release notes updated Keep test cycle updated Keep the most usual images building and booting You can see here [1] the goals we had in last release (1.6). It´s supposed that *at least* the maintainer have tested all those items for her/him board. When a build error is faced, the maintainer will "fix" it. For those guys with kernel control (meta-fsl-arm-extra) is expected that they properly fix the kernel issue (when it´s a kernel issue). But anything out of our control should be work-rounded anyway. [1] http://freescale.github.io/doc/release-notes/1.5/index.html#goals Otavio, did I miss anything? Daiane > > Best regards, > Trevor > ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: maintainer for imx53qsb 2014-03-11 14:09 ` Daiane.Angolini @ 2014-03-13 13:33 ` Otavio Salvador 0 siblings, 0 replies; 6+ messages in thread From: Otavio Salvador @ 2014-03-13 13:33 UTC (permalink / raw) To: Daiane.Angolini@freescale.com; +Cc: meta-freescale@yoctoproject.org On Tue, Mar 11, 2014 at 11:09 AM, Daiane.Angolini@freescale.com <Daiane.Angolini@freescale.com> wrote: >> -----Original Message----- >> From: Trevor Woerner [mailto:trevor.woerner@linaro.org] >> Sent: Tuesday, March 11, 2014 9:36 AM >> To: Angolini Daiane-B19406; meta-freescale@yoctoproject.org >> Subject: Re: [meta-freescale] maintainer for imx53qsb >> >> Hi, >> >> Are there any published maintainer procedures/responsibilities? > > I´m happy you have questioned that! > >> >> I realize it might be best to not be too stringent on these requirements, >> but on the other hand it seems as though maintainers are free to define >> whatever they feel is enough, which might be "nothing" ;-) >> >> More seriously, a maintainer could decide booting core-image-minimal and >> seeing a login prompt is enough. This would be setting the bar quite low. > > The maintainer is the person that will have the Minerva/casting vote when we face a deadlock. > > S/he is responsible to keep the things working. For those boards in meta-fsl-arm-extra, it´s > much more easy to understand, because maintainer is the one who keeps kernel updated, u-boot tested/working. > > For meta-fsl-arm boards it´s lightly different, as 'who' keeps kernel updated is Freescale. > > It´s not a matter of "what is supported", because anyone can add support for anything. But a matter of > keeping the gears spinning. > > >> >> Maybe for each board a matrix could be maintained whereby the maintainer is >> free to do as few or as many things from the list of potential items? >> At the very least, we'd have a better definition of what "maintained" >> would mean for each board. Even better: if instructions were available >> describing how to build and test each line item, then everyone could >> benefit! > > In addition, we want maintainers help for some "maintainer work" we face in our day-by-day, as example: > Keep release notes updated > Keep test cycle updated > Keep the most usual images building and booting > > You can see here [1] the goals we had in last release (1.6). It´s supposed that *at least* the maintainer > have tested all those items for her/him board. > > When a build error is faced, the maintainer will "fix" it. For those guys with kernel control (meta-fsl-arm-extra) > is expected that they properly fix the kernel issue (when it´s a kernel issue). But anything out of our control > should be work-rounded anyway. > > > [1] http://freescale.github.io/doc/release-notes/1.5/index.html#goals > > > Otavio, did I miss anything? No; I think this is a good summary of the duties involved in being a board maintainer. Trevor, are you up for the task? -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-03-13 13:33 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-03-07 17:11 maintainer for imx53qsb Daiane.Angolini 2014-03-07 17:30 ` Otavio Salvador 2014-03-07 19:50 ` Daiane.Angolini 2014-03-11 12:35 ` Trevor Woerner 2014-03-11 14:09 ` Daiane.Angolini 2014-03-13 13:33 ` Otavio Salvador
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.