Excellent summary. Thanks Max.
I finished implementing the highlighting feature. So when you receive a
message from a user other than the one you are currently chatting with, that
(other) user is highlighted.
I am currently making myself familiar with Launchpad and Bazaar. I will post
the code for review within next couple of days.
Before I push my code, I found that I had to replace all the occurrences of
QSLOT with QSLOTS anf QSIGNAL with QSIGNALS: to compile the source. Did
anyone else have to do this? I am running Qt 4.4 on Debian Linux. Do I need
to change anything on my end?
Thanks
Naveen
On Sat, Jun 12, 2010 at 10:57 AM, Max Bossino <m...@miragroupware.org> wrote:
> Hi all,
>
> Thursday's meeting was attended by Naveen, Neeraj, Shilpa and myself. You
> can find a transcript of the meeting here:
>
> http://miragroupware.org/wiki/doku.php/development/communication/archives/100610_weekly
>
> I shall address the topics in the order in which they were discussed.
>
> Shilpa is going to start working on the Notes Utility next week. Through
> our discussion, we proposed a provisional design for the Notes Utility which
> would allow it to support both synchronisation and conflict handling. This
> is how it would work:
> Every note would be referenced by a unique ID, which the user isn't aware
> of and which is set by the Server the first time a note is pushed. Every
> note would also contain other metadata *set by the Server*, including the
> last user to edit it and the time it was last pushed to the Server (either
> the first time or in a subsequent edit).
> Let's pretend that I am online, and I create a note with the title 'My
> Brilliant Note', for which the Server sets an ID of 'xn10'. This new note is
> pushed to all Members of the Workplace.
> I then go offline. While offline, I edit the content of the note 'My
> Brilliant Note' and Save it locally (i.e. confirm my amendments to the
> note). Meanwhile, Shilpa is online and she changes the content of 'My
> Brilliant Note' and Saves it (i.e. confirms and uploads her changes to the
> Server).
> When I go back online, the Notes Utility pushes my change to the Server.
> The Server compares the metadata of my uploaded note with ID 'xn10' to the
> Server's version of the same note, and discovers that the Server's version
> is newer - i.e. another Members has edited that note while I have been
> offline. The Server returns an error to my Client prompting me to either
> 'Discard My Changes', or 'Save As A New Note'. If I discard my changes, my
> local version of the note is dropped and the Server's copy is downloaded. If
> I choose to save as a new note, my note is uploaded and given a new
> reference, such as 'xn11', automatically by the Server. The Server might
> also allow me to set a different name for this new note, such as 'My
> Outstanding Note', but this should be an option rather than a requirement
> (i.e. I don't think note titles should be exclusive).
> Shilpa is going to consider this design in more detail and try to improve
> it, or propose an alternative. In the meantime, I would like to flesh it out
> as a blueprint, which could then be changed to suit her proposal.
>
> Neeraj is going to work on encrypting the authentication mechanism,
> commencing after the 17th June. This will be carried out in two stages. The
> first stage will involve encrypting it using a three-way handshake, as
> proposed below:
> “A three-way handshake is proposed. First, the Client sends the username to
> the Server. The Server replies to the Client with the unique salt used for
> that username. The Client then replies with the password (encrypted using
> the salt).” The unique salt used for that username would, of course, be
> created by the Server when the user is created (and stored on the Server by
> the Directory layer).
> The second stage will involve using a global salt hard-coded in both the
> Client and Server to encrypt the unique salt sent by the Server to the
> Client, to provide an extra layer of security. I am going to raise a comment
> about this in a new mailing list thread, shortly.
>
> Naveen would also like to work on a task for 0.2. He suggested working on
> offline messages for the Chat widget (i.e. message queueing, where a message
> sent to an offline user would be delivered to the user when they return
> online). I thought that Shilpa had already implemented support for this, so
> Naveen is going to look into it. If message queueing is already supported,
> he will work on implementing highlighting in the Contacts widget instead, so
> that whenever a message is received from a contact that contact's name is
> highlighted automatically until it is manually clicked on by the user.
>
> We set our next weekly meeting for Thursday 17th June at 23:00 UTC. I
> encouraged everyone to please send a message to the mailing list whenever
> any progress is made - e.g. you start working on a task, make significant
> headway with it, request that your code be reviewed, etc. The more
> communication we maintain, the better!
>
> Regards,
>
> Max Bossino
> Project Manager
> http://miragroupware.org
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Mira-development mailing list
> Mira-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mira-development
>
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Mira-development mailing list
Mira-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mira-development
