phpgroupware-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[phpGroupWare-developers] Ideas for phpgw / RFC


From: Caeies
Subject: [phpGroupWare-developers] Ideas for phpgw / RFC
Date: Wed, 27 Jan 2010 14:18:34 +0100
User-agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707)

Hi all,

I'm doing some fixes today, roughly checking for typos with an in house
script that count occurrences of a var in a function (that's really
really basic).

I have a proposition for third-party libraries that we are using
straight from upstream :

We can add in phpgwapi/ a new directory call lib/thirdparty and modify
our CreateObject function accordingly. The purpose of this is :
1) Easier maintenance of thirdparty software (licence issues, easy to
identify what to change into the project, and what to change upstream in
the thirdparty stuff, how to update it, etc ...)
2) better recognition / integration of others contributions in our project.
3) since we are now php 5, migrate the CreateObject function to use the
auto load mechanism and using new as is, for better compatibility with
thirdparty software.

Next. I'm looking for the opportunity to use an ORM in phpgw (propel,
doctrine, redbean, php-activerecord, ...) and doing here a RFC about it.

Next. Can I strongly suggest everyone commiting the code in our source
tree to use English var names / db names / translation base / etc ...
That's really easier for us to understand the code and it's philosophy ...

Next. If you want to merge code from a branch or another, can I suggest
the use of svnmerge scripts ? This will help us for merging back things
instead of looking in the history for already done merges, etc ... I'm
open to suggestion regarding other tools to manage the merge stuff.

Happy Hacking,

Caeies





reply via email to

[Prev in Thread] Current Thread [Next in Thread]