Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 78373200C68 for ; Wed, 3 May 2017 11:18:56 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 76CAC160BB5; Wed, 3 May 2017 09:18:56 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B491F160BAA for ; Wed, 3 May 2017 11:18:55 +0200 (CEST) Received: (qmail 27251 invoked by uid 500); 3 May 2017 09:18:55 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 27240 invoked by uid 99); 3 May 2017 09:18:54 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 May 2017 09:18:54 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 93168DF9FD; Wed, 3 May 2017 09:18:54 +0000 (UTC) From: tbouron To: dev@brooklyn.apache.org Reply-To: dev@brooklyn.apache.org References: In-Reply-To: Subject: [GitHub] brooklyn-server issue #664: Add contributing guidelines and PR template Content-Type: text/plain Message-Id: <20170503091854.93168DF9FD@git1-us-west.apache.org> Date: Wed, 3 May 2017 09:18:54 +0000 (UTC) archived-at: Wed, 03 May 2017 09:18:56 -0000 Github user tbouron commented on the issue: https://github.com/apache/brooklyn-server/pull/664 > This particular template is onerous and patronising Patronising, seriously? I'm speechless here. FYI @ahgittin a `CONTRIBUTING.md` can be useful because [GitHub treats it a bit differently](https://github.com/blog/1184-contributing-guidelines) Anyway, anybody else against this? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---