Hello Sankarshan, Louis, and everybody here, Sankarshan Mukhopadhyay wrote:
> >We will collate and collect the issues (a majority of which would have >Issue Tracker entries) and present a comprehensive document for the same. > > Good. > > >>They also have to do with the impression that the process by which code >>is submitted, evaluated, incorporated is opaque. The overall solution, >>I believe, lies in making the relevant processes more transparent. The >>Engineering Steering Committee has been working in this direction but >>perhaps something more from it would help. The idea, after all, is to >>promote development of OOo everywhere. >>The general feeling is that in some cases there exists some bit of >>communication gap in terms of understanding the local priorities. >>Obviously, a project cannot start being sensitive to each and every >>locale it touches and the issues therein - that is a sure shot recipe >>for chaos. What would be desired is a clear direction in terms of who is >>the GoTo team for the issues, how does the Engineering Steering >>Committee view the path to resolution, how to map Indic priorities with >>the product roadmap and priorities as well as release schedules and more >>importantly is it possible to make such native language developers part >>of the ESC. >> >> I may have an idea here; it may sound a bit artificial but maybe the Indic NL group could appoint somebody -Vijay Kumar- for instance as the permanent contact for the ESC. I do realize that it is a two way effort, so "coaching" the ESC on the strategic importance of the Indic group concerns, and in the mean time, the concerns of the native-lang projects could be a good idea. What I have in mind, and that can be done asap, is to draft a page in the wiki reporting the most crucial issues at hand for all the native-lang projects. Certainly some common patterns will emerge and this can be brought to the ESC. > > > >This is another important point. A consequence of the interest in the >Indic enablement has been that a lot of upcoming contributors want to >contribute to OpenOffice.org. The notion would thus be to - direct, >goad, coach and guide them into the direction which require most love >but also fit in with their skill sets. GNOME has a nice way of >addressing this by having dedicated BUG Days where a lot of real time >mentoring happens. IRC provides a somewhat limited (bandwidth access in >India is still an issue) but very real time way to meet this high touch >activity. Having local mentors who are present, active and serve as >guides would be best placed to do the needful. What it needs to begin >with is a list of things expected out of the mentors, what specific >areas need to be targetted and a single landing page for all this >probably on the wiki. > >Louis, I tentatively agreed then - I put up my hand now. > > > I think every native-lang project should have its own local initiatives. Mentors are a very good idea; bug hunting parties and Code-athons are another. These have been a success in the Macedonian and Catalonian projects, for instance. More generally, I gradually came to realize that there is a social aspect that is actually one of the keys to success for native-lang projects. This is why gatherings of any kind, dinners or whatever are also good things to take place inside Native-Language projects. >A little bit of direction, a whole lot of collaboration and more >importantly constant interaction would enable us to take OpenOffice.org >to greater heights. > >To all the developers who strive to make OpenOffice.org better with each >passing day - my heartfelt thanks. I guess someday Louis will post about >his views on how passionate the Indic NLP is on OO.o. > > > Thank you for your kind words, Sankarshan! As already said, we can set up whatever tools you guys want on the wiki. We have an NLC section there and many NL projects make already good use of the wiki. Best Regards, Charles. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
