Re: [Licq-devel] Migrating trac tickets [help needed]

>> ##### Group 3 - Possibly bugs #####
> In general, I think we should only migrate bug reports with clear and
> understandable descriptions. If we can't understand the report or
> reproduce the problem it will probably never get fixed. In this case I
> think less is more. If we miss to migrate a bug report for a real bug,
> someone else will discover it and report it in which case we'll get a
> report from someone that hopefully is interested in helping us solve
> it.
Yes, I agree, and this should reduce the list a bit.

>> 384 [icq] GUI popup sometimes show idle time larger than logged in time
>>         =>  Haven't seen this in a while so not sure if it's still a bug
> Seems minor and if you haven't seen it maybe we can leave it.
Some of our timestamps are provided by the server and some are tracked 
locally and depend on when we logged in etc so I think we can assume 
this is the reason for the confusion and move this to the forget-it-list.

>> 556 [daemon] Group handing is strange due to merging of local and server
>> lists
>>         =>  We don't know if a mismatch is due to local or server change, also
>> there are different opinions
> Perhaps skip this until someone new reports it as an issue?
The only solution I can think of would require Licq to keep a log of all 
changes and use that to figure out if a change was local or from the 
server (i.e. another client) and merge based on that. To me this sounds 
complicated and is either a low-prio enhancement or skip it. My vote is 
to forget it and just accept it as a limitation when using multiple 
client/instances for the same account.

>> 559 [icq] Licq shows IP when ip hiding is enabled
>>         =>  Workaround in ticket that I'm guessing is a hack
> I vaguely remember something about IP hiding being removed from the
> ICQ protocol? If so we should skip this as well.
Ok, the ticket isn't very detailed anyway

>> 597b [gui] Top chat pane is not updated when encoding is changed
>>         =>  Not sure if this shold be considered a bug or working as intended
>
> When uncertain leave it out.
If a user changes encoding it doesn't mean it should apply to previous 
messages, so I'll just drop this one.

>> 675 [daemon] Licq adds all receivers to the list
> Don't know what this is, but it sounds like it could be a bug.
The complaint here is that spammers are added to list but I haven't seen 
same as messages in a long time now (just as authorization requests) so 
I'm guessing it's not as important any longer.
The description asks for a "Not in list" group which is something we 
already have so this might be possible to close as fixed depending on 
how you read it.

>> 741 [icq] Checking if a user is invisible doesn't work
> From the title is sounds like something that once worked but that have
> since been fixed in the ICQ protocol (on the server side).
Yes, there is even a comment "The server has been fixed, so this feature 
no longer works." from Jon 2005-07-01 so I guess we can just drop it 
unless he can tell why he left it open.

>> 1461 [icq] Sending URL to multiple contacts is only sent to one recipient
> Similar to 844?
Maybe, but I'm not sure.
Anyway, I just fixed 1461 in 1.5-stable and I can't reproduce 844 so 
these are no longer an issue.

 >> 1646 [icq] Update all users floods the server
I just tested this and it's verified. With my 150+ contacts the server 
disconnected me when I requested meta information for all of them at the 
same time. So this one moves to the list of confirmed bugs.

>> 1722 [jabber] Typing notification received when sending to offline contact
> I wrote this one right? If so, skip it. I think I concluded that it
> was something strange with the server.
Ok, moved to drop list

>> ##### Group 4 - Realistic enhancements #####
>> I consider these enhancements doable without major changes
>
>> 1363 [daemon] Create the plugin pipeline architecture
>>         =>  Not sure what this means. Task created by Erik
> This was when Licq 2.0 was the next big thing. Can be skipped now.
Ok, gone.


Apart from the ones discussed above, the rest of the tickets in group 3 
needs to be tested by someone who can reproduce the fault otherwise I'll 
probably just drop them. I thinking maybe asking on licq-users before 
dropping them though if noone can help me here...

There are also a few where Jon or Eugene have been involved, if you two 
are reading this feel free to comment on the following:

1428 [icq] Invalid login sequence being performed
     => Reported by Jon but not sure what it's referring to.

1445 [icq] Licq does not receive messages from icq 5.1
     => Long discussion with several patches from Jon and it looks like 
it got partially better (messages working but not file transfers). Did 
these patches get committed or did they just exist as attachments to 
this ticket?

1530 [icq] Server side contactlist damaged after moving users between groups
     => Confirmed as a known problem / Eugene 2007-08-16
     => Cause of problem probably found and will fix them next / Jon 
2008-04-21

1573 [icq] Charsets conversion problem
     => Several updates by author and Eugene but no solution

1592 [icq] Inspect why info requests between AIM owner and ICQ contact 
are not answered by the server
     => Task created by Eugene but no details on what requests it's 
referring to