On Sun, 12 Dec 2021 15:11:22 -0800
Chris Bennett <cpb_ports@bennettconstruction.us>:
> Hello.
>
> At least for myself, I really, really need to have following files:
>
> Dependency_trees_for_cpanfile_modules_needing_finishing (from Perl ports generator)
> ports_submitted
> ports_submitted_but_needing_a_ping
> ports_submitted_but_with_issues
> committed_ports
> committed_ports_needing_to_be_updated
>
> That may seem excessive, but I have worked several times on bringing in
> LedgerSMB. A number of years ago, I needed 2 Perl ports committed and it
> was good to go. I was even about to submit some really nice code to LedgerSMB.
>
> Last try, I submitted roughly 12 ports. Getting 2 OK's wasn't possible.
> I had about 6 more ready to submit. Committed ports from that effort was 0.
>
I do use a text file with the list of ports I sent, in the text file I can
easily keep track of each advancement. I also flag my emails for each thread
so I can easily find every thread in my emails.
Sending new ports is really hazardous, even for people with commit
rights. Reviewing a port take time because the OpenBSD project has a
high quality standard and it's preferred to correctly work on the ports
before they get included. This is sometimes discouraging, but there are
only volunteers here doing reviews on their free time and there are no
performance obligation. People review what they use or enjoy, we can't
force anyone to review something they don't like. This doesn't mean
we shouldn't send new ports, but sometimes, when we send a port, it's
either missed or the person who may have interest in it is busy and
will forget. That's why a ping can be very useful from time to time.
If you make a port, at least you can use it for yourself before it get
included, which is quite useful for keeping your system clean.
No comments:
Post a Comment