[Development] These weeks in Oslo

Atlant Schmidt aschmidt at dekaresearch.com
Mon Mar 19 13:11:58 CET 2012


Frederik:

> We didn't have this email in a while and I don't know how
> regular we get around to sending it, but it might be
> interesting. If everyone here thinks it's spam, we'll stop ;)

  I support your sending of this mail.

  I think it will be valuable in keeping everyone
  aware of:

    1. Who is working on what

    2. What's not getting worked on

  And, IMNSHO, most importantly...

    3. That the work that's done on Qt is done by
       real live human beings with names. That is,
       this sort of E-mail will help foster good
       feelings of amity among the very-extended
       Qt team.


  And anyone who doesn't want to get the E-mail can
  easily devise a routing rule to send it to a
  "Meaningless and unnecessary_for_me mammal-bumps"
  folder. ;-)

                         Atlant

-----Original Message-----
From: development-bounces+aschmidt=dekaresearch.com at qt-project.org [mailto:development-bounces+aschmidt=dekaresearch.com at qt-project.org] On Behalf Of Frederik Gladhorn
Sent: Friday, March 16, 2012 09:28
To: development at qt-project.org
Subject: [Development] These weeks in Oslo

Hi,

we used to have a weekly email internally that would be a random collection of
what people did the last week. "This week in Oslo".

We didn't have this email in a while and I don't know how regular we get
around to sending it, but it might be interesting. If everyone here thinks
it's spam, we'll stop ;)

So this list is a) incomplete b) total random in that it contains people I ran
into c) not 100% serious.
You have been warned.

Greetings
Frederik


Shawn: playing with mouse area and touch events
Adriano: looked at memory consumption in QML
Jedrzej: changing Qt MetaType around
Kent: unbreaking CI because of changes in qtbase affecting qtdeclarative
Leonard: add debugging info to QThread
Arnab: documentation module fixes for QtXmlPatterns
Nico: document Qt JsonDb
Casper: modularize docs, move qdoc into qtbase, work on enabling qdoc to run
on just a directory
Martin S: update dita-xml generation in qdoc
Jiang: look at how to do a shared glyph cache in raster paint engine
Eirik: regression testing of qt scene graph rendering
Christian: distribute Fishermen's Friends to developers
Paul: direct rendering in qt compositor
Sergio: autotests block for windows build of qt 5 again; gerrit update soon so
you get less duplicate mail (on merges for ex); debating enabling of topic
branches again
Eskil: platform enablers for a shared glyph cache
Samuel: autotests for qt wayland (the first ones)
Jørgen: client side window deocrations for qt wayland plugin (currently in a
gitorious branch)
Joan: reduce memory consumption of distance field glyph cache
Denis: JsonDb optimizations and looking at alternative storage solutions
Martin P: fixed some network bugs
Ali: JsonDb B-Tree storage mechanisms, space optimizations
Carlos: removing transactionless cursors from JsonDb and more generally
prototyping storage solutions
Brad: broke and fixed qt; rocking the cocoa plugin, especially printing and
keyboard shortcut fixes
Morten: also rocking cocoa plugin, got creator with qt5 running on mac
(somewhat)
João: fixed Lars' qmap patch and then approved it
Pierre: fiddling with raw fonts in webkit and almost done with it
Benedikte: team building day in Oslo and recruiting developers
Jocelyn: fixed stuff in webkit
Andras: make webview flickable and fight touch vs. mouse issues
Tor Arne: webkit with qt5 improvements
Zeno: fixes to get qt webkit running on mac again and again, looking at
texture mapper not working
Jan Arve: got IAccessible2 work merged into qtbase
Frederik: improve and test accessibility events to update the at-client




_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


 Click https://www.mailcontrol.com/sr/3NLtOcXBvI7TndxI!oX7Uj80y4Ou3Kxpb2WnxOyD9E4MAbIKf03NNDFna1ELrUyQFlJxfAfjpXqz5oFEicUPXg==  to report this email as spam.

This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.



More information about the Development mailing list