why not using drupal book in jolug? On 2/17/07, Ammar Ibrahim <[EMAIL PROTECTED]> wrote: > > Our page on wikibooks will be deleted. Will try to find another wiki, > I'm pasting what we have for now just in case. > > > ---------------------------------------------------------------------------- > 4th Feb, 2005 > JoPHP Meeting > In the meeting we discussed the first steps in arabization project, > and we concluded to the following notes. > > Project Name: Ar8n Glossary > Goal: create a unified glossary for all Arab users. The goal is to > have one translation per one ICT term. > > System features: > > * Words Management. > * Approval System. > * Search Engine / Spelling / Suggestion. > * Word Unambiguity. > * Bilingual Interface. > * Importing / Exporting List. > * Admin Area. > * Users Management. > * Rating System. > * Words Classification. > * Revision / Versioning System. > * Statistics / Reporting. > * New Words. > * New Suggestions. > > Technical Details: > > * OS: Linux. > * Language: PHP 5.2. > * Web Server: Apache. > * Database: MySQL 4.1+. > * No stored procedures, triggers etc. We'll do it the old MySQL way. > * PDO, all database statements must be prepared and binded before > execution. > * MVC architecture. > > Words Management: > > * Terms. > * CRUD (Create, Read, Update and Delete). > * Translating. > * Rating. > * Classification. > > Notes; > > * Rating Process Work-flow: > o Word is created. > o Admins are notified through the New Words Area. > o The first suggested translation is temporarily accepted as > the standard one. > o Suggestion Period: For some defined period the admins (and > maybe users) would submit suggested translations. > o Rating Period: For some defined period the admins should > choose a translation from the suggested list for the term. > o In the end of the Rating Period the translation with the > largest number of rating would be chosen automatically as the standard > translation for the term. > o Users would have the ability to rate the translation in a > binary mode (yes, no), so maybe it would be modified later. > * Modification Process Work-Flow: > o Some admin chooses to modify a word with a new meaning, > and he submits his request. > o Modification Acceptance Period: For some period of time, > the admins would choose to whether accept the modification request or > not. > o If the admins voted not to accept the modification, the > whole Modification Process would be ignored. > o If the admins accepted the modification, it would run > through the Rating Process Work-Flow. > * Classification (Level 1, for the admins): > o Abbreviation (eg. PHP, XML, ...) . > o Brand Name (eg. Google, Microsoft, Debian, ...). > o Term (eg. File, Directory, Spam, ...). > > > UML and Diagrams: > > * Ar8n use case diagram > ------------------------------------------------------------------------------- > > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Jordan PHP Users Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/JoPHP http://Jolug.org/ -~----------~----~----~----~------~----~------~--~---
