On 2/10/21 12:54 PM, Patrice Dumas wrote:
I understand well the makeinfo Perl code, and I can help on checking the
code. But I do not have much time overall for texinfo these days. I do
not really know what co-mentoring would entail besides what I already do
for texi2any.
Basically, it is to provide help and guidance for a student working
on a given project. That could include setting expectations and goals,
help the student with creating a roadmap, evaluate their progress, and do on.
We create a project suggestion (now), and if a student is interested,
they submit a proposal to work on the project. (The student can submit
unrelated proposals, but usually don't, but we're free to summarily reject
anything we don't think os a good idea, or a proposal that indicates
they don't get it. Usually there is some back-and-forth with the
student helping them with their proposal and helping them understand
what is involved, before the formal submittal and possible acceptance
of the proposal.)
The amount of work for the mentors depends on both the student and the project.
When Gavin co-mentored Mathieu Lirzin a few years ago, he did find it took more
time than expected - and that was with an above-average student - but I
think he'll agree it was a valuable contribution. Getting a long-term
contributor/member of the community is unlikely, unless the student
is already involved with GNU and/or texinfo: They're busy with studies
and/or starting a job, and many are mostly motivated by the money and/or
resume-building. But at the least we can get a useful contribution
out of it (assuming the student is reasonably motivated and capable),
and sometimes they come back later.
--
--Per Bothner
p...@bothner.com http://per.bothner.com/
