[OE-core] Why openembedded-core mailing list is now author of some patches?

[Neal Gompa]

On Sat, Mar 23, 2019 at 6:25 AM <richard.purdie at linuxfoundation.org> wrote:
>
> On Fri, 2019-03-22 at 16:26 -0700, Taras Kondratiuk wrote:
> > Quoting Burton, Ross (2018-10-12 07:04:38)
> > > On Fri, 12 Oct 2018 at 15:03, Ruslan Bilovol <rbilovol at cisco.com>
> > > wrote:
> > > > > This is basically due to SPF, and people sending email from
> > > > > non-authoritive hosts.  Concrete example: Richard Purdie's mail
> > > > > comes
> > > > > from a machine which the linuxfoundation.org SPF records
> > > > > doesn't
> > > > > recognise as an authorised sender.
> > > >
> > > > Hmm.. I've just sent an email from rbilovol at cisco.com to another
> > > > Gmail
> > > > address, and Gmail says SPF checks passed:
> > > >   SPF:  PASS with IP 173.38.203.51
> > > >   DKIM: 'PASS' with domain cisco.com
> > > >   DMARC:        'PASS'
> > > >
> > > > Does it mean oe-core mailing list's software is incorrectly
> > > > configured,
> > > > or there is something else missing on @cisco.com side?
> > >
> > > CCing yet more people, specifically Michael Halstead who admins the
> > > machines and actually knows what he is talking about (unlike me).
> >
> > The issue seems to be still there. It doesn't seem to be cisco.com
> > specific. I see actia.fr and globallogic.com too:
> > https://patchwork.openembedded.org/patch/159446/
> > https://patchwork.openembedded.org/patch/157540/
>
> The cause is the same though, the senders are sending from addresses
> which the SPF records at those domains say shouldn't be sending emails.
>
> I'm trying to catch these and fix them up in before committing them. I
> thought I had local hooks which would not allow them, clearly the hooks
> need more work as things are getting through those filters.
>
> We are looking at a different email list hosting solution which may
> help. Adding "From:" lines directly in the patches where the domains
> are problematic would also help. We could also in theory teach mailman
> how to do that for patches but its a question of people/time/resources.
>

Has anyone considered the (perhaps radical?) idea that the sending
changes as an email patch series should be replaced? For example, if
git.openembedded.org and git.yoctoproject.org were overlaid with
Pagure[0] frontends (it uses Gitolite internally, so you can have
multiple frontends in place for the same Git repos), it would be easy
enough to support pull requests, even from external Git servers. And
with that model, OE/Yocto can use CI properly (e.g. using Jenkins,
Zuul, or something else) rather than building more hacks on top of
emails.

Email is getting harder and harder to deal with for handling
contributions, and it's only more difficult as mail servers extend and
mutate emails as they work to try to combat all kinds of other
problems with email these days.

[0]: https://pagure.io/pagure


--
真実はいつも一つ！/ Always, there's only one truth!