Comment 57 for bug 507511

I would to be clear here about GOsS...

I don't like this. I don't understand what a GOsC mentor need to do exactly, ho to start... etc... And i don't want to read a huge collection of paper from google to only guide a student with Google rules. Sound like very complicated and unadapted to open source project !

To resume my viewpoint : It's a waste of time for me...

I know how to follow students in real job. I do it everyday. I'm also a teacher and i like to share informations, and see working progress in a project.

But seriously, GOsC add rules witch are definitively not adapted to open source project.

In open-source, why to add GOsC constraints ? It's already difficult to follow standard contributors, check/review patches, guide all peoples who want to help. Time is precious and i don't want to lost time with GOsC, to follow students release dates, write papers, etc... with no guaranty of results...

And i have a real life outside this computer.

How i work : when time permit ! Look this entry for ex:

https://bugs.kde.org/show_bug.cgi?id=149485

Here a student, outside GOsC, works on new Liquid Rescale tool for digiKam image editor. And it's work very well. Progressively, the job is done on the right way. There is no advantage for me to use GOsC to follow this guy.

And i work on open-source since a very long time now. I have a very good experience on project management. so, i'm sorry, but GOsC is not an advantage for me...

Gilles Caulier.