Apache OpenOffice (AOO) Bugzilla – Issue 24361
mentoring program
Last modified: 2017-05-20 10:32:03 UTC
This issue is to track progress on the mentoring program specified in the council minutes for 2003-11. louis
Adding myself as CC
adding MH... whom I ought to have added immediately. (but, he reads these anyway) Louis
Adding myself to the CC list.
Do you think it would be possible to work towards a mentoring program to be launched or initiated at OoCon2004? I proposed this as an agenda item to the CC (http://council.openoffice.org/servlets/ReadMsg?list=agenda&msgNo=87), but then withdrew it as I thought I better ask the people doing it - first :) The opportunity for mentors and mentorees to meet for a full on get stuck into it day at OOoCon 2004 I think would really be worthwhile not just to get a mentoring programme underway, but to attract potential developers that are wondering how to get started. If you think initiating this at OOoCon 2004 would attract mentors and mentorees, and therefore worthwhile pursuing please let me know how I or others can help.
Hi I think we should follow Jacqueline's suggestion. But that means that we should then create an agenda of issues to be discussed at the conference. What is needed (now and later) is a report on how the GSL effort has gone. Further, where issues lie, where mentoring is needed, and how. louis
Suggest we work with the SLUG initiative at http://www.communitycode.org This is for mentoring and also to assist others provide their 'community obligation' required by someone through coding FOSS if required.
interesting! How do you envision this working? BTW, the mentoring program status is not reflected in this issue. Essentially, at a meeting in Berlin, during the OOoCon, we agreed on: *Our goal: to achieve transparency in the process, a good example of this being the GSL project. The overall idea: to give developers an accurate sense of the state and progress of their patches. The ESC has since taken this on, and has an AI--not sure it's recognized--to come up with general guidelines for patch submissions. I proposed such to the ESC late September; it was ignored :-/ [1] The ESC has continued discussion. The basic discussion revolved around scripting guideilnes. We agreed that rigid guidelines were not desired, but that individual projects should be given individual freedom: general rules, individual deviations. See : http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=423 The program, in short, is now focused on making it easier for developers to actually submit code, and to make it transparent to them where their submission is in the process. The ESC is obligated now to report on the status of this. Once it's done that, we can post it to Development category. That does not mean that we should not work with others! Just updating. thanks louis
martin, do you have an update on the information page you were working on per CC suggestions earlier 2006? thanks, louis
in the meantime irc team meeting have been established where people can ask for getting mentors for their work. see http://www.google.com/calendar/embed?src=k4bgtc8bil9cs2a77lhh1r998g%40group.calendar.google.com for meetings schedules. I would like let the teams decide on how to formalize this.