[chandler-users] First impressions

[Yorgos Pagles]

Hi Heikki,
I 've used Eclipse for quite a while in the recent past but it didn't
fit my personal taste after all. While using it I went through the
phase that I guess every Eclipse user has been of installing every
possible plugin out there. I also have used Mylyn (not heavily but to
some extend). I must admit that the ideas behind it are quite
impressive but if you 'd ask me where I would like to keep my issue
tracking while developing I would vote for Chandler more or less using
the approach you described. I think of the issue tracker as the
collaboration means of a developer with his team / management / q&a /
clients and I think that Chandler can fit in this role better than an
IDE.

Regards,
Yorgos

On 11/1/07, Heikki Toivonen <heikki at osafoundation.org> wrote:
> Yorgos Pagles wrote:
> > After a few weeks of heavy usage of Chandler Preview (I have also used
> > previous releases but I don't think that they count) as mainly a task
> > list I am delighted with the whole triage idea as it is a very simple
> > and yet effective and powerful way of keeping focused in the most
> > important of the gazillions of taks that require my attention without
> > worrying that I will neglect the not so urgent ones. Stamping my tasks
> > as calendar events comes in handy as a specific task can include
> > setting up a meeting etc.
>
> It's great to hear that, thanks!
>
> > * The starter project "integration with bugzilla" you have in your
> > wish list would be for me "integration with issue trackers" as we
> > don't use bugzilla but some other issue tracker. You should know that
> > most developers' main collaboration tool is their issue tracker. I
> > think that I could help with this one if there are any thoughts /
> > previous work available.
>
> When that idea was originally thrown around, Chandler was very
> different. So this will basically have to start from zero. Fortunately I
> think there is something that we could model this after.
>
> The Eclipse project has a plugin called Mylyn, which includes Bugzilla
> connector. In Mylyn, you can create and edit bugs through its UI, make
> queries, and set a bug as an active task. The last is a really cool
> concept with Eclipse, because Mylyn can track what files you are editing
> to fix that bug and gradually hide stuff that is irrelevant to your
> current bug. This helps you focus to the task at hand, especially with
> large source trees.
>
> How would this mold a Bugzilla/some other issue tracker plugin for
> Chandler? I think the plugin should allow one to create queries for bugs
> and dump the results into the now, later or done section. I could
> imagine doing a query for all the bugs in Chandler milestone 0.7.3 and
> showing them in now section. I'd mark all but the one I was working
> right then as later. After I'd fixed a bug I could perhaps change the
> current bug to done, which would automatically close the bug as fixed.
> There are obviously a lot of questions that would need to be answered
> about this design, but it seems like it would be possible and Mylyn has
> showed that it is also useful.
>
> --
>   Heikki Toivonen
>
>
>
> _______________________________________________
> chandler-users mailing list
> chandler-users at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/chandler-users
>
>
>