Re: [Gajim-devel] meeting sum up
Dne 26.10.2009 23:47, Yann Leboulanger napsal(a): > * statusicon > missing things: rich tooltip, tooltips on the fly, middle click, and > animations If we have any code to do it (especially but not limited to Python bindings) we are very much encouraged to send it to the Gtk folks (#gtk+ on irc.gnome.org or www.gtk.org). Matěj -- http://www.ceplovi.cz/matej/, Jabber: mceplceplovi.cz GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC To err is human, to purr feline. ___ Gajim-devel mailing list Gajim-devel@gajim.org http://lists.gajim.org/cgi-bin/listinfo/gajim-devel
Re: [Gajim-devel] meeting sum up
On Mon, Oct 26, 2009 at 23:47, Yann Leboulanger wrote: > * branching policy > for contributions: 3_word_descrip-num where num == ticket_id Maybe num-3_word_description would be more 'visual search' friendly? I was about to say that yesterday, but I must have switched to another thread in discussion too fast. -- vArDo ___ Gajim-devel mailing list Gajim-devel@gajim.org http://lists.gajim.org/cgi-bin/listinfo/gajim-devel
[Gajim-devel] meeting sum up
Here is a small sum up of the meeting we did this evening in gajim room. * merge plugin systen after 0.13 release, we'll need to add a lot of entry point, and plugin developpers will be able to tell us where they need them. * dependent software version requirements we can depend on gtk2.16 / pygtk2.18 if needed (for gtk.statusicon for example) * what to do for 0.13,0.14,0.15 0.13: finish current tickets 0.14: at least a first version of plugin system, and begining of refactoring work 0.15: a stable plugin API? * branching policy for contributions: 3_word_descrip-num where num == ticket_id * refactoring this will happen slowly when writing new features, using GED from plugin system. Ever dev is welcome to help in this directory and test things. * gtkbuilder switching to it will remove libglade dep, and allow us to design treestore and columns out of the code. Start conversion with simple dialogs after 0.13 release * convert to bitbucket There is no real need of that, and will preven us to do some automatic tests before commits. * statusicon missing things: rich tooltip, tooltips on the fly, middle click, and animations * coding standards we'll switch to 4 spaces indentation. I'll announce it in devel mailing list before doing it so that everyone can upgrade they changes. Thanks to all participants, and see you soon for the next meeting! ___ Gajim-devel mailing list Gajim-devel@gajim.org http://lists.gajim.org/cgi-bin/listinfo/gajim-devel ___ Gajim-devel mailing list Gajim-devel@gajim.org http://lists.gajim.org/cgi-bin/listinfo/gajim-devel
[Gajim-devel] meeting sum up
Here is a small sum up of the meeting we did this evening in gajim room. * merge plugin systen after 0.13 release, we'll need to add a lot of entry point, and plugin developpers will be able to tell us where they need them. * dependent software version requirements we can depend on gtk2.16 / pygtk2.18 if needed (for gtk.statusicon for example) * what to do for 0.13,0.14,0.15 0.13: finish current tickets 0.14: at least a first version of plugin system, and begining of refactoring work 0.15: a stable plugin API? * branching policy for contributions: 3_word_descrip-num where num == ticket_id * refactoring this will happen slowly when writing new features, using GED from plugin system. Ever dev is welcome to help in this directory and test things. * gtkbuilder switching to it will remove libglade dep, and allow us to design treestore and columns out of the code. Start conversion with simple dialogs after 0.13 release * convert to bitbucket There is no real need of that, and will preven us to do some automatic tests before commits. * statusicon missing things: rich tooltip, tooltips on the fly, middle click, and animations * coding standards we'll switch to 4 spaces indentation. I'll announce it in devel mailing list before doing it so that everyone can upgrade they changes. Thanks to all participants, and see you soon for the next meeting! ___ Gajim-devel mailing list Gajim-devel@gajim.org http://lists.gajim.org/cgi-bin/listinfo/gajim-devel
