The best way to start is to work off the SVN tree (pick your poison, the
stable 1.1 branch, or the nearly deadly trunk). For now, submit patches
to zenoss-dev. When that gets awkward, we can grant SVN write access.
The corporate guys may require a copyright waiver or something if the
code changes are significant.
Starting with 2.0, you should be able to customize a lot of Zenoss
without changing the existing code base. If there's a hook you need, we
can make that happen.
There is a target in the inst directory to generate documentation from
the code. It needs to be expanded.
A much-needed developer's guide is a task for this summer.
-Eric
Noah Gift wrote:
I have a project I am working on where I would like to work with the
Zenoss source code and possibly make some contributions. What is the
best way to start? Is there any formal source code documentation?
Thanks,
Noah
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
