Re: [sugar] New joyride build 1971
Mikus Grinbergs wrote: Now have the 'Circle of Activities'. But Journal does not start automatically. [Did not have Journal on Joyride 1970, either.] What are the steps to start Journal manually ? Thanks, mikus The journal is placed in /usr/share/activities and expected in /usr/share/sugar/activities/ http://dev.laptop.org/git?p=sugar;a=commitdiff;h=6dff9a9ef6323c62f189e8234dd4da00a06ffd39 I think we have to adjust that in pilgrim, Dennis Scott? For a workaround just move the journal to /home/olpc/Activities Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] release infrastructure
On Thu, May 22, 2008 at 1:30 AM, Wade Brainerd [EMAIL PROTECTED] wrote:
Hi, I'm wondering if you guys could provide a publicly accessible area
on dev.laptop.org for releasing tar.bz2 and .xo files. It's pretty
cumbersome to upload files to the Wiki, and I'd rather not use private
hosting.
Also, is anyone working on a 'setup.py release' command? What would
it do? Something like the following steps would be useful to me:
1. Verify no uncommitted changes exist (git status returns non-zero).
2. Increment version in activity/activity.info.
3. setup.py dist
4. setup.py tarball (or tar cjvf Bundle-Version.tar.bz2 -T MANIFEST)
5. git commit activity/activity.info
6. git tag -a Bundle-Version -m 'Bundle-Version release'
7. git push --all --tags
7. scp Bundle-Version.{tar.xo} dev.laptop.org:/pub/releases/
Warnings should be shown for things like missing po, AUTHORS, NEWS, etc.
Any comments about what steps should/shouldn't be included?
And, this still leaves the developer to update the Wiki page, git push
and git push --tags.
setup.py release exists, and does some of the things you want. It
increments the version in activity.info, adds the release number at
the top of NEWS, does dist, commits and attempts a git push.
The rest of your list should be easy to add...
Morgan
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
Re: [sugar] New joyride build 1970
On Thu, May 22, 2008 at 1:24 AM, Mikus Grinbergs [EMAIL PROTECTED] wrote: Joyride 1970 has the OLD 'Frame', instead of the 'Circle of Activities' in the Home view. Please fix. An older sugar was built in koji for a bugfix release. By default this gets included in joyride, and requires manual intervention to override. Joyride 1971 has sugar reverted to the current version. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Log 7
Wade Brainerd wrote: http://www.wadeb.com/log-activity.tar.bz2 Do you have an account on crank? - then you should be able to upload to here: http://dev.laptop.org/pub/sugar/sources/ which translates to: dev.laptop.org:/var/www/sugar/sources/ This release fixes #6005, #6356, #6597, #6014, adds various GUI improvements. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar Please send a mail to devel-announce as well. http://wiki.sugarlabs.org/go/Release#Module_release Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Log 7
On Thu, May 22, 2008 at 10:04 AM, Simon Schampijer [EMAIL PROTECTED] wrote: Wade Brainerd wrote: http://www.wadeb.com/log-activity.tar.bz2 Do you have an account on crank? - then you should be able to upload to here: http://dev.laptop.org/pub/sugar/sources/ I uploaded it for you: http://dev.laptop.org/pub/sugar/sources/log-activity/log-activity-7.tar.bz2 For the next release we should provide space either on sugarlabs.org or laptop.org. Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Missing 0.81.1 tarballs
See: http://wiki.sugarlabs.org/go/Release#Module_release Please release your modules as soon as possible. We are missing: read-activity write-activity tamtam-activity pippy-activity etoys-activity Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Missing 0.81.1 tarballs
Hi, Read was announced here: http://lists.laptop.org/pipermail/sugar/2008-May/005939.html Regards, Tomeu On Thu, May 22, 2008 at 1:37 PM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: See: http://wiki.sugarlabs.org/go/Release#Module_release Please release your modules as soon as possible. We are missing: read-activity write-activity tamtam-activity pippy-activity etoys-activity Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] OLPC's bizarre behaviors
Thank you Martin for your insightful perspective. The teams' excellent work has produced such high expectations that they can easily run away and lead to temporary disappointments. Remember the alternatives, be encouraged, and keep up your best efforts. We applaud you all. On Thu, May 22, 2008 at 1:38 AM, Martin Langhoff [EMAIL PROTECTED] wrote: On Thu, May 22, 2008 at 1:53 PM, Kim Quirk [EMAIL PROTECTED] wrote: Lots of things that we do don't meet any normal expectations of a 'company'. Most people at OLPC will tell you we are not a 'company'. ... I have been trying to understand it, explain it, live with it , and improve it for a year now. What I think is going on is a unique and somewhat chaotic (perfect storm?) intersection of non-profit, open source, research lab cultures with the need to ship a real product. This is excellent analysis. And I'd go a bit further than Kim actually in saying that I don't feel particularly bad that we are a bit of a mess. Being a bit of a mess means that we are breaking new ground so quickly that the ground is changing faster than the org gets used to it. Which leads to a few observations (which overlap somewhat with what Kim is saying) - IME, people complaining that we don't know what we are doing can be a positive indicator. The scenario outside the car is changing! - Learning to organise and handle new situation X is only worthwhile once we are confident that X is here to stay. - Therefore, there will be many situations that are impossible or not worth to be well prepared for. So being a constant mess is a reasonable approach. We can handle that by saying that strange new situations are common, and we have to keep an open mind and be ready to work w the team to get new and strange things done. - Prioritisation is important. Some things are too much of a distraction. Letting them go to hell can be less disruptive than an all-hands effort. This is - IME - the hardest part. When everyone is ready to take on whatever comes, it's hard to avoid getting the team distracted. Which can also be stated in more blunt terms: We are doing development of new stuff! If you want it predictable and organised, I hear EDS is hiring - the processes and procedures manual is 800 pages :-/ All of the above is from my experience in various organisations large and small, and govt and private. We are radically diffrerent from a big corp, and even from established non-profits. In this space you can expect us to be very good at a couple of very specific things, and a complete mess about a lot of other stuff. We will have to get good at some of that other stuff... in the meantime it'll be frustrating. :-/ There's a good book about this - Waltzing with Bears by either DeMarco or Yourdon, that says basically: if you are considering a project that doesn't take you into uncharted territory, *can it*. It's not worth it if it's not so new that you feel lost and helpless. It's written for big corps that are frozen in terror ;-) but it applies to what we are doing @ OLPC. Uncharted territory. So everytime we spot something in the horizon there's some fear that the earth might actually be flat. http://imagecache2.allposters.com/images/pic/EUR/2400-0070~Sailboat-and-Waterfall-at-Earth-s-End-Posters.jpg but I think we should keep sailing no matter what. m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [PATCH] Implement installation dates in the activity list
Not introduced by your patch but worth fixing: journal/misc.py: E0602: 92:get_date: Undefined variable '_' Nitpicks: 79chars: date = hippo.CanvasText(text=util.timestamp_to_elapsed_string(timestamp)\ a pity we have to re-import gettext as in util.py - but don't know how to do otherwise. def ngettext(singular, plural, n): pass - pylint complaints for that not being on one line r+ with these changes, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Missing 0.81.1 tarballs
On Thu, 2008-05-22 at 13:37 +0200, Marco Pesenti Gritti wrote: See: http://wiki.sugarlabs.org/go/Release#Module_release Please release your modules as soon as possible. We are missing: write-activity Working on it. I hope to have it ready before this weekend. Marc ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Missing 0.81.1 tarballs
On 22.05.2008, at 18:14, Bert Freudenberg wrote: I uploaded tarballs for etoys and etoys-activity: http://dev.laptop.org/pub/sugar/sources/ But the mail to [EMAIL PROTECTED] bounced: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 5.1.2 Host not found (not in DNS)) Reporting-MTA: DNS; klopstock Received-From-MTA: DNS; p50996fc3.dip0.t-ipconnect.de Arrival-Date: Thu, 22 May 2008 18:12:39 +0200 (MEST) Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.1.2 Diagnostic-Code: SMTP; 550 5.1.2 Host not found (not in DNS) Last-Attempt-Date: Thu, 22 May 2008 18:12:41 +0200 (MEST) Final-Log-ID: x033a6k4MC95PS.ee63d728 - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Test cases
Hello, To land 0.81.1, which is largely about the redesign, we will need someone to write down test cases for each feature in the redesign. Eben we thought you could perhaps help out with it, so that can keep focusing on the code. What do you think? Here is a quick proposal on how to handle test cases for the next versions. It will never be mandatory for any module (each maintainer is responsible to negotiate with Michael in the ways he consider more useful), but I'd like to try it out with glucose and a few activities. From: http://wiki.sugarlabs.org/go/TestCases To land new versions of glucose and new activities in the OLPC builds we need to: * Provide test cases for each new feature or bug fix. * Find testers to execute the test cases. A way to handle it in a distributed way and ensure it's done consistently is: * Ensure that every fix or new feature is associate to a trac ticket and that the git log for each of the related commits contain a reference to the bug. * Before closing the ticket make sure that it contains a comment with the test case (mark it by inserting a keyword in the text so that it can be extracted automatically. * When releasing a module, use a script to automatically generate the NEWS from the ticket references in the git log and the test cases (git log - ticket - test case). Put both in the release announcement. * Decide which modules to land together. Get the test cases from the release announcement and create a page in the wiki. Ask volunteers to execute them and report the problems they find. * Negotiate with the release manager on the base of the testing data. Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Missing 0.81.1 tarballs
Doh! Bernie? Marco On Thu, May 22, 2008 at 6:25 PM, Bert Freudenberg [EMAIL PROTECTED] wrote: On 22.05.2008, at 18:14, Bert Freudenberg wrote: I uploaded tarballs for etoys and etoys-activity: http://dev.laptop.org/pub/sugar/sources/ But the mail to [EMAIL PROTECTED] bounced: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 5.1.2 Host not found (not in DNS)) Reporting-MTA: DNS; klopstock Received-From-MTA: DNS; p50996fc3.dip0.t-ipconnect.de Arrival-Date: Thu, 22 May 2008 18:12:39 +0200 (MEST) Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.1.2 Diagnostic-Code: SMTP; 550 5.1.2 Host not found (not in DNS) Last-Attempt-Date: Thu, 22 May 2008 18:12:41 +0200 (MEST) Final-Log-ID: x033a6k4MC95PS.ee63d728 - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Log 7
Cool, thanks guys. On Thu, May 22, 2008 at 1:49 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: On Thu, May 22, 2008 at 10:04 AM, Simon Schampijer [EMAIL PROTECTED] wrote: Wade Brainerd wrote: http://www.wadeb.com/log-activity.tar.bz2 Do you have an account on crank? - then you should be able to upload to here: http://dev.laptop.org/pub/sugar/sources/ I uploaded it for you: http://dev.laptop.org/pub/sugar/sources/log-activity/log-activity-7.tar.bz2 For the next release we should provide space either on sugarlabs.org or laptop.org. Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Missing 0.81.1 tarballs
Host not found? Not in DNS? That's weird. It might have to do with the fact that lists.sugarlabs.org is actually a CNAME, and we do not have MX records. This is incorrect according to RFCs, but I had never seen an MTA complaining. Here, I updated the zone. Bert, please try again. Marco Pesenti Gritti wrote: Doh! Bernie? Marco On Thu, May 22, 2008 at 6:25 PM, Bert Freudenberg [EMAIL PROTECTED] wrote: On 22.05.2008, at 18:14, Bert Freudenberg wrote: I uploaded tarballs for etoys and etoys-activity: http://dev.laptop.org/pub/sugar/sources/ But the mail to [EMAIL PROTECTED] bounced: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 5.1.2 Host not found (not in DNS)) Reporting-MTA: DNS; klopstock Received-From-MTA: DNS; p50996fc3.dip0.t-ipconnect.de Arrival-Date: Thu, 22 May 2008 18:12:39 +0200 (MEST) Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.1.2 Diagnostic-Code: SMTP; 550 5.1.2 Host not found (not in DNS) Last-Attempt-Date: Thu, 22 May 2008 18:12:41 +0200 (MEST) Final-Log-ID: x033a6k4MC95PS.ee63d728 - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar -- \___/ _| X | Bernie Innocenti - http://www.codewiz.org/ \|_O_| It's an education project, not a laptop project! ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Missing 0.81.1 tarballs
Same error. Maybe it still needs to propagate? - Bert - On 22.05.2008, at 20:00, Bernie Innocenti wrote: Host not found? Not in DNS? That's weird. It might have to do with the fact that lists.sugarlabs.org is actually a CNAME, and we do not have MX records. This is incorrect according to RFCs, but I had never seen an MTA complaining. Here, I updated the zone. Bert, please try again. Marco Pesenti Gritti wrote: Doh! Bernie? Marco On Thu, May 22, 2008 at 6:25 PM, Bert Freudenberg [EMAIL PROTECTED] wrote: On 22.05.2008, at 18:14, Bert Freudenberg wrote: I uploaded tarballs for etoys and etoys-activity: http://dev.laptop.org/pub/sugar/sources/ But the mail to [EMAIL PROTECTED] bounced: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 5.1.2 Host not found (not in DNS)) Reporting-MTA: DNS; klopstock Received-From-MTA: DNS; p50996fc3.dip0.t-ipconnect.de Arrival-Date: Thu, 22 May 2008 18:12:39 +0200 (MEST) Final-Recipient: RFC822; [EMAIL PROTECTED] Action: failed Status: 5.1.2 Diagnostic-Code: SMTP; 550 5.1.2 Host not found (not in DNS) Last-Attempt-Date: Thu, 22 May 2008 18:12:41 +0200 (MEST) Final-Log-ID: x033a6k4MC95PS.ee63d728 - Bert - ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar -- \___/ _| X | Bernie Innocenti - http://www.codewiz.org/ \|_O_| It's an education project, not a laptop project! ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Test cases
On Thu, May 22, 2008 at 6:32 PM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: Hello, To land 0.81.1, which is largely about the redesign, we will need someone to write down test cases for each feature in the redesign. Eben we thought you could perhaps help out with it, so that can keep focusing on the code. What do you think? This is the kind of testcase we need: http://wiki.laptop.org/go/Tests/Mesh_view Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] OLPC's bizarre behaviors
I think it's worth noting that with the announcement of the new 2.0 spec on the hardware, you're going to get even more backlash of current G1G1 participants feeling like they helped to fund and purchase a system that is basically really a serious work in progress and test bed for the new system. Again, impression counts. Todd On Thu, May 22, 2008 at 9:25 AM, C. Scott Ananian [EMAIL PROTECTED] wrote: On 5/21/08, Kim Quirk [EMAIL PROTECTED] wrote: I have been trying to understand it, explain it, live with it , and improve it for a year now. What I think is going on is a unique and somewhat chaotic (perfect storm?) intersection of non-profit, open source, research lab cultures with the need to ship a real product. [...] Can we use help? Absolutely. Lots of it! The hardest thing for us to figure out is how to let people help us. OLPC is not so unique and special that we can't learn from our predecessors. OLPC is not the first research lab which morphed into a non-profit with a product. I'm sure others can contribute examples, but Firefox and Debian leap to mind. That said, I don't think that we can (or should) point our finger at any single person and say that we don't communicate as well as we could because of that scapegoat. Rather, I'd like to suggest that we point to a person who *doesn't yet exist*: a community liason. Fedora and Firefox both have (many!) designated 'ambassadors' whose job it is to keep the community in the loop. Debian has a 'Project Leader' with similar charge. I would like to nominate SJ and Adam for the role of interim community liason, as they've done a fantastic job to date building and nourishing their respective content and support communities. What we need is to broaden that task and embody and formally recognize it. A liason will be privy to inside information and continually ask is this public? can it be? and conversely, keep in touch with the broader community and bring to internal attention worthwhile efforts outside. By naming and recognizing a liason (even an interim one), we would all have a single point of contact: cc '[EMAIL PROTECTED]' to ensure broad distribution. This job is likely to be a bit overwhelming, and I suggest actively seeking to hire proven community builders who have worked with other projects to take the burden off our interim liason(s). Liasons should, of course, work with the community to build a broader base of OLPC ambassadors who can share the local work. Concrete things I'd like to see a liason take charge of: a) monthly tech mini-conferences to present current work and wild ideas b) the same for deployments, to exchange success stories, challenges, and curricula c) organizing local OLPC chapters, with their own charges, projects, focus. Providing resources to same: http://alabama.laptop.org could be a focus for OLPC volunteers in Alabama, for example. (See http://freesklyarov.org/local-howto.html for inspiration.) d) collecting and archiving talks and press releases for reference and to ensure broad distribution. (both 1cc-created content, and locally-created content) e) A more broadly-focused community news, agressively seeking out and incorporating local as well as offical OLPC content f) coordinating blogging efforts: a weekdaily blog post by a different OLPC developer each day, say. g) coordinating news releases to community sources like OLPCNews as well as traditional press sources. Providing access to traditional press for noteworthly community work. h) To some degree involving local communities with local i18n and support work for pilots and deployments. i) Hosting regular open houses, both at 1cc and at local OLPC groups. j) Faciliating travel to allow different groups to interact: having 1cc developers give talks at local OLPC groups and vice-versa. I'm sure folks here can contribute more ideas. Note that some of these tasks are made much easier if there is an OLPC employee involved, while others (c, d, e, h) are good task which interested members of the community can take the lead on w/o waiting for us. In fact, if there are passionate community members, I'd suggest viewing the entire list as within your scope: I think that OLPC employees are very amenable to badgering by the community if (for example) someone has set up a mini-conference elsewhere and wants to get someone from 1cc to attend. --scott ps. Since I personally have a technology focus, I can suggest several interesting 'research projects' I'd love to see a local group really take charge of. Some ideas: care nourishment of the Debian/Ubuntu/Fedora packaging of Sugar; maintaining a Sugar live cd and/or maintaining a one-click-install Windows emulator of Sugar for groups interesting in exploring Sugar or teacher training; a research fork investigating gestures for Sugar; a research group to tackle the best approaches for emulating keyboards
Re: [sugar] [IAEP] OLPC's bizarre behaviors
C. Scott Ananian wrote: I would like to nominate SJ and Adam for the role of interim community liason, as they've done a fantastic job to date building and nourishing their respective content and support communities. SJ and Adam did a great job in the past to leverage and organize the community around OLPC, so I think they'd be perfect fits for this job. However, it seems most of the communication work needs to be directed *within* OLPC rather than towards its discontent community. Folks were alienated for a number of reasons, most very easy to grasp even without holding a degree in community building. One might consider reviewing some of the abundant criticism published in the open by people including Greg, RMS, Wayan, Ivan and Mako. And maybe pick some of their advice. A very important first step in the right direction would be suppressing all those secret mailing lists and bring most of the communication back on [EMAIL PROTECTED] Yes, there might be a small amount of confidentiality even within an open source charity. The same kind of things mommy and daddy would keep secret for the good of the family. Transparency is an *essential* precondition for regaining the trust of donors, volunteers and all plenty of other idealistic people who believe in reinventing education. Is there a better argument for secrecy besides our new business partners demand us to keep all our agreements secret? Restoring transparency would be just the first step, but an important step. Concrete things I'd like to see a liason take charge of: a) monthly tech mini-conferences to present current work and wild ideas b) the same for deployments, to exchange success stories, challenges, and curricula a) [...] d) Good ideas. e) A more broadly-focused community news, agressively seeking out and incorporating local as well as offical OLPC content Restoring the old weekly news posted to devel@ would be a good start. Perhaps even publishing the longer version that went by the name of below the line or something like that. f) [...] h) Very good ideas too. I'd like to stress, Scott, that your efforts towards improving communication are, as always, *very* welcome. -- \___/ _| X | Bernie Innocenti - http://www.codewiz.org/ \|_O_| It's an education project, not a laptop project! ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] OLPC's bizarre behaviors
On Thu, 22 May 2008 15:06:05 -0400 C. Scott Ananian [EMAIL PROTECTED] wrote: [...] pps. a little bird told me we've managed to ink deals with several more countries on the strength of our country meetings this week, which were 99% XO-1 related, even though we also used the opportunity to announce the XO-2. Don't imagine that we're not working on the XO-1. Rather, it's the XO-2 which is currently just an inkling of an idea. I nominate that little bird to be OLPC's new community liason! ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] OLPC's bizarre behaviors
Indeed, one of the goals of Sugar Labs is to help build community collaboration, so working together on organizing is a positive step forward. I plan to start sending a weekly Sugar Digest out--but it will not be comprehensive of all the OLPC comings and goings and it will include Sugar in other venues, e.g., apt-get sugar on Hardy. Feel free to forward Sugar-related news my way (Fridays if possible). -walter On Thu, May 22, 2008 at 4:16 PM, C. Scott Ananian [EMAIL PROTECTED] wrote: On 5/22/08, Bernie Innocenti [EMAIL PROTECTED] wrote: e) A more broadly-focused community news, agressively seeking out and incorporating local as well as offical OLPC content Restoring the old weekly news posted to devel@ would be a good start. Perhaps even publishing the longer version that went by the name of below the line or something like that. Below the line was never posted to [EMAIL PROTECTED] Community news continues to be published to the [EMAIL PROTECTED] list, which is open (as far as I know). I guess the only thing that's changed is that it is no longer cc'ed to [EMAIL PROTECTED] Should it be? ( http://lists.laptop.org/pipermail/community-news/2008-May/thread.html ) f) [...] h) Very good ideas too. It's worth noting explicitly that sugarlabs can step in and fill some of these needs as well. Arranging mini-conferences and local user groups, poking developers for regular blog posts, etc, etc. Mel Chua [EMAIL PROTECTED] is interning on grassroots building this summer, and you should certainly touch base work with her if you can. She's already roughly wiki-fied my original email at http://wiki.laptop.org/go/Community_liason . --scott -- ( http://cscott.net/ ) ___ Devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/devel ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] OLPC's bizarre behaviors
In total agreement, etc, here my 2 ¢ To avoid a plus ça change, plus c'est la même chose* kind of moment, could we have the naming of such an ombudsman be an open affair, not something done behind doors? To begin with, could we pinpoint _what_ we are looking in such a person? 1.- obsessive openness, not subject to OLPC NDA 2.- reasonable knowledge of OLPC, known by and knows the actors / goings on 3.- (please add on, edit, maybe wiki this thing?) . *(more of the same) Paul Fox wrote: c. scott ananian wrote: On 5/22/08, Todd Cranston-Cuebas [EMAIL PROTECTED] wrote: i think your earlier proposal for establishing a liaison/ambassador role was spot on -- that role of evangelism and outreach was missing throughout G1G1, and is still missing today ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Help regarding Sugar on Ubuntu
Hello All, I have changed fullscreen mode of Xephyr into 800x600, but now how to change the size of frames and icons ? I have tried changing sugar-xo.gtkrc file but nothing happens, any clues? 2ndly, the activities inside this small screen do not show properly i.e they remain the actual full screen size how to make this environment fit into the size of 800x600 Regards -- Waqas Toor member of OLPC Pakistan Team member of Ubuntu Pakistan Team ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] OLPC's bizarre behaviors
On 5/22/08, Yamandu Ploskonka [EMAIL PROTECTED] wrote: To begin with, could we pinpoint _what_ we are looking in such a person? 1.- obsessive openness, not subject to OLPC NDA I actually want the opposite. You are welcome to have a non-OLPC community liason, but *I* want someone *employed by OLPC* who knows *all* the secrets and works to make them public to the greatest degree possible. Someone who attends all the meetings and continually challenges us, why isn't this public and why haven't I seen this on devel@? Having someone who only knows the stuff they've seen on devel@ or olpcnews isn't going to help us get more stuff onto devel@ and olpcnews. --scott -- ( http://cscott.net/ ) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] OLPC's bizarre behaviors
On Fri, May 23, 2008 at 4:45 AM, Christoph Derndorfer [EMAIL PROTECTED] wrote: So you're basically looking for someone who doesn't mind being despised by both OLPC staff (God, s/he keeps bugging me, how annoying!) and the community (s/he knows more than s/he's telling us). Nah. We all want to pull things to the open. But naturally some discussions do contain confidential information. And to makesure it's ok to publish there's a bit of work to do, and it sometimes falls through the cracks. Someone who keeps track of those things would be great. It's a well known function, and most large open source teams that have physical headquaters have such a role. Think mozilla, ubuntu, etc. cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Second Bundle Commentary
Dear sugar, Jameson, Ben, Eben, and I talked at length three weeks ago about bundle formats and the Sugar UI's data model. I've published a barely-edited transcript of that conversation at http://wiki.laptop.org/go/User:Mstone/Commentaries/Bundles_2 Please review it at your leisure both for accuracy and to generate new comments. Michael ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] dual-display ebook reader project
Some of you might have seen this, but it was certainly new to me: http://vis.berkeley.edu/papers/ebook/ http://www.youtube.com/watch?v=Mbh4Fdnv-s0 Definitely some food for thought wrt XO-2, don't you think? Thanks for the heads-up, curiouslee! Christoph -- Christoph Derndorfer Co-Editor OLPCnews, http://www.olpcnews.com ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] A Conversation with Marco
Marco and I (as well as Dennis and Bernie) had some long chats at the beginning of this week about how to work together to pull of the next release. At Marco's request, I've posted one important chunk of this conversation at http://wiki.laptop.org/go/User:Mstone/Commentaries/Releases_2 Please comment freely. Thanks, Michael ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Release process
On 5/22/08, Michael Stone [EMAIL PROTECTED] wrote: Marco and I (as well as Dennis and Bernie) had some long chats at the beginning of this week about how to work together to pull of the next release. At Marco's request, I've posted one important chunk of this conversation at http://wiki.laptop.org/go/User:Mstone/Commentaries/Releases_2 Please comment freely. I think that your desire to always provide a stable build is admirable, but you need to be much more careful not to let it interfere with development. A broken build is not a bad thing, as long as there is still a stable version for people to use. Linus' philosophy of development is valid here: the way to get bugs fixed is to get the code distributed. In my opinion, if the remaining bugs in the FC9 branch are small enough not to interfere with the sugar developer's work, there is no reason why they shouldn't start working with it. The more people looking at that branch, the more people will be able to help Dennis pummel the bugs out of it. I'm all for not landing broken code into joyride (which makes joyride the 'testing' branch of the debian triumvirate), as long as people have unstable and experimental branches to land their works in progress for broad review. (As I proposed elsewhere, I actually encourage the creation of *lots* of long-lived unstable branches with different maintainers and focuses (sugar, cerebro, X, etc) and well-defined merge windows. --scott -- ( http://cscott.net/ ) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Help regarding Sugar on Ubuntu
On 5/22/08, Waqas Toor [EMAIL PROTECTED] wrote: I have changed fullscreen mode of Xephyr into 800x600, but now how to change the size of frames and icons ? I have tried changing sugar-xo.gtkrc file but nothing happens, any clues? 2ndly, the activities inside this small screen do not show properly i.e they remain the actual full screen size how to make this environment fit into the size of 800x600 I'm not certain the Sugar will scale well to a screen that small. It seems to scale to 1024x768 quite nicely, though. --scott -- ( http://cscott.net/ ) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Help regarding Sugar on Ubuntu
On Fri, 23 May 2008, C. Scott Ananian wrote: On 5/22/08, Waqas Toor [EMAIL PROTECTED] wrote: I have changed fullscreen mode of Xephyr into 800x600, but now how to change the size of frames and icons ? I have tried changing sugar-xo.gtkrc file but nothing happens, any clues? 2ndly, the activities inside this small screen do not show properly i.e they remain the actual full screen size how to make this environment fit into the size of 800x600 I'm not certain the Sugar will scale well to a screen that small. It seems to scale to 1024x768 quite nicely, though. it should, that's approximatly the same effective resolution that the XO-1 gets with it's screen in color mode. David Lang ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
