Re: Code analysis Module contribution

Hi,

Thank you for your concern , I'm truely pleased for being welcomed for contributing in This module specialy and openOffice generally .. I will start wroking by understanding JCA , CVS and CWS working models to be able to fit in , In the same time I will be working on a proposal to my Faculty on this module and creating vision of what I specifically am going to do , In the meanwhile I can use your help by getting the requirements specifications of this Module .. can you support my by details for this module or I shall start from scratch Using the general Idea of checking flexibility , maintanability , etc... meaning Quality of code produced??? and if so shall I start with hypothesis that the C++ checklist is already used and Java standards are used ?

Thanks in advance

>From: Martin Hollmichel <[email protected]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: Re: [tools-dev] Code analysis Module contribution
>Date: Fri, 17 Jun 2005 15:33:31 +0200
>
>Hi,
>
>thank you for your application. Any contribution to the
>OpenOffice.org codebase, which makes the source more flexible,
>maintainable or more extensible are definitely welcome.
>
>Can you please describe what your first steps will be and how we can
>help you. Please also have a look on
>http://contributing.openoffice.org/programming.html for details on
>how to contribute to the project. Please alsp have a look to
>http://www.openoffice.org/licenses/jca.pdf to make work via CVS and
>cws
possible.
>
>I'm looking forward to your contributions,
>
>Martin
>
>Mohammed Mamdouh wrote:
>>Team member names
>>1- Teacher Assistant.Hani Samir
>>2- Mohamed mamdouh Kamel
>>3- Ramez gbriel Michelle
>> Email
>>1- [email protected] <mailto:[email protected]>
>>2- [email protected] <mailto:[email protected]>
>>
>>project Title
>>Code Analyisis
>> *We are kindly asking for*
>>Assigning this module to us or joining or team to the team working
>>on it if exists
>>
>>Synopsis
>>Keeping the code flexible, maintainable, extensible, is highly
>>desired,as the Module describtion said sowe intend to develop a CWS
>>that

can be used by openOffice.org developpers to detect areas of
>>code that doesn't satisfy desired quality of code flecibility,
>>maintainablity,extensiblity and satisfy organization standards for
>>code production
>> Benefits to the openOffice Community
>>Such a tool when used will ensure code compatibility with standards
>>of Openoffice.org , increase reliability of code and decrease time
>>of code testing and QA phases at some points related to code, As
>>well this tool can be used generally as an open source tool for
>>free code errors or quality assurance for later projects
>>
>>Project Details
>>1- Increasing reliability of code submitted to the project
>>2- Decrease QA phases at some points that takes alot of time
>>3- Increase
production speed for the project
>>
>>Project Schedule
>>How long will the project take?
>>Time estimation still not final but rough estimation for 4 Months
>>more or less
>> When can you begin work?
>> As fast as we get acceptance for working on the Module
>> *Benifits for our team*
>>1- high experience in reverse Engineering
>>2- Experience in open source projects
>>3- This project can be a part of our graduation project
>>
>>Bio
>>we are undergradute students in Faculty of computers and
>>Information, Computer science Department, Cairo University in Egypt
>>, we Have More than three years of Experience in the following :
>> *
Java (proffetional)
>>* C++ (Expert)
>>* Datastructures (Expert)
>>* FileStructures (proffetional)
>>* Software Engineering (Proffetional)
>>* Artifitial Intelegence (Intermediate)
>>* prolog (Intermediate)
>>* Assembly (proffetional)
>>* Database Design (Expert)
>>* Computer organization and Architecture (Intermediate)
>>* Computer Graphics (fair)
>>* GUI Via Java (Expert)
>>* web programming via ASP.NET and JSP (Proffetional)
>>* Networking (proffetional)
>>* SQL
server
>> Note : this is not our first E-Mail but we are willing to
>>contribute
>> thanks in advance
>>your concern will be highly appretiated
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [email protected] For
>>additional commands, e-mail: [email protected]
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>