Deployment Team/Meetings/2008-09-24/Log


 *   I realize we didn't publicize the deployment meeting


 * nteon has quit (Read error: 104 (Connection reset by peer))
 * nteon (n=nteon@cpe-74-79-168-197.twcny.res.rr.com) has joined #sugar-meeting
 * aa has quit (Read error: 110 (Connection timed out))
 * dirakx (n=rafael@190.156.125.94) has joined #sugar-meeting
 *   hey rafael
 *   I don't think we did a good job of reminding people of this meeting.
 *   walter: hi..
 *   yes i think is better to do it next week?


 * nteon has quit
 *   walter: i mean in order to get more people involved.
 *   Yes. Next Wednesday, same time?
 *   yep..


 * erikos (n=erikos@e178217046.adsl.alicedsl.de) has joined #sugar-meeting
 *   I'll try to remember to advertise on the weekend Digest
 *   hey Simon
 *   walter i'll also write an emailk about it..
 *   walter: hey - do we have a meeting today?
 *   we were just discussing this. We didn't get the word out, so we don't have a quorum.
 *   we'll postpone until next week.
 *   oh ok, would it have been deployments one?
 *   erikos: yep
 *   aha ok
 *   i think it's better, we are just starting to get things together ;)
 *   Meanwhile, I am in the midst of writing a grant proposal... for outreach, including some needed engineering...
 *   nice
 *   walter: in the same page we are using for that?
 *   dirakx: I don't understand the question
 *   walter: doh i misunderstood, that sorry
 *   Well, I am going to get back to writing. I think I need to really focus on getting lots of applications in play ASAP.
 *   let the paper flow!
 *   One question on the application I am writing now is about any images or multimedia we might have.
 *   I wonder if the video we put together for the MOMA exhibit would work.
 *   I'll have to ask Eben.
 *   Any other thoughts?
 *   walter: he's in #sugar now
 *   other than what is in the wiki and manuals, no
 *   Also, another idea I had that is related to deployment: Sugar Labs has no human face...
 *   what if we make a page which is a matrix of faces: developers, teachers, children
 *   we can ask everyone to upload pictures
 *   I guess the silence is an indication that there isn't much interest in the idea
 *   that gets me to another idea of having something like about sugar with the names and faces? of all the devs and others..
 *   something to give it a human side
 *   i like the idea ;). though i dont now about the others..
 *   now/know.
 *   I'll float it this weekend.
 *   walter: sounds good to me
 *   yup
 *   should we just make a "galley" in the wiki?
 *   ^galley^gallery
 *   walter: i am ok as well to upload my face ;p
 *   walter are you thnking in something like the Community/profiles page on wiki.laptop.org ?
 *   http://wiki.laptop.org/go/Profiles
 *   great
 *   but maybe simpler
 *   Just a picture...
 *   and a link to a User page if there is one
 *   Wanna sketch it out on Sugar Labs?
 *   yep why not..
 *   Think we could get kids and teachers to post?
 *   i could send an email to Sur asking, we will see how it goes ;).
 *   Let'
 *   s prepare the page first
 *   I guess some teachers from uy will be favorable
 *   so they have somewhere to go
 *   although they are just starting to participate
 *   tomeu: yes.
 *   some suggesiotns about how the page should be named?
 *   profiles is fine... just something more simple than the OLPC version
 *   ok
 *   thanks.
 *   tomeu: will you wear a black or a red shirt?
 *   hmm, not sure
 *   I guess it depends on which one is in the washing machine :p
 *   :p
 *   some of the pictures at olpc site are a bit scary - hope we don't scare people away
 *   maybe everyone should draw an animal, instead :)
 *   For those who have customized their Sugar icon, maybe they could include that?
 *   Speaking of which, I need to write up a ticket for making the user icon a separate file from the xo icon.
 *   oh yeah - heard that changing the sugar icon is on vogue
 *   I documented it in Modifying Sugar in the Sugar manual...
 *   but OLPC didn't include that chapter in the Help manual
 *   But the granularity of control is not quite correct
 *   MyIcon.py lets you modify the homeview, but not your icon in any other view
 *   oh, the manual in the help activity does only include a portion
 *   erikos: i agree some pictures in those profiles are too geeky even for me taste ;).
 *   computer-xo.svg modifies it everywhere, including places it shouldn't
 *   yeah modifying the computer-xo icon is not the right way
 *   that was the method advertised in OLPCNews a few months ago.
 *   we once had early code for that
 *   since you would ideally send the image as well around when
 *   to appear on the other's mesh view
 *   but this would need quite some effort, actually - to make it happen
 *   sorry: I had to step away for a phone call.
 *   It could be staged: change it on your machine and then change it on the network...
 *   I had built a parametrized XO that with a few extra bytes let the XO change over the mesh...
 *   sure, it is true that you could stage the task
 *   how critical is it, i wonder?
 *   the first step would be to make a clear distinction between the xo-icon and my-icon in the codebase
 *   not critical...
 *   the journal is most important
 *   the first step would be to make a clear distinction between the xo-icon and my-icon in the codebase
 *   not critical...
 *   the journal is most important
 *   walter: do you have already an idea of what changes in the journal UI are most urgent?
 *   everybody seems to have a different idea each ;)
 *   @tomeu: the most important things in my mind are: robustness; easier access to journal items (e.g., access from the home page); and a better way of managing the data as it grows.
 *   Robustness is really the datastore
 *   I think the discussion about tags is a good way to address the management issues
 *   but I think the bulk of the journal "spam" as Albert likes to call it, comes from the fact that people don't access the Journal more directly--we need to make it an extension of the homepage.
 *   yeah, we see some consensus growing on that
 *   I think we definitely should get that one for 9.1
 *   I had some UI ideas that Eben/Pentagram never liked about making the journal a direct extension of the Frame
 *   0.84
 *   oh, haven't heard about it
 *   Just like the clipboard is always there, relevant journal entries could always be there
 *   some kind of "recent documents"?
 *   yeah.
 *   or recent objects, once you are in an activity
 *   Eben I think wanted to do this with a tray instead
 *   I'm not sure we'll have much time to do changes in the journal UI for 0.84
 *   so we should choose well what gives most for the price
 *   I don't expect that level of change, but I think the datastore ideas from last January could support this model
 *   for now, I think the tags stuff is too much for 0.84 unless someone volunteers to help
 *   When we think about what we optimize in terms of access...
 *   walter: yup, increasing query performance is one of the main goals of the rewrite
 *   we are already much better and can improve significantly
 *   more
 *   That's going to make a huge difference... the foundation has to be there first.
 *   That's going to make a huge difference... the foundation has to be there first.