Thank you for your long answer.
"1- Make yourself available, but you don't need to know everything"
Well, I pointed out that I don't have even the possibility to make myself
more than *a little bit* available. So there's no danger I will become the
only "free software maintainer" for this person.
And yes, I want to make use of other resources available, that's what the
whole topic is about.
"2- This person is a scholar, used to academic work and lectures. Don't
underestimate or judge their ability to process HUGE amounts of
information. Be clear: "**In my opinion** there is a lot of information,
here is a starting point [URL to free-sw.html]. Take a look and let me
know what you think"- then STOP - let people discover, open the door and
remain available for further questions"
The information on gnu.org isn't really too much, but it uses to much
technical expressions, such as "source code" or "binary blobs" and there is
too much information on side topics like tivoization, which isn't necessary
to know for a total beginner.
You have to bear in mind: this kind of persons have only a vague idea of what
a program is.
They only know: I'm clicking here, and this and that happens.
You have to explain to them: a program can do more things like those you can
see with your eyes on the screen.
I think the information on gnu.org is not quite appropriate for this
audience.
Beside of this, it's a great idea to show her this kind of information and
then shut the door, but I don't quite know how to proceed.
"Remember there is no such thing as 100% at the moment"
Yes, I was talking about operating systems only.
