[geeklog-devel] Getting started with Geeklog development
ascepanovic at gmail.com
Sun Mar 8 11:22:58 EDT 2009
This is cool way to motivate new developers to contribute. The biggest
problem in my opinion is documentation because classes and methods doesn't
contain detail information about their job...
Of course something is better then nothing :) But if source code is
projected to be self documented diving in to Geeklog development would be
faster. Extjs based API documentation can be implemented as PHPDocumentor
theme and I honestly believe that development will be much easier with
documentation like this...
If someone isn't famiiar with Ext docs check this url:
On Sun, Mar 8, 2009 at 10:42 AM, Dirk Haun <dirk at haun-online.de> wrote:
> I've made an effort to make things a little easier for those wanting to
> start with Geeklog development (not only for GSoC). Comments welcome.
> As you may have seen from my recent commits, I've played around with
> phpDocumentor in an effort to get it to generate some sort of
> documentation of the Geeklog sources. The current state can be seen at
> I've set up a cronjob to update it from the Mercurial repository every
> night, so it reflects the current development version. Needs more work,
> but it's a start.
> I also wrote a (very short - Developers are impatient ;-) "Getting
> Started" document:
> And finally, the nightly tarball is now ready to use (just like a
> regular release), i.e. it includes the required PEAR classes and leaves
> out unused / experimental code:
> That should make it easier to try out the current development version.
> bye, Dirk
>  more like "struggled with" ...
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geeklog-devel