Date: Mon, 29 Aug 2016 10:49:44 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org, Rommel Escuadro <r.escuadro79@gmail.com> Subject: Re: maintainership Message-ID: <00eecf5f-7844-2a4c-3350-e2ababd30875@FreeBSD.org> In-Reply-To: <CAO-2P7GVQgVWLioX9JCXNVYmdfd1Ey6mSoMbzeuBYrWNv5Yp0A@mail.gmail.com> References: <CAO-2P7GVQgVWLioX9JCXNVYmdfd1Ey6mSoMbzeuBYrWNv5Yp0A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --p5XDok2tKwbKooejaUPXQJkQMACCP8hKn Content-Type: multipart/mixed; boundary="gbhasOXUUvbI8mvuc7Xdnv9AjgielTL4O" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org, Rommel Escuadro <r.escuadro79@gmail.com> Message-ID: <00eecf5f-7844-2a4c-3350-e2ababd30875@FreeBSD.org> Subject: Re: maintainership References: <CAO-2P7GVQgVWLioX9JCXNVYmdfd1Ey6mSoMbzeuBYrWNv5Yp0A@mail.gmail.com> In-Reply-To: <CAO-2P7GVQgVWLioX9JCXNVYmdfd1Ey6mSoMbzeuBYrWNv5Yp0A@mail.gmail.com> --gbhasOXUUvbI8mvuc7Xdnv9AjgielTL4O Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 29/08/2016 07:35, Rommel Escuadro wrote: > What is the knowledge requirement for adopting a port? The literal, by the book, answer is that you have to understand enough about standard development tools to be able to generate a diff changing the MAINTAINER line to your own e-mail address, and enough about Bugzilla that you can open a PR, attach your diff to it and request maintainership. The practical answer in many cases is that you can frequently just ask to be given maintainership on e-mail or IRC or whatever, and some committer will generally oblige. The deeper answer here is that it isn't really about knowledge: it's about commitment. You're making an undertaking to track development in an upstream project, to represent the FreeBSD user base to them, push FreeBSD related patches upstream and ultimately pull upstream's changes into the ports tree in a timely fashion. Yes, having a level of technical understanding of the port you are maintaining is important, but you by no means have to be an expert, nor do you need to be instantly capable of debugging anything that may get reported to you. You do have to be willing to investigate and help putting together a useful bug report and to perform whatever testing is necessary and to answer both upstream's and the end-users' questions. As necessary, that is. Usually once the port is written and there's been an initial round of bugfixes and patches, it's then very much plain sailing to occasionally bring in the latest changes upstream produces. Plus if you do get thrown a curve ball you can't handle, then there are a lot of extremely knowledgeable and helpful people just an e-mail away on this very list. Cheers, Matthew --gbhasOXUUvbI8mvuc7Xdnv9AjgielTL4O-- --p5XDok2tKwbKooejaUPXQJkQMACCP8hKn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJXxAVAXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT5OYP+wULJamItIbphdcPAKw2bZcR MJ3xwaGRLuTlgRWy2IV/2ChNcHDTzV4Skpc/TiTDCAuXhfKlHiRMQfXNmB8DogHp mIyxqqpEIb5O/m85eGTK2nycVi5gdzWipcn+Arqw7o3p3FB55OAXXQeLkXcoPooO UOXAFS4GoRVIpsKr+3yjFYLgMj41fr8ohJZUHC/8H8gptpzYm5I7wPrWTqxnXzwn oVkSBSLlShWVM55KGV0ro18SHJjVxn54+X6YvYQBm2Ed2Aqtm9H9KEfKZr2lw4ii u5no1uavATjcaow4O28JVO7FaAvGPjdRK7/ZAQImgoQmH+oBSehG3dz+XhSsg0VC KUKg0pxHdRkwQemlxx+RgRvB15+PAEKBBMKCX6KPZkVwqoKv7Oed22YwHWL/r0W0 7oKqfu5lLKIBGcAscXh+7N8kLKbuG7vgZW69b2oFOj1od8qs+3360k3HAsXOoxeM ekIO3oa1Xx/5kU8BzSuhpJ4ltivRniMhYMUP4HH3oyNEVL7zGxKGLwyU7kUrr9Pm WrDA5lCGcpHsHWoL6CqwuS2xcK5WjqJNiY27sdHchN7wIFhUaTmD03L3UgIeJ/K7 qSBGMSrGZfdtUXi4GiYMejH8yug+g5bZ6PhF7SZ9rictK9SykU1vX/S7e1w2709X nLvfCAuwxQpAX32R1sIW =5Ok3 -----END PGP SIGNATURE----- --p5XDok2tKwbKooejaUPXQJkQMACCP8hKn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00eecf5f-7844-2a4c-3350-e2ababd30875>