Date: Mon, 11 Mar 2024 11:27:06 +0100 From: Moin Rahman <bofh@freebsd.org> To: Adam Labus <adam.labuznik@gmail.com> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: Contribution workflow Message-ID: <EA38341E-97A5-44F6-9C1B-96BCC313817B@freebsd.org> In-Reply-To: <CAEUYQqq09sNaxxN2sXSCLK5Ws-dXfLSSCLjKm-JPLdE5%2BX684g@mail.gmail.com> References: <CAEUYQqq09sNaxxN2sXSCLK5Ws-dXfLSSCLjKm-JPLdE5%2BX684g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_12613DF0-DF0F-4487-8FA7-D9D614E75A59 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Mar 11, 2024, at 11:18 AM, Adam Labus <adam.labuznik@gmail.com> = wrote: >=20 > Hello, >=20 > It was said to me that the main way to contribute is via bugzilla. So = last year, I wrote tickets 270798, 273569, 273568 and got no response = since. On github, repo freebsd-ports, I have pull-request 241 which I = think will have a similar fate as the bugzilla tickets. I do realize = that the github repo is supposed to be publish only, but if you look, = some pull requests are being accepted and it is better than being = ignored. > That brings up the question: > Firstly, are requests for new ports supposed to be sent via bugzilla? = Secondly, is the wait time on bugzilla normal behaviour or am I missing = some part of the contribution process here? Thirdly, how can one become = a maintainer to help clear up the waiting line of bugs, pull-requests = &c? Hi, The main point of contribution is still Bugzilla. The problem is = committers often do not go through all PRs so can miss those tickets. = There are two ways to have it priotized: 1. If you are submitting a new port with your email as the MAINTAINER = add the flag maintainer-approval to + so it automatically goes through = the filter and is shown in the maintainer approved PRs which are often = easier to handle by a committer without any problems. When I am idle I = also look through that list before moving into other lists. 2. After creating the PR send a mail in this list which attracts more = attention. Or jump into the IRC channel to ask someone to look into it. Github PRs are mostly ignored as those cannot be merged there. When you setup the MAINTAINER email to yourself you automatically become = the maintainer but that doesn't give you the skip from the queue or = waiting time. You can become a committer to avoid those queues and = commit yourself but that is a long process. As that requires certain = level of contribution and maintenance of ports. Then a committer might = approach you whether if you are interested to become a committer. But = for that you must nudge a committer so badly that they will get bored of = you and punish you with a commit bit. :D Hope that helps you answer the question. Kind regards, Moin --Apple-Mail=_12613DF0-DF0F-4487-8FA7-D9D614E75A59 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEETfdREoUGjQZKBS+fvbm1phfAvJEFAmXu3HpfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRE Rjc1MTEyODUwNjhEMDY0QTA1MkY5RkJEQjlCNUE2MTdDMEJDOTEACgkQvbm1phfA vJFisxAAhKJzMXSKJnEjqOwyLHwAFB2jkrEf6MDFpssD/TSbgP9CZTFV3ktLqXC6 RC7zb6W4tfVXD7pLyZf4b8v/Z8SNo+XkEeLXdIbzO1kVQF+sUcurKeFlBDulNcYd C/5JMQ0BPWHafNO5uYFO0w+Pp2sJzzB75s/0u2WBc8r15TDFlOEyzdyu+JbZQ2zV z9dM8UbS49bHXaNzeOi0tcKIRqPe2hJhsi9pVS9oxrllGvp/dmPqGvDN3Jy6b3bU 7s8db+GrDpouh3vHxUja7SmAWVEZX6h28kHFW+lnRHJuGr9tvx+g+mwWovu/LBiL wDmhSUt/DcTv2BxBtxdY9XNlaxFifyzpLFkT5lAef+Xmu7SP+ECIxHQDZwPT/1xP UuYH20CM14S3ZNq1rKgvzO7+Qn5a6QMyfj+QnQZN5/bbmtEmh5B0bCPU6XAKnz7i XE4Ab5ZLXM+82qG31DPW67BDPsoZS4dYKPIj9ocpZ2FXViZeoKNtb9bnTS7B8vXZ F7o/mlhuT64POCgx2lr3VNslESCGULIflj9/xQaFvzyfetSngpI9gYx+Jkptk5V8 7dgD0aVrhrN9Lvjp2NisNRBktO2JU8qKC58iRsBM9sfXGr1gpDoZb41WYLHvHmwJ mDRdq117Zdj8mj6Rti9/MFb2Ek3RJwui8TtSCdqzS9M71shCQYM= =vxyp -----END PGP SIGNATURE----- --Apple-Mail=_12613DF0-DF0F-4487-8FA7-D9D614E75A59--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EA38341E-97A5-44F6-9C1B-96BCC313817B>