References: <1484297432-14435-1-git-send-email-chipitsine@...277...> <7dc75a19-451e-effa-503a-ac5b75a23bab@...515...> <6256c846-ca60-be4f-7122-60465374a322@...515...> From: David Sommerseth Message-ID: <7e7799f0-e2f1-8773-18aa-6a89b87d3500@...2080...> Date: Tue, 31 Jan 2017 14:49:15 +0100 MIME-Version: 1.0 In-Reply-To: <6256c846-ca60-be4f-7122-60465374a322@...515...> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OOnCxbdtDMCnboCqxGkrhenl2BP0RTgL3" Subject: Re: [Openvpn-devel] [PATCH] add PR template in order to simplify new developers cooperate properly if they open PR. discussed here: https://sourceforge.net/p/openvpn/mailman/message/35601310/ Reply-To: openvpn-devel@lists.sourceforge.net List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Samuli_Sepp=c3=a4nen?= , =?UTF-8?B?0JjQu9GM0Y8g0KjQuNC/0LjRhtC40L0=?= , "openvpn-devel@lists.sourceforge.net" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OOnCxbdtDMCnboCqxGkrhenl2BP0RTgL3 Content-Type: multipart/mixed; boundary="rH0xdLcwChXR7rWss0Iv4MXHFO56Tv1sf"; protected-headers="v1" From: David Sommerseth Reply-To: openvpn-devel@lists.sourceforge.net To: =?UTF-8?Q?Samuli_Sepp=c3=a4nen?= , =?UTF-8?B?0JjQu9GM0Y8g0KjQuNC/0LjRhtC40L0=?= , "openvpn-devel@lists.sourceforge.net" Message-ID: <7e7799f0-e2f1-8773-18aa-6a89b87d3500@...2080...> Subject: Re: [Openvpn-devel] [PATCH] add PR template in order to simplify new developers cooperate properly if they open PR. discussed here: https://sourceforge.net/p/openvpn/mailman/message/35601310/ References: <1484297432-14435-1-git-send-email-chipitsine@...277...> <7dc75a19-451e-effa-503a-ac5b75a23bab@...515...> <6256c846-ca60-be4f-7122-60465374a322@...515...> In-Reply-To: <6256c846-ca60-be4f-7122-60465374a322@...515...> --rH0xdLcwChXR7rWss0Iv4MXHFO56Tv1sf Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 30/01/17 13:34, Samuli Sepp=C3=A4nen wrote: > I agree with you on keeping the pull request template minimal and having= =20 > the more fine-grained information in Trac. >=20 > ACK. Don't get me wrong! I agree we should keep the template minimal. But I yet have to see a developer full of enthusiasm with a fix ready, who just clicked "Send pull request!" who will actually instantly go reading further. And especially when the information need is fairly comprehensive and not even directly in the first URL being listed. In fact the first place where the patch process is described is here: . That is "hidden" in the middle of the wiki on the second URL. And the first URL provides just a link to the same DeveloperDocumentation wiki page. So I kindly ask you to reconsider the text more carefully once more. --rH0xdLcwChXR7rWss0Iv4MXHFO56Tv1sf-- --OOnCxbdtDMCnboCqxGkrhenl2BP0RTgL3--