Thank you very much! When I first noticed connector discovery bug
272621, I immediately knew that I want to get Foglyn there. You guys
have made a great feature, and it's a honor for me to join other
connectors in c-d listing.
Re using connector as a support mechanism: FogBugz already provides two
ways to receive feedback from users: 1) email -- FogBugz can be
configured to fetch emails from pop3 account and convert each email
into case automatically, 2) BugzScout -- simple HTTP API for sending
new cases, targetted more to automatic submission of problems
(http://www.fogcreek.com/FogBugz/docs/60/topics/customers/BugzScout.html).
I am pretty sure that I will use one of these mechanisms to submit bugs
directly from eclipse/foglyn. I think that extending mylyn's support
mechanism to emails would be beneficial for other projects too, and I
hope to take a closer look at this when I have more time.
-Peter
Steffen Pingel wrote:
The vote completed with the following result:
+1 : 6 votes
0 : 0 votes
-1 : 0 votes
I have added Foglyn to the Community section in the discovery portal
listing. Congratulations to Peter!
Note that the Tasktop Certified portion of the portal which was
approved in a previous vote is now also visible. The listing is still
not complete and some features may appear disabled due to incomplete
update sites but we expect everything to be ready by June 24th.
Steffen
On Mon, Jun 22, 2009 at 10:16 PM, Mik
Kersten <mik@xxxxxxxxxxx> wrote:
+1
In addition to being impressed by the connector during its review and
with Peter's responsiveness to feedback, it has been good to see Peter
collaborating with the Mylyn committers and providing patches.
One issue that came up during the review of the connector on the call is
that it does not use itself as a support mechanism, i.e., for reporting
bugs. That kind of bootstrapping has helped other connectors harden
around
the feedback of their users, and I think that it's generally a good
idea for
connector authors to consider. I realize that with the case of Foglyn
this
would require an additional license to FogBugz, but it should be
beneficial
to Fogcreek overall, so I imagine they would be open to that.
A side issue that arises from this is that since the connector is under
a
commercial license, we'll probably have to rename the Community section
to
something else. It's common to see "Community" equated with "Open
Source"
and "Commercial" with "Closed Source / for pay". If anyone has any
ideas on
what the section should be called please comment on:
276235: create Mylyn discovery site content
https://bugs.eclipse.org/bugs/show_bug.cgi?id=276235
Mik
--
Mik Kersten, Ph.D.
CEO: http://tasktop.com/blog
Project Lead: http://eclipse.org/mylyn
__________ Informacia od ESET NOD32 Antivirus, verzia databazy 4179 (20090622) __________
Tuto spravu preveril ESET NOD32 Antivirus.
http://www.eset.sk
|
