Re: [Rdfapi-php-interest] Introduction

[Christian W. <cw...@cw...>]

Hello Pieter,


> In there any "hierarchy" that I should be aware off?
Big changes should be announced/discussed on the list.

> Which versions of PHP are supposed to be supported?
I also had this question some time ago, and the answer I got was that
PHP5 is fine and that RAP should move to PHP5 more sooner than later -
it's just that nobody has the time to properly move everything to it.

> Is it allowed to check-in PHP code that depends on PHP
> 5.2.x features, like for example the magic __toString() method?
SparqlEngineDb does not work on PHP < 5.2 since it relies on the
__toString() magic, so I think it's ok if you take 5.2 as base.

> Is there some release-cycle that I / we should adhere to?
If there are enough new features/bug fixes, a new release can be pulled.

> Do I understand correctly
> that active development takes place on the trunk?
Yes.

> Is there some latest-release-with-bugfixes branch to which I should
> commit bugfixes, parallel to the trunk?
No.

> I couldn't find a script to
> generate the PhpDoc documentation in the subversion tree. Could tell
> me how (with which parameters) phpdoc was invoked, in order to
> generate the phpdoc api documentation?
I don't remember, just with as few parameters as possible (that is,
those needed to specify the code root and such).

> I saw that Sourceforge offers
> the possibility to have a Wiki for each project. Wouldn't it be a good
> idea if all the documentation were transferred to a Wiki, so we can
> all collaboratively make changes?
That'd be good - documentation is not ideal at best, manifested in HTML
files that haven't been changed since they have been written years ago.


> What's the policy regarding code changes that aren't backward
> compatible?
A good question. I always kept legacy code working.


Nice to have another active dev on board :)


And please, use the unit testing framework extensively.

--=20
Regards/Mit freundlichen Gr=FC=DFen
Christian Weiske