Contribute to SIRAGI (was : Re: About Arabeyes Quality Software Standard)

[Tarik FDIL <tfdil at sagma dot ma>]

Alaykoum salam Ahmad,

Lassad and I will be very glad if you join your efforts to us. Together we can 
do good job !

We're rethinking SIRAGI-OCR from the beginning. It's important to fulfill 3 
topics : 

- produce a good design. I'm working on high level design. I'm going to post a 
first release today. We should discuss, detail and validate this design 
before writing code. All code written so far is just a little test. Code 
should be based on known, validated design. All arabeyes developers can 
contribute to discuss the design of project before it's validation. It's easy 
to contribute in a project when there's a detail design showin what and how 
to do the job. 

- plan the project. Even the project plan is always evolving, we must have a 
plan. If we can just working 2h or 4h per week in the project, we should plan 
our tasks on this basis.

- implement the design using strict coding rules. Arabeyes Developer Guide is 
a good starting point, but there other rules to implement to have clean 
source code.

So welcome Ahmad to SIRAGI-OCR project and let's start by a good design.

Best regards

Tarik

Le Dimanche 14 Mai 2006 19:08, Ahmad Sayed a écrit :
> Salam  Alikom,
>
> i worked in an arabic OCR before using python and a develop a segemntation
> algorithm using numeric library bundled with python that gives good
> performace, that works but i got some trouble with (SEEN and BAA') س و ب so
> while searching  i rediscover your project to be honest i know about it
> before
> but reading your segementation algorithm i found that i almost do the same
> algorithm i did testing it it gives similar results so i'll be happy to
> join you in this project instead of creating my own, i tried a lot of
> segementation algorithms or to be more accurate enhancment for this
> algorithm but i also failed to get segmentation that satiisfy me to not
> wasting your time reading a long email just i could offer my help if you
> want.
>
> On 5/13/06, Tarik FDIL <tfdil at sagma dot ma> wrote:
> > Salam,
> >
> > With Lassad, I'm going back to Siragi-OCR project. Since we aim to do
> > good job, we've some questions about quality software in arabeyes
> > projects.
> >
> > UMHO, producing quality software need at least some tools and practices
> > in "planning", "designing",  "coding" and "quality measuring"
> >
> > **Planning**, I think the "Todos"  tool in arabeyes.org is a good tool
> > for planning and monitoring projects and parts of projects. Without
> > planning projects we can't know how much of project is done and what's
> > the remainnig
> > work.
> >
> > **Designing**, coding is a good think but designing software before
> > coding it
> > is better. Without sound design, we can't produce bug-free, evolving and
> > maintainble software. Since design is essentially producing documents,
> > Arabeyes CVS is a good tool to store and track design documents. Every
> > design
> > language could be used. I personnaly like UML... But is there  free
> > software
> > tools to produce UML diagrams ? Anyway we can always use OO to produce
> > basic
> > diagrams.
> >
> > **Coding** we should write code following a coding standard. Is there an
> > arabeyes coding standard ?
> >
> > **quality measuring**  bugs.arabeyes.org/ is a sound tool to track bugs.
> > But,
> > to be meaningful, bugs measurements should be counted per lines of code
> > (or
> > function points). Is there an arabeyes standard  to count LOC (Line Of
> > Code)
> > in C, C++ or other languages used by arabeyes developers ?
> >
> > Best regards
> > Tarik
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Developer mailing list
> > Developer at arabeyes dot org
> > http://lists.arabeyes.org/mailman/listinfo/developer