Gents,
Below is our MOM for yesterday's meeting. We have decided to split the
work into phases. Please go through this list before I refine it and put it
somewhere (SourceForge, or another place where we can have our specs). I
have also included the MOM from the previous meeting. Let's target 1-2 weeks
to finish all the requirements.
Your feedback makes a difference, please share your thoughts.
*********************************************
17th Feb, 2007
Attendees:
Hafez
Faisal
Mamoun
Ahmad Fathi
Ammar
Word Status:
- Approved
- Under revision
- untranslated
- draft
- Conflict
- Under voting (board members)
Phase I
- Project site
- Project Blog
- Allow users to report mis translated terms and suggest another
Form: email (to contact reporter), comment, suggestion
- Request new word to be translated
- RSS (news, terms)
- Export formats (XML SQL, PHP, Plain Text or CSV)
- Stats
- List of untranslated words
- Box on "every page" of random untranslated words to help users contribute
- Search
- When term is not found, give option to submit for moderation
- Login
- logs & tracking
- Something like send to friend
- version control (history)
- Admin Interface
- User Management
- Moderation
- list of changes
- Admin stats
- Word list/translation management
- blocked words
- classification
- moderator based lock
- login based lock
- word queue
- Word Conflict
Phase II
- Synonyms, Antonyms & related terms
- Webservices (REST)
- report bug/issue/broken link ..etc
- Browse & explore
- Firefox extension
- English Interface
- Spelling
- Suggestions
- Word Amiguity
- Rating system (we don't need this, removed from specs)
- Alerts
- Alert me when this word changes
- Alert me when a new version
- Formats (QtLinguist, GETTEXT)
Phase III
- multilingual translation support
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/
-~----------~----~----~----~------~----~------~--~---
