Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance

[<Tim.Bird@sony.com>]

> -----Original Message-----
> From: James Bottomley
> 
> On Tue, 2018-09-18 at 10:00 +0200, Daniel Vetter wrote:
> > On Tue, Sep 18, 2018 at 1:04 AM, James Bottomley
> > <James.Bottomley@hansenpartnership.com> wrote:
> > > On September 17, 2018 4:39:48 PM MST, Dave Airlie <airlied@gmail.co
> > > m> wrote:
> > > > > This is a valid point: whatever development process is used,
> > > > > drive-by contributors should be allowed to send e-mails without
> > > > > needing to
> > > >
> > > > subscribe
> > > > > (neither to a moderated list nor to a web-UI). I don't care how
> > > > > the maintainer will handle such patches, provided that they
> > > > > will be
> > > >
> > > > properly handled.
> > > > >
> > > >
> > > > It really depends on what type of one-off contributor they are.
> > > >
> > > > Setting up git send-email isn't trivial for everyone, if you are
> > > > a gmail user and work for a company that doesn't embrace smtp so
> > > > much, then having a webui and https git access will be a lot
> > > > easier for one-off contributions.
> > >
> > > Agree with this but that's why I don't use git-send-email
> > >
> > > > Beware of thinking our setup with email is in any way simple for
> > > > a newcomer to setup properly.
> > >
> > > Right, but there are many other ways of doing this which still work
> > > with mailing lists.
> >
> > Aside from bare diffs stuffed into plaintext mails directly (which I
> > is a lot harder to set up than git send-email for new people),
> 
> Well, that is how I do it: git format-patch followed by preformatted
> text insertion in evolution.  I've got to say I don't find it at all
> hard, but I do understand if you use outlook or gmail it can be a pain.
> 
> >  what else is there that works with mailing lists? I'd be great if we
> > have other options here, since it is a fairly annoying problem for
> > us.
> 
> This is more about mail tools than actual lists, isn't it?  In which
> case I find the Documentation/email-clients.txt and invaluable resource
>  to point people to (wait, where is it now, ah:
> Documentation/process/email-clients.rst)

Well, it's more than just the mail tool - it's the entire enterprise e-mail
infrastructure where problems can crop up.  Sony's IT department recently
installed a system to help prevent phishing attacks which re-writes all the URLs in
every e-mail that goes through the system.  This is patch-unfriendly, to say the least.
I'm working with IT to try to get myself exempted from this "service",
but it affects every Sony employee who wishes to use corporate
e-mail to collaborate with upstream.  Unfortunately, this type of
thing is fairly common.

For my part, I wish there were a gateway I could send through, that would
undo all the mumbo-jumbo that exchange and the like introduce (text re-flowing,
uuencoding, url-rewriting, etc.)

Mainstream e-mail infrastructure implementations are increasingly averse to just
delivering raw text from one point to another, so the fundamental assumption
that e-mail is a reliable text delivery service is increasingly unfounded.
 -- Tim