Hello Kristis,
I want to summarize my evaluation of this issue. First of all, these
are the 'bugs' I've found for this issue.
http://bugzilla.mkgnu.net/show_bug.cgi?id=547
http://bugzilla.mkgnu.net/show_bug.cgi?id=948
http://bugzilla.mkgnu.net/show_bug.cgi?id=1061
http://bugzilla.mkgnu.net/show_bug.cgi?id=1082
I've considered following options for implementation:
1. Write our own code
2. Wait for Bugzilla 3.2
3. Use Bugzilla's email interface
Option 1: Wouldn't be a trivial task because we have to care about:
- Bug activity logs
- Timetracking issues
- Database integrity
- User and group permissions (Bugzilla)
- Support and maintenance of own code (probably most important)
Option 2: Would be the best solution, because Bugzilla 3.2 will offer
all the API methods we need. But to have some intermediate solution
for 3.0 users I've found ...
Option 3: Use email_in.pl contributed by bugzilla. This may also work
for older bugzilla versions, but I would focus on bugzilla 3.0.x.
Therefore we would have indirect dependencies to following perl modules:
Email::MIME::Attachment::Stripper (any)
Email::Reply (any)
These modules are optional for Bugzilla, but required if you want to
use inbound email. So we would have to add this to the documentation
of Scmbug (might link to bugzilla installation docs).
I've been playing around and the results are quite promising, but
before implementing it this way, I want to have your opinion and
comments.
--
Oliver Schäfer
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
