Hi,
On Tue, Jun 17, 2008 at 07:18:56AM -0700, Kristis Makris wrote:
> I'm not sure how much help Yann Dirson could be. He had started work on
> a GForge tracker a long time ago at work, but was not allowed to finish
> it:
Indeed the project was never validated and did no go past the
"thoughts" stage.
Nevertheless, I still have ideas :)
The GForge SOAP API could possibly be used, but it should be checked
first to verify the feasability. Particularly, at that time it would
not allow any particular ("scmbug") account to modify gforge tickets
as another user. If you can patch GForge to add a new tracker-related
permission flag on users, as well as extend the SOAP API, I guess
writing the scm-bug backend will be quite straightforward. So for
this path tight collaboration with the GForge team would be a must.
Otherwise you'll have to hook the database directly, but that's very
risky since the db schema changes quite often. And the internal APIs
to the DB are mostly available for PHP, so even if they would not move
you probably could not use them.
I wish you the best for this project, it will be a great addition for
all gforge users !
Best regards,
--
Yann
PS: you may have seen my sagem.com is not valid any more.
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
