On 09/12/2024 16:49, Andreas Tille wrote:
Am Thu, Dec 05, 2024 at 08:03:36AM -0600 schrieb rhys:
It's not the sort of thing that needs to be strictly updated like a man page or other technical document. It
just needs to be a couple of pages that describe the "general" (big picture structure an workflows)
to get that established as a reference and then some of the "specifics" for at least the larger
teams who have workflows more complex than "apt info package | grep -i maintain".
Not only would it help outsiders and newbies get a feel for how things work, but it would
create visibility among the existing teams and allow them to compare and contrast their
workflows (with some mentions of "different != bad").
IMHO the most natural thing to seek for friends is looking for packages
with functionality covering a similar use case or written in the same
programming language. Than you do
apt showsrc similar_package(s) | grep ^Maintainer
and if you are lucky you have found some friends.
As an outsider trying to help, the natural thing I looked at was the RFH
process to dip my toes into things.
But only 56 packages have RFH bugs and they're usually not very clear on
what help they need. And most of those were requested >1 year ago.
No one needed help in 2024 or it was answered and closed quickly.
Perhaps encouraging overwhelmed maintainers to delegate more with RFH or
even RFH before orphaning. Maybe that could bring more people in?
And side note, there is almost a document or example for everything I
needed to get me to the RFS stage, I was pretty happy with all of it.
--
Regards,
Ahmad
