[meta-chip] Jenkins, reviews and mailing list

[meta-chip] Jenkins, reviews and mailing list

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

Hello all,

We've been testing a setup with meta-raspberrypi which seems to work fine:
PR to github integrated with a jenkins server and use mailing list for
discussions. I recommend people pushing their patches to the mailing list
too even if they send pull requests so people who don't use github that
much can have a chance to be informed on what is changing. We've been
dragging this setup for a couple of months (I think) now and it looks great
especially easing the work of the maintainer.

I propose to copy the same setup to meta-chip too. We will be using the
same server for jenkins (https://yocto-ci.resin.io/) and the github
repository https://github.com/agherzan/meta-chip .  Yes, I am aware of
multiple forks of the same repository but given that this repository saw
some activity lately I will consolidate the work hoping that the other
repositories will contribute back to it.

Any comments?

Regards,
Andrei

[-- Attachment #2: Type: text/html, Size: 1197 bytes --]

Re: [meta-chip] Jenkins, reviews and mailing list

[Trevor Woerner]

On Mon, Jun 26, 2017 at 9:21 AM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> We've been testing a setup with meta-raspberrypi which seems to work fine:
> PR to github integrated with a jenkins server and use mailing list for
> discussions.
>
> I propose to copy the same setup to meta-chip too.

That's all fine. As the maintainer (thank you!) you're welcome to use
whatever workflow with which you're the happiest... as long as you
update the "Contributing" section of the README :-)

Re: [meta-chip] Jenkins, reviews and mailing list

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 648 bytes --]

On Mon, Jun 26, 2017 at 2:29 PM, Trevor Woerner <twoerner@gmail.com> wrote:

> On Mon, Jun 26, 2017 at 9:21 AM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> > We've been testing a setup with meta-raspberrypi which seems to work
> fine:
> > PR to github integrated with a jenkins server and use mailing list for
> > discussions.
> >
> > I propose to copy the same setup to meta-chip too.
>
> That's all fine. As the maintainer (thank you!) you're welcome to use
> whatever workflow with which you're the happiest... as long as you
> update the "Contributing" section of the README :-)
>

Sure. That makes sense.

--
Andrei Gherzan

[-- Attachment #2: Type: text/html, Size: 1184 bytes --]

Re: [meta-chip] Jenkins, reviews and mailing list

[Petter Mabacker]

[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]

On Mon, 2017-06-26 at 17:12 +0100, Andrei Gherzan wrote:
> On Mon, Jun 26, 2017 at 2:29 PM, Trevor Woerner <twoerner@gmail.com>
> wrote:
> > On Mon, Jun 26, 2017 at 9:21 AM, Andrei Gherzan <andrei@gherzan.ro>
> > wrote:
> > 
> > > We've been testing a setup with meta-raspberrypi which seems to
> > work fine:
> > 
> > > PR to github integrated with a jenkins server and use mailing
> > list for
> > 
> > > discussions.
> > 
> > >
> > 
> > > I propose to copy the same setup to meta-chip too.
> > 
> > 
> > 
> > That's all fine. As the maintainer (thank you!) you're welcome to
> > use
> > 
> > whatever workflow with which you're the happiest... as long as you
> > 
> > update the "Contributing" section of the README :-)
> > 
> 
> Sure. That makes sense.

Hi Andrei,
I fully agree with Trevor, just update the README and lets rock! :) But
like you say I also believe it's good if people can take the time to
also send the patches to mailing list, so we don't risk losing those
valuable discussions that often is initated through the mailing list
(since more people will track the changes that way). My opinion is that
this have work good for meta-raspberrypi, so cannot see any reasons why
it should work great for meta-chip as well.
Let us know when jenkins is up-and-running!
Cheers Petter
> --Andrei Gherzan
> 

[-- Attachment #2: Type: text/html, Size: 2264 bytes --]

Re: [meta-chip] Jenkins, reviews and mailing list

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]

On Tue, Jun 27, 2017 at 5:18 AM, Petter Mabacker <petter@technux.se> wrote:

> On Mon, 2017-06-26 at 17:12 +0100, Andrei Gherzan wrote:
>
> On Mon, Jun 26, 2017 at 2:29 PM, Trevor Woerner <twoerner@gmail.com>
> wrote:
>
> On Mon, Jun 26, 2017 at 9:21 AM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> > We've been testing a setup with meta-raspberrypi which seems to work
> fine:
> > PR to github integrated with a jenkins server and use mailing list for
> > discussions.
> >
> > I propose to copy the same setup to meta-chip too.
>
> That's all fine. As the maintainer (thank you!) you're welcome to use
> whatever workflow with which you're the happiest... as long as you
> update the "Contributing" section of the README :-)
>
>
> Sure. That makes sense.
>
>
> Hi Andrei,
>
> I fully agree with Trevor, just update the README and lets rock! :) But
> like you say I also believe it's good if people can take the time to also
> send the patches to mailing list, so we don't risk losing those valuable
> discussions that often is initated through the mailing list (since more
> people will track the changes that way). My opinion is that this have work
> good for meta-raspberrypi, so cannot see any reasons why it should work
> great for meta-chip as well.
>
> Let us know when jenkins is up-and-running!
>

All is up and running. README updated too
https://github.com/agherzan/meta-chip/pull/13 .

Cheers,
Andrei

[-- Attachment #2: Type: text/html, Size: 2655 bytes --]