Date: Mon, 29 Aug 2016 19:05:41 +0800 From: Rommel Escuadro <r.escuadro79@gmail.com> To: Matthew Seaman <matthew@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: maintainership Message-ID: <CAO-2P7EcX=gsMqYK5CkSwwQtC=FYbsx9qs0WStK2n-X5kx2w5A@mail.gmail.com> In-Reply-To: <00eecf5f-7844-2a4c-3350-e2ababd30875@FreeBSD.org> References: <CAO-2P7GVQgVWLioX9JCXNVYmdfd1Ey6mSoMbzeuBYrWNv5Yp0A@mail.gmail.com> <00eecf5f-7844-2a4c-3350-e2ababd30875@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you for your replies. As I am using the application used so I want to make sure that it wont be having future problems. I have read the linked porters handbook but it will be more helpful for me to understand if there is an example where to start and how to go over it. I maybe asking so much but i i guess the dedication to maintain is the most important aspect. On Aug 29, 2016 5:49 PM, "Matthew Seaman" <matthew@freebsd.org> wrote: > 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 > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAO-2P7EcX=gsMqYK5CkSwwQtC=FYbsx9qs0WStK2n-X5kx2w5A>