New Project: Zekr
mohsens at gmail.com
Fri Apr 6 07:30:39 EDT 2007
Here is a new project.
On OLPCs withough Sun's JRE 1.4.2+ or GIJ 4.1.2+, there is also a
native compilation with GCJ available.
1. Project name : Zekr
2. Existing website, if any : main website: http://siahe.com/zekr
alternate website: http://sourceforge.net/projects/zekr
3. One-line description : A Quran study tool, for simply browsing
and researching on the holy Quran.
4. Longer description : Zekr is an open-platform Quranic
project, to researching on the holy Quran. It's a rather light-weight
core with a number of Quranic resources (translations, bookmark sets,
themes, ...). Zekr is written fully in Java (1.4.2 compliant), and
uses SWT as a native wigdet toolkit.
5. URLs of similar projects : -
6. Committer list
Please list the maintainer (lead developer) as the first entry. Only list
developers who need to be given accounts so that they can commit to your
project's code repository, or push their own. There is no need to list
Username Full name SSH2 key URL E-mail
-------- --------- ------------ ------
#1 mohsen Mohsen
Saboorian http://siahe.com/zekr/dev/pubkey.txt mohsens at gmail.com
If any developers don't have their SSH2 keys on the web, please attach them
to the application e-mail.
7. Preferred development model
[ ] Central tree. Every developer can push his changes directly to the
project's git tree. This is the standard model that will be familiar to
CVS and Subversion users, and that tends to work well for most projects.
[X] Maintainer-owned tree. Every developer creates his own git tree, or
multiple git trees. He periodically asks the maintainer to look at one
or more of these trees, and merge changes into the maintainer-owned,
"main" tree. This is the model used by the Linux kernel, and is
well-suited to projects wishing to maintain a tighter control on code
entering the main tree.
If you choose the maintainer-owned tree model, but wish to set up some
shared trees where all of your project's committers can commit directly,
as might be the case with a "discussion" tree, or a tree for an individual
feature, you may send us such a request by e-mail, and we will set up the
tree for you.
8. Set up a project mailing list:
[ ] Yes, named after our project name
[ ] Yes, named ______________________
When your project is just getting off the ground, we suggest you eschew
a separate mailing list and instead keep discussion about your project
on the main OLPC development list. This will give you more input and
potentially attract more developers to your project; when the volume of
messages related to your project reaches some critical mass, we can
trivially create a separate mailing list for you.
If you need multiple lists, let us know. We discourage having many
mailing lists for smaller projects, as this tends to
stunt the growth of your project community. You can always add more lists
9. Commit notifications
[ ] Notification of commits to the main tree should be e-mailed to
the list we chose to create above
[ ] A separate mailing list, <projectname>-git, should be created
for commit notifications
[X] No commit notifications, please
10. Vhost setup
[X] Yes, set up a vhost for the domain http://siahe.com/zekr
pointing to our project website.
[ ] No, we don't have a project domain, or don't want to use one.
We'll use the laptop.org website address.
11. Shell accounts
As a general rule, we don't provide shell accounts to developers unless
there's a demonstrated need. If you have one, please explain here, and
list the usernames of the committers above needing shell access.
Zekr project started in late 2004. I has an active commmunity,
making it possible
to have 12 different language packs and a number of Quran translations.
It needs a JRE 1.4.2+ (also works with GIJ 4.1.2), and a Mozilla
GTK2 1.4+ (used for
SWT browser widget). Alternatively on some Linux machines (Ubuntu,
SuSE, ...), Firefox
can also be used.
Zekr project mailing list: http://groups.google.com/group/zekr/
More information about the Devel