[Gaim-e-developer] gaim-e roadmap

[<gai...@li...>]

I'd like to take this time to hash out ideas for where
gaim-e is, and where it is going.  Please send
feedback, this isn't set in stone, and we are open to
sugestions. 

My goal for v1.0.  
When I initially took over gaim-e I wanted to get it
to a stable place with enough functionality to make it
usefull to the masses.  Then, once we got to a
reasonably stable platform, my goal was to move onto
v2.0.  I wanted to make it usefull enough that most
normal users could use gaim-e with gaim and not have
problem after problem.  
That being said, I think we are close to v1.0.  It
will allow most users the ability to use gpg keys to
chat with other gaim users in the three most popular
protocols.  So, at this point I think that if we can
find the last of the random seg faults, I will be
happy.  Then gaim-e won't crash for most users. 

There are however users out there that will push
gaim-e to the extreme and find some errors in our
logic and programming.  Here are a couple that I can
think of:

1. If you are using multiple accounts into the same
protocol, and encrypt with one. Then switch to the
other, and you will attempt to send them encrypted
text.  Gaim-e doesn't check to see who set up the
conversation.  

2. If you are using multiple accounts in any of the
protocols.  If you log off of any of the protocols,
then gaim-e will start to do clean up functions.  IE,
it will destroy the icons, and turn off encryption. 
So if you have an encrypted chat going in TOC and you
log off of yahoo, I think it will turn off the
encryption and get rid of the config.  I don't think
it will crash gaim, but it does create a possible
vulnerable situation. 

3. There is a random bug that crashes gaim.  It
happens most of the time when no one is around and
using gaim-e.  Attempts are being made to find this
gremlin.  

4. Larger keys in TOC get truncated.  Nothing
happens.. The person that initiated things encryption
is on. the person receiving, doesn't get a passphrase
because the whole message isn't there. 

5. When using gaim-e and msn, we just strip out the
font shit at the beginning of messages.  So all of the
pretty colors go away. 

6. If someone has pretty font shit and they type /off
to turn off encryption, the other side doesn't turn
off encryption.  

There are probably many more that I've just forgotten
about.  But those are the ones on my mind right now. 
We will find the 3rd bug, and I might look into a way
to make the 2nd bug a little nicer.  At least put a
temp band-aid on the problem till v2.0 starts being
developed. 

Alright, now for my ideas that should be in v2.0

1. Be able to use multiple accounts, each can be
associated with it's own key if desired.  

2. Create keys for users on request.  

3. Send and retrieve keys from keyservers.  

4. Encrypted chat rooms. 

5. Encryption in irc/jabber, and better support for
msn. 


Stu has some ideas for v2.0 as well.  So I won't steal
his thunder.  Please send in feedback.
peace
w0d3n

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com