Hi Andre,
Le 5 janv. 09 à 19:33, André Schnabel a écrit :
Hi Eric,
eric.bachard schrieb:
I'm not sure to understand. there is an Education Project already,
and instead of working together, and e.g. create a QA department
or something similar you could manage, inside the Education
Project, you created another project/thing ?
If I understand correctly, what you aim to achieve is teach
OpenOffice.org (here QA), so isn't it reinvent the wheel somewhere ?
sub-project ... it just happens.
Ok, so please read below.
Well .. our project is large and diverse.
As Education Project co Lead, Mozilla Foundation invited me at FSOSS
2008, and I discovered several years of work from them. And following
Mozilla Project experience, this is a bad idea to teach and work
together (they tried already ..). Second, they created a consistent
content. Not only one part, and nothing else.
That's why they concentrated everything to be teached in one piece,
and have separated IRC channel, and so on. Mainly to avoid bothering
the devs.
Could be a great idea to learn fro the experience of the other,
couldn't it ?
And some things are just done at the places where people lurk
around in their daily work.
What is the idea : today QA, tomorrow another project, and a day,
think "hey; why not group all ?" ... and finally understand the
Education Project is the answer, but lose several years first?
Again, I invite to *group everything at the beginning*, share the
resources and the energy: just objectivity, and consistency/good
sense. Create yet another "internal school" can even be desctrucive,
and is similar to "bad energy". Do we need that ?
This is not to offence "this or that" sub-project. (E.g. coaching
new members in doing translationsandqa workisone of my daily tasks)
This is not an offence problem, really, and this is no problem with
me to discuss.
The obvious point is : Education Project aims to teach all
OpenOffice.org (this is what is was thought for), means teach
everything we need, to mentor new people joining, and lead them to
become professional in the whole OpenOffice.org project
Teach code without talk about QA is wrong. Teach QA without code is
wrong. If you look carefully (unfortunaly down at the moment), QA has
already it's place in the list of courses I wrote, long time ago.
This is natural, means "included".
So why separate ? Worse, why use a private school, with non free
courses ? Means this school can copy everything of us, but does not
share. Is it the right model for an Open Source Project?
*Share and be open* are the idea of Education Project, and since a
year, I invite people to join us : we are open.
I could add: when there is a will, there is a way.
I'd suggest to track the work of Natalia and Oleg and see what
could have been done better (or what could be adopted by the
education project).
I'm sorry, but I don't have time. That's even why I invite people in
charge of that, to join the Education Proejct, and create QA part,
and share the idea, the methods, and so on.
Happy New Year to all of you,
Eric Bachard
--
qɔᴉɹə
