[Jenkins-infra] Request to install Slack in jenkinsci

[Kohsuke Kawaguchi]

New people doing things in a clumsy way is partly expected. They are new,
they just don't know. We OTOH are long timers, so we know better, and so we
set a higher bar for ourselves.

Yes, it would have been nicer if David initiated an email conversation. But
this isn't a tit-for-tat, we can fix it very easily by us reaching out.
He's showing some interest to interact with the Jenkins project, let's
build on that, instead of making a little thing like this an automatic
disqualifier. New contributors don't grow by themselves, we need to nurture
them.

I certainly don't think you are asking for a lot here, but I hope you
understand where I'm coming from, too.


On Thu, Sep 6, 2018 at 3:23 PM Daniel Beck <ml at beckweb.net> wrote:

>
> > On 6. Sep 2018, at 18:09, Kohsuke Kawaguchi <kk at kohsuke.org> wrote:
> >
> > The thing you should avoid, IMO, is to reject something without trying
> to understand the motivation nor providing an explanation.
>
> So what you're saying is, requesting without explanation is completely
> fine, but rejecting without explanation is not? IOW, we place any burden on
> the few org admins we have to chase down the requester and understand
> what's the request is about, rather than require that to be part of a
> request in the first place?
>
> I don't think I'm asking for a lot here. Just more than an automated email
> by GitHub.
>
> --
Kohsuke Kawaguchi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20180906/42da7a50/attachment.html>