Regarding the wording, from my perspective (as someone from the US), the implied meaning of the wording depends mostly on context.

"We are trying to educate new users on free software principles" for example may have the unintended implication that we are ideologically placing ourselves above the uneducated new users, and will be doing them a favor, pulling them out of their woeful ignorance, into the light of our sublime software-based religion.

Now that's not at all what we mean, but this is something I've seen time and time again. I explain what free software is and how it respects people's freedoms, etc. I come off sounding like I'm part of some paranoid cult (of which there are many in the States). I may as well be cycling through town in a suit knocking on people's doors and handing out pamphlets. 

In my experience people don't care as much about personal freedom as they do about convenience, and how the piece of software will help them have a better life. That's not to say we should not mention that as a goal of the project, but as a leading banner, it's just not something most people seem to care that much about.

Now if we describe free software in terms of benefits to the user (and developers) individually, and as part of a community, education (in terms of all education, all around the world), open formats that everyone can use for free, you start to paint a picture of the utopian digital society we are after without having to presuppose that it is.

The minute I mention source code in terms of privacy, most people start to get uncomfortable. They can't read the code after all, nor do they believe they have time to learn it, and I'm starting to look like a cultist now saying "all software should be free", and "people and governments are invading your privacy with your own computer." First impressions are important.

These days I take a very minimalist approach to talking about free software, and tailor the description for who I'm taking to:

To students and teachers:
"Free software enables people to work and learn without having to pay license fees for every computer, so it helps people all over the world better themselves and use high quality, community maintained software without a financial barrier."

To startups, entrepreneurs, and business people:
"Free software can be used by anyone, and can be changed to suit their own needs. This allows parts of programs to be reused in different ways, and contributes to innovation, allowing ideas and new technology to be freely adopted without a lot of software licensing overhead. It also provides the basis for collaboration, open formats for interoperability, and an active welcoming community with a wealth of free documentation, examples etc. Also, if something goes wrong, you/your company/your team have the ability to fix it right away."

To people complaining about viruses, expensive computers, etc.:

"I've got a USB drive that could change your life! Let's back up your important files, and I'll lend you a computer with different software on it for safe internet browsing, and an App store built right into it for all your productivity needs. Use it a week, and if you like it, well put it on your machine." Week later: "Yea, it's really cool isn't it? Price? How about free!"

Regarding the principles of free software, I always direct people to the FSF website. That is the home of FOSS anyway. It's not like I need to reinvent the wheel, or provide a description that is less thought-out and lacking compared to what the creator of copyleft has intended.

In my experience, users of all types need to warm up to something before they are willing to listen fully. I always show the benefits on the surface first, and then if they ask about the deeper world-changing stuff, I'm happy to discuss further.

None of this may be what you want to do with Inkscape, but it's the best way I've found to "sell" open source to new people, fwiw.

-C


On 13 May 2015 01:32, "Bryce Harrington" <bryce@...961...> wrote:
On Tue, May 12, 2015 at 06:36:42AM -0700, LucaDC wrote:
> Bryce Harrington-3 wrote
> > Heh, I guess that's one way to interpret what I am trying to say, but
> > really I should be more explicit:
> >
> > If we have a mission here at Inkscape, it isn't to get everyone using
> > our software.  Nor is it really to stop people using Illustrator or
> > anything negative about proprietary software; after all, we're actively
> > supporting proprietary OS's and enabling people to remain on those
> > systems with our Windows and Mac builds.
> >
> > Rather, I think our mission is to _educate_ people about _making_ free
> > software.
> >
> > So, in our coffee analogy, what we should be doing is educating the
> > people who come by about how we roast our beans, maybe tricks for
> > getting different tastes out of them, and how to do all the various
> > chores needed in operating a garage coffee shop.  They may come by
> > simply for the free coffee, but we want to see that working together to
> > *make* the free coffee as part of a community is even more rewarding.
>
> Good positive elaboration :) I second it, of course.
> Still, I dislike the word "educate" (I'm not a native English speaker, so
> maybe I'm wrong). What about: "Help people realize that contributing to free
> software is more rewarding than simply using it"?

Does educate have a bad connotation in your language?  In the US
'reeducate' can give images of cult brainwashing and such, and
'indoctrinate' gives images of missionaries putting the fear of god into
natives, but I don't know of common interpretations of plain old
'educate' that are quite so negative.  Maybe teach or coach would be
better.

In any case, it doesn't really matter what we call it, so long as we're
good at doing it - helping new folks learn what makes free software so
great, and showing the ropes of how to get involved.  Make them feel
comfortable making contributions, and give them tips to help improve
their work techniques.

I also like the idea of organizing deliberate lessons on key topics, to
help disseminate good know-how.  We did a bit of this at the hackfest on
several different topics (Architecture of Inkscape internals, State of
imported libraries, Editing the Website, etc.), and I'd love to see us
start doing that more broadly, perhaps through Hangouts or similar.

> IMHO starting from the assumption that only contributors deserve attention,
> the final product is going to miss a big actor in the process, that is the
> mass of passive users from where new fresh and innovative contributors may
> come. A product which is not attractive for who is "outside" is going to
> slowly deflate or stall. This to say that people should be brought "inside"
> not by "teaching" (educating) them what they should do, but by showing them
> the advantages of being an active part of the game.

If you re-read my analogy above, I think you'll see we're in violent
agreement.  :-)

Bryce


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel