Sunday, May 10, 2009

Release schedule (sort of)

some people are asking when the first alpha/beta/something will be, to answer those questions I made this post.

The idea of the first "something" officially for emesene 2 will be when I get to the following milestone:

"emesene 2 is everything I want except P2P"

what that means?

that the first public bundle to test will be made when I have emesene feature complete excluding P2P (custom emoticons, file send/receive, webcam and inks). When that release is made I will receive bug reports on some place (trac is really not used right now, at least by me), I will work to fix all the problems that appear on that release, then I will make a new release when I think that all major bugs are removed, I will make a new cycle fixing bugs.
When those two cycles are finished we should have something like:

"emesene 2 is everything people want except P2P and it's stable"

then if dx is still not working on P2P (*looks at dx*) I will start to work on that, the features will be added in this order:
  • display pictures
  • custom emoticons
  • file send/receive
then I will make a release to test those implementations and fix bugs. After fixing the bugs the first release of emesene 2 will be made, a next cycle of bugfixing will be made and after that we will start to work on webcam.

why webcam at the end?

because webcam is unstable, it breaks, different distributions/operative systems handle webcam in a different ways, it breaks, it needs to compile/have a shared library, it breaks... did I said it breaks? ;)

dates for that milestones?

No idea, pretty busy right now trying to finish my engineer career and working, but I really want to get to the first milestone fast. Right now the things missing are

  • display emoticons on userlist/labels
  • plugin preference dialog
  • finish emoticon handling on conversation input
  • theme handling on preferences
  • finish the information view for logs
if you want to test earlier, you can checkout from tne subversion repository :)

15 comments:

Fabio said...

Thanks Mariano, 2 questions:
1) emesene 2 will be backward compatible with emesene1 log database? (and maybe avatar history?)
and what other preferences can import?

2) emesene 2 will take the layout of emesene 1 in the contact list?

i mean:
coloumn1) avatar/status
coloumn2) nickname
coloumn3) personal message

(ps: p.m. can be placed in another row)

brunitom said...

THAAAAAAAAAAAANK
GRACIAAAAAAAAAAS

Cyanotic said...

Uhm... :'(
I think that till you don't write P2P no-one will use emesene2.
The fastest way to see emesene2 "complete" is to host the source in BZR or GIT (or similar) so while you're working on everything (except p2p) someone will work on P2P and, if it's cool enough, you can integrate it with your version.
In this way:
1) You can continue with your real life :D
2) You will have less work to do on emesene ;)

The Crazy version is not so bad...it means that the community is doing a "good" work (ok, it's true the code structure is a real sh**t)!

Cyanotic said...

Uh I forgot...PLEASE look @ farsight2 WHEN you'll write webcam support!

juancarlospaco said...

Por que es tan dificil Webcam ???
Hacer streaming de Audio es tan facil...

Con buena onda lo digo eh,
no es a modo de critica al contrario,
te felicito por el trabajo!!!,

Pero no se puede "mandar" el streming
de video por fuera del protocolo de MSN ?
para que, aunque sea sea estable a lo
largo del tiempo entre emesene<--->emesene
Se me ocurre usando programas como Bashare (P2P en Python) y Sockso (Streaming Server)

que se yo, se supone que inclusive si tenemos el lado "Server" deberia poderse usar videoconferencia,
LibJingle no sirve para esto?
http://code.google.com/intl/es-AR/apis/talk/libjingle/index.html

salu2

Folken said...

No se si ya se dijo esto pero, hay la posibilidad de que exista la opcion de bloquear no solo usuario, sino por grupo o algo asi?

Por cierto gran trabajo el que haces, me encanta Emesene, un Mazinger sin complicaciones y cosas de mas.

Adrián Solamente said...

sin apuro capo ;-)

Unknown said...

Have you thought about using Google Code? Every project hosted there has it's own subversion repository and they have a really nice system to track issues/bugs.

Anonymous said...

@dxdx

http://code.google.com/p/msnp-sharp/wiki/KB_MSNC12_BinaryHeader

Anonymous said...

asdman said:

FUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU
CKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK
TTTTTTTTTTTTTTCCCCCCCCHHHHHHHHHHHH

open cmd and write: format c:

PD: (on Güindows)

dx said...

@anon: Thanks for that

Vincenzo said...

Please don't forget chat while appear offline!!! And block group feature!!!

Stéphane said...

Hi Mariano. I think it would be nice to host the project on Launchpad. Would make bug triaging much more easier for everybody. Opinion ?

juancarlospaco said...

Mariano mirate esto si tenes tiempo:
http://fonomo.com

Videoconferencia basada en Web y Free.

Anonymous said...

Por favor ten en cuenta hacer una herramienta para hacer backups a los emoticonos :D =) (alguna forma de guardar las imágenes con un archivo xml para las preferencias)