On 12/31/2011 1:55 PM, Dirk Stöcker wrote:
On Sat, 31 Dec 2011, Ian Wild wrote:
Unfortunately, no one from the initial group we contacted was able to
commit to working on Trac full time (or even part time afaik). Since
then we have been able to employ a number of experienced Python
developers who are familiar with the Trac architecture and who will be
dedicated to the project. I can assure people that the view so far is
very much in favour of maintaining compatibility with Trac and
even the idea of forking or not is certainly still open to discussion
within the Apache Bloodhound community.
I compare this request now with my situation. Someone like your company
is asking to
* change the server infrastructure and control mechanisms
* change the license
* ask if core contributors will work for you full-time/part-time
for JOSM.
Actually my answer would be no for all of these requests. It took a long
time to establish running services, the code license is fine and I like
the job I have.
I don't see why Trac people should behave different.
Yes, that was exactly our situation and reaction as well.
[...]
But in the end I don't care. You have the right to do what you want to
do, so do it. If you can create a better product than Trac which is
compatible and does work with the dozens of extensions I made for my
existing installation, then I will happily switch. Otherwise I will
stick to Trac and continue to extend and improve it when necessary.
+1 ;-) We never frowned at anyone switching to Redmine for example, we
won't blame you for switching to Bloodhound if it becomes a better
alternative for you! (But if even in doing so, you could continue to
maintain the SpamFilterPlugin to its excellent level in a way that would
be compatible with the "legacy" Trac, all the better ;-) ).
-- Christian
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to trac-dev@googlegroups.com.
To unsubscribe from this group, send email to
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
