[Gossip-dev] Re: [Telepathy] Telepathy Status

[Mikael Hallendal]

Jimen Ching wrote:
> On Thu, 12 Oct 2006, Martyn Russell wrote:

>> What is the point in having a schedule if the work input is not
>> consistent enough to guarantee such a schedule could be kept to?
> 
> Having a schedule helps you track where you are and how far you have to 
> go.  A schedule is just a plan, a todo list, etc.  I'm pretty sure you 
> have such a schedule/plan/list.  It's probably only for the short term, 
> and isn't written down.  I'm merely suggesting such a list be created, so 
> everyone knows their part in reaching a goal.

I think what you are asking for is a roadmap and yes, having a long term
roadmap would be good. Having a defined set of goals would be even more
valuable and we are in the process of writing these down.

>From these goals it can be discussed whether Telepathy will help us
reach them or not.

>> are really basic and a necessity for Gossip) and there will be bugs. If
>> you consider that it might take 3 months for Telepathy to get to a place
>> where they support all the key features of Gossip now and that it would
>> be stable by then too, that leaves the Gossip team (of 2/3 people plus 2
>> volunteers) 3 months to implement all the backend, all multi protocol UI
>> updates and any fixes in between. This leaves no time for any testing
>> what so ever.
> 
> If you're trying to convince me that there are lots of work to be done, 
> you don't have to do that.  As I look through the code, I can see there 
> are work to be done.  But the qoute above seems to imply things need to be 
> done serially.  I.e. Telepathy needs to stabilize before work on Gossip 
> can begin.  I'm not sure this is true.  If work progress in parallel, 
> based on features, it should be possible to reach the same goal at the 
> same time.

What we are saying is that until Telepathy is "there" we will not
consider making a full jump to it. Things are already being done in
parallel by Eitan and Xavier.

> A few days spent on planning will save weeks of work that may prove to be 
> unnecessary.  I can only offer this advice.  But personal experience has 
> proven this statement to be true.  Please take some time to consider it.

Hmm.. I have no idea where you find the base for this kind of assumption
that we aren't planning. What you seem to miss to see is that we already
have a working client, for only Jabber, having Telepathy won't give us
anything (that I know of at least).

Yes, we do need to define our goals better, and to communicate those
better to the community. But please, you don't need to tell us the
importance of planning for software projects.

Best Regards,
  Mikael Hallendal

-- 
Imendio AB, http://www.imendio.com/