Custom Query (332 matches)

Hi Bas,

I'm looking after WANdisco's input to Apache Bloodhound, which is an ASF
project based on Trac, aiming to improve the default packaging
and provide an easier to use and more accessible defect tracker out of the
box. You can find out more at http://incubator.apache.org/bloodhound/
(although
it is still early days!)

As part of the work we'd doing we are hoping to include some useful Trac
plugins, pre-configured and ready to use out of the box. In the case of
email2trac, we believe your tool provides essential functionality and are
wondering if you would consider allowing this to be used as part of
Bloodhound? We'd be happy to help maintain the tool going forwards and
would also welcome any suggestions you have for ongoing collaboration.

Obviously the GPL license of email2trac restricts us from including
email2trac as it is today, so the first question would be whether this is
something you and any other authors of email2trac be interested in talking
about further, either by email or on a quick conference call?

Best Wishes,

Ian

--
Ian Wild
Director of Engineering
WANdisco, Inc.

Cell    : +44 (0)7961193722
Office DDI: +44 (0)114 3030472
US: +1 925 3801734

http://www.wandisco.com

uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com <http://www.ubersvn.com/>

Everything you need to deploy Subversion in the Enterprise
http://www.wandisco.com/subversion<http://www.wandisco.com/subversion/multis
ite>

Subversion community
http://www.svnforum.org

There was a case where the lower method on a string was referenced as an object instead of actually making a method call. I've added a patch for it.

Hello, email2trac developers.

I'm a developer of DiscussionPlugin for Trac [1] and one of its users
requested an e-mail posting support for it [2]. I see that a good way to
implement this would be to extend your email2trac set of scrips so I'm asking
if would it be acceptable for you to include to mainstream possible patch that
would add DiscussionPlugin support to email2trac or should I fork/reuse
email2trac (or something else) in standalone solution or start to implement
something from scratch?

I haven't studied email2trac code much for now so I don't know how to do it
exactly yet, but in case of possitive answer, I'd digg more into it. Anyway,
any hints or advices would be appreciated.

Thank you for making your stand on this topic.

[1] - https://trac-hacks.org/wiki/DiscussionPlugin
[2] - https://trac-hacks.org/ticket/6883

With best regards,