Re: gathering use cases
To clarify, by use case, we mean a way to describe the interaction of people with a system. In this case, it may be how a child interacts with the XO, and the XS (via XO) or how a teacher may interact with the XS (via XO or otherwise) by using Moodle. As you may have noticed, pretty much every response on this thread focuses on the system, with the assumption that the user end of it is understood well. I am not so sure. Take a look at http://www.gatherspace.com/static/use_case_example.html to see if it helps you understand the idea behind use cases and user stories. Here's another example of how use cases can vary by being very high level (which is what we are aiming for) and can be user centric or system centric. http://www.agilemodeling.com/artifacts/systemUseCase.htm Our focus is user centric, in a way where we would like to describe the actors (children, parents, teachers, admin, etc) and their actions (access class information, read books, send email) without the XS as the focus. Networking topology, storage, UI, LMS, DNS, etc. should flow from the storytelling exercise. We are a bunch of technologists and it is easy to get carried away by designing from the tech and not the user end. Sometimes that misses the mark. We may build it and they may not come. cheers, Sameer On Thu, Nov 8, 2012 at 4:07 PM, Sridhar Dhanapalan wrote: > On 9 November 2012 10:19, Tony Anderson wrote: > > Hi, Sridhar > > > > Thanks for the clarification. I guess I was mislead by statements such > as: > > > > The platform for the One Network server is an ARMv7-based XO, running the > > One Education OS (based on OLPC OS). This makes development, and > deployment > > and support far simpler than a standalone distribution. The OS can be > > extended with server capabilities using a bootable USB Customisation > Stick > > (offline) or yum. > > > > Please accept my apology if any statement I have made seemed uncivil, > that > > was certainly not my intention. Communicating by email in certainly much > > more hazardous in this regard than face-to-face. > > Thank you, Tony. I was quite careful to take your needs into account > when I wrote the design doc, so I had trouble understanding your > opposition to the idea. > > Maybe we can make the doc clearer somehow? I structured it as: > > 1. context > 2. Community XS design > 3. One Network server > > The Community XS design itself is flexible enough to handle a variety > of different deployments' needs. One Network server is merely one > configuration of the Community XS, mentioned as an example of what can > be done. > > > > Just as the deployments you are supporting have specific and urgent > needs, > > so do the ones I am working with. I don't believe either of us is > pursuing > > personal desires. We certainly can easily differ on which is the > appropriate > > technical approach to solving the problems of a deployment. > > I think we generally want the same thing in the end. I'm happy to > continue the conversation to improve the design and implementation. I > sincerely believe that this design can accommodate your needs. > > > > I really appreciate this specification: > > > > > > * this is a flexible design, built on Fedora > > * it will run anywhere where x86 or ARM Fedora will work > > * it can be installed on top of an existing Fedora installation > > using 'yum groupinstall xsce' > > * being designed in this way provides extreme flexibility for > deployments > > * all current features of the XS (Moodle, etc.) will be ported, but > > will be optional > > * installation and configuration will be easy, but sysadmins will be > > able to treat it like any Fedora installation > > Awesome. I hope this also satisfies your desire to have it rebased to > Fedora to work on ARM systems. That's a key goal of this project, > while maintaining compatibility with x86. > > > > There is clearly a great deal to be gained by a community taking > > responsibility for the ongoing development and maintenance of the school > > server as neither Daniel Drake nor Martin Langhoff are likely to have > > adequate time for this in the foreseeable future. > > Indeed. A motivating factor was to take some of the load off some of > these prolific people and spread it out to the community in a > sustainable way. > > > Cheers, > Sridhar > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: 13.1.0 development build 10 released
You are free to unsuscribe from this list: http://lists.laptop.org/listinfo/Devel Date: Thu, 8 Nov 2012 19:31:31 -0800 Subject: RE: 13.1.0 development build 10 released From: strawbridgenat...@gmail.com To: alan...@hotmail.com CC: devel@lists.laptop.org; d...@laptop.org Cease all emails to me and immediately remove me from all future emails. Strawbridge On Nov 8, 2012 7:29 PM, "Alan Jhonn Aguiar Schwyn" wrote: Hi, Quick tests: - In the "neighborhood" when you click on AP with password, not appears the window to enter the password. If you make a right click and select "connect" (that I supose thatcontinues being "connect" because only see a black frame) the window appears. Attach "neighborhood.png"In the shell appears some error of this.. attach the log file.. HOW TO FIX: file: "/usr/lib/python2.7/site-packages/jarabe/desktop/networkviews.py" line: 648change: _palette_ by: _palette And Works!! ;-) - Copy an entry to a Pendrive (or similar). Continues with problem. No copy! If you use the secondary menu: copy to.. it works.. - The activities works.. I'm only check the basic.. Regards! Alan > Date: Thu, 8 Nov 2012 13:31:41 -0600> Subject: 13.1.0 development build 10 > released > From: d...@laptop.org > To: devel@lists.laptop.org > > A new 13.1.0 development build is available. > > http://wiki.laptop.org/go/13.1.0 > http://build.laptop.org/13.1.0/os10/ > > Changes: > - The latest sugar component versions that were released on Wednesday > - A handful of activity updates > - XO-4 bluez command-line utility added to allow the factory to test > bluetooth support on the XO-4 8787 wireless card > - Latest XO-4 kernel work for suspend/resume > - XO-1.75 audio recording works again (#12199) > > Thanks for any testing and feedback! > > Daniel > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: 13.1.0 development build 10 released
Cease all emails to me and immediately remove me from all future emails. Strawbridge On Nov 8, 2012 7:29 PM, "Alan Jhonn Aguiar Schwyn" wrote: > Hi, > > Quick tests: > > - In the "neighborhood" when you click on AP with password, not appears > the window > to enter the password. If you make a right click and select "connect" > (that I supose that > continues being "connect" because only see a black frame) the window > appears. > Attach "neighborhood.png" > In the shell appears some error of this.. attach the log file.. > > HOW TO FIX: > > file: "/usr/lib/python2.7/site-packages/jarabe/desktop/networkviews.py" > line: 648 > change: > > _palette_ > > by: > > _palette > > And Works!! ;-) > > - Copy an entry to a Pendrive (or similar). Continues with problem. No > copy! > If you use the secondary menu: copy to.. it works.. > > - The activities works.. I'm only check the basic.. > > Regards! > > Alan > > > > Date: Thu, 8 Nov 2012 13:31:41 -0600 > > Subject: 13.1.0 development build 10 released > > From: d...@laptop.org > > To: devel@lists.laptop.org > > > > A new 13.1.0 development build is available. > > > > http://wiki.laptop.org/go/13.1.0 > > http://build.laptop.org/13.1.0/os10/ > > > > Changes: > > - The latest sugar component versions that were released on Wednesday > > - A handful of activity updates > > - XO-4 bluez command-line utility added to allow the factory to test > > bluetooth support on the XO-4 8787 wireless card > > - Latest XO-4 kernel work for suspend/resume > > - XO-1.75 audio recording works again (#12199) > > > > Thanks for any testing and feedback! > > > > Daniel > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: gathering use cases
On 9 November 2012 10:19, Tony Anderson wrote: > Hi, Sridhar > > Thanks for the clarification. I guess I was mislead by statements such as: > > The platform for the One Network server is an ARMv7-based XO, running the > One Education OS (based on OLPC OS). This makes development, and deployment > and support far simpler than a standalone distribution. The OS can be > extended with server capabilities using a bootable USB Customisation Stick > (offline) or yum. > > Please accept my apology if any statement I have made seemed uncivil, that > was certainly not my intention. Communicating by email in certainly much > more hazardous in this regard than face-to-face. Thank you, Tony. I was quite careful to take your needs into account when I wrote the design doc, so I had trouble understanding your opposition to the idea. Maybe we can make the doc clearer somehow? I structured it as: 1. context 2. Community XS design 3. One Network server The Community XS design itself is flexible enough to handle a variety of different deployments' needs. One Network server is merely one configuration of the Community XS, mentioned as an example of what can be done. > Just as the deployments you are supporting have specific and urgent needs, > so do the ones I am working with. I don't believe either of us is pursuing > personal desires. We certainly can easily differ on which is the appropriate > technical approach to solving the problems of a deployment. I think we generally want the same thing in the end. I'm happy to continue the conversation to improve the design and implementation. I sincerely believe that this design can accommodate your needs. > I really appreciate this specification: > > > * this is a flexible design, built on Fedora > * it will run anywhere where x86 or ARM Fedora will work > * it can be installed on top of an existing Fedora installation > using 'yum groupinstall xsce' > * being designed in this way provides extreme flexibility for deployments > * all current features of the XS (Moodle, etc.) will be ported, but > will be optional > * installation and configuration will be easy, but sysadmins will be > able to treat it like any Fedora installation Awesome. I hope this also satisfies your desire to have it rebased to Fedora to work on ARM systems. That's a key goal of this project, while maintaining compatibility with x86. > There is clearly a great deal to be gained by a community taking > responsibility for the ongoing development and maintenance of the school > server as neither Daniel Drake nor Martin Langhoff are likely to have > adequate time for this in the foreseeable future. Indeed. A motivating factor was to take some of the load off some of these prolific people and spread it out to the community in a sustainable way. Cheers, Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: gathering use cases
Hi, Sridhar Thanks for the clarification. I guess I was mislead by statements such as: The platform for the One Network server is an ARMv7-based XO, running the One Education OS (based on OLPC OS). This makes development, and deployment and support far simpler than a standalone distribution. The OS can be extended with server capabilities using a bootable USB Customisation Stick (offline) or yum. Please accept my apology if any statement I have made seemed uncivil, that was certainly not my intention. Communicating by email in certainly much more hazardous in this regard than face-to-face. Just as the deployments you are supporting have specific and urgent needs, so do the ones I am working with. I don't believe either of us is pursuing personal desires. We certainly can easily differ on which is the appropriate technical approach to solving the problems of a deployment. I really appreciate this specification: * this is a flexible design, built on Fedora * it will run anywhere where x86 or ARM Fedora will work * it can be installed on top of an existing Fedora installation using 'yum groupinstall xsce' * being designed in this way provides extreme flexibility for deployments * all current features of the XS (Moodle, etc.) will be ported, but will be optional * installation and configuration will be easy, but sysadmins will be able to treat it like any Fedora installation There is clearly a great deal to be gained by a community taking responsibility for the ongoing development and maintenance of the school server as neither Daniel Drake nor Martin Langhoff are likely to have adequate time for this in the foreseeable future. Tony Tony On 11/08/2012 05:59 PM, Sridhar Dhanapalan wrote: On 9 November 2012 09:10, Tony Anderson wrote: This is my greatest concern. The ability of a server to deliver content is central. It is my understanding that your Community XS does not support a LAMP stack or Moodle. Please do not refer to the Community XS as XO-0.8 until there is a chance that it can deliver the essential capabilities of XS-0.7. My other concern is that a lot of very talented people are spending a lot of time solving a non-problem. Naturally, the network problem you mention is solved by connecting the XS-0.7 to that network as the WAN. Tony, It appears that no matter what we say, you are cemented in some strange notions about the community XS: * that it is intended to run only on XOs * that it cannot (and will not) serve content * that your personal desires from an XS are shared by every other deployment in the world I think we've been quite clear about what we're intending to achieve. If you're going to criticise, at least be civil enough to do so based on the facts: * this is a flexible design, built on Fedora * it will run anywhere where x86 or ARM Fedora will work * it can be installed on top of an existing Fedora installation using 'yum groupinstall xsce' * being designed in this way provides extreme flexibility for deployments * all current features of the XS (Moodle, etc.) will be ported, but will be optional * installation and configuration will be easy, but sysadmins will be able to treat it like any Fedora installation We've tried hard to be inclusive and constructive. I ask you to do the same. Regards, Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: gathering use cases
On 9 November 2012 09:10, Tony Anderson wrote: > > This is my greatest concern. The ability of a server to deliver content is > central. It is my understanding that your Community XS does not support a > LAMP stack or Moodle. Please do not refer to the Community XS as XO-0.8 > until there is a chance that it can deliver the essential capabilities of > XS-0.7. My other concern is that a lot of very talented people are spending > a lot of time solving a non-problem. > > Naturally, the network problem you mention is solved by connecting the > XS-0.7 to that network as the WAN. Tony, It appears that no matter what we say, you are cemented in some strange notions about the community XS: * that it is intended to run only on XOs * that it cannot (and will not) serve content * that your personal desires from an XS are shared by every other deployment in the world I think we've been quite clear about what we're intending to achieve. If you're going to criticise, at least be civil enough to do so based on the facts: * this is a flexible design, built on Fedora * it will run anywhere where x86 or ARM Fedora will work * it can be installed on top of an existing Fedora installation using 'yum groupinstall xsce' * being designed in this way provides extreme flexibility for deployments * all current features of the XS (Moodle, etc.) will be ported, but will be optional * installation and configuration will be easy, but sysadmins will be able to treat it like any Fedora installation We've tried hard to be inclusive and constructive. I ask you to do the same. Regards, Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: gathering use cases
Hi, If you are re-implementing XS-0.7, one beneficial project would be to rebase it on Fedora so that it will run on Arm systems. This is currently a limitation of CentOS. The design of XS separates the LAN and WAN networks. The XOs connect to schoolserver via the LAN network. The school server has a domain name relative to the WAN network appropriate to that network. This is set up by the netsetup.sh script. XS-0.7 provides normal firewall protection to the XOs. OLE Nepal has added Dan's Guardian to provide specific protection against access to objectionable sites. Tony On 11/08/2012 05:25 PM, Jerry Vonau wrote: On Thu, 2012-11-08 at 17:10 -0500, Tony Anderson wrote: On 11/08/2012 05:01 PM, Jerry Vonau wrote: Hi Tony and all, On Thu, 2012-11-08 at 13:32 -0500, Tony Anderson wrote: Hi, Sridhar One of the important potential benefits from gathering use cases is to clarify the roles of the Community XS project and XS-0.7. Why is that an issue at at all? The "Community XS" (think XS-0.8 here) is going to address the current shortcomings of XS-0.7. This is my greatest concern. The ability of a server to deliver content is central. It is my understanding that your Community XS does not support a LAMP stack or Moodle. Please do not refer to the Community XS as XO-0.8 until there is a chance that it can deliver the essential capabilities of XS-0.7. My other concern is that a lot of very talented people are spending a lot of time solving a non-problem. That's very interesting LAMP is installed and George tells me Moodle is now working. We just didn't quite have the time prior to SF to debug the issue and I confident that the work done will become 0.8. Naturally, the network problem you mention is solved by connecting the XS-0.7 to that network as the WAN. How do you deal with the name resolution of 'schoolserver' without having the ability to alter the network dns server's entries or have the server called something other than 'schoolserver' to avoid a clash with an pre-existing server on the target network? Jerry Yours, Tony From my perspective, if you can afford to deploy a server with 2GB or more main memory and 500GB or more hard drive capacity, XS-0.7 serves well and easily supports adding or customizing services. The configuration shown in SF costs less than $350 and draws 18w (based on measurements taken by George Hunt). With a large hard drive, it is perfectly to keep Moodle even if it is not used. In my experience, the school server is installed in the school ready with XS-07 installed along with the available content. Barring hardware failure, the only interaction at the school is to turn the server on at the start of day and turn it off at the end. With modern computers, both functions require only a push on the power button. I'm not thinking about an XO here at all but on a server that you spec'd. Tell me how do you deploy the 0.7 version on a network where you don't have control over the DNS and have everything work? I have an idea on how to pull that off with avahi, I would like to hear about how you would implement that situation. Community XS serves a valuable role where only XOs are available or where power constraints are critical. It may also have a role in supporting special network requirements. Not to mention better hardware support for the latest hardware available and ARM support by using Fedora. You can get on board with the future and have a say in your pet interests but please don't get in the way of progress. Jerry The other XS-CE developer Tony On 11/08/2012 10:55 AM, devel-requ...@lists.laptop.org wrote: Message: 2 Date: Thu, 8 Nov 2012 13:57:12 +1100 From: Sridhar Dhanapalan To: Holt Cc: Devel's in the Details, Maryam Rehan El Baz,iaep, XS Devel , Support Gangsters Subject: Re: gathering use cases Message-ID: Content-Type: text/plain; charset=ISO-8859-1 On 3 November 2012 07:46, Holt wrote: Thanks much Sameer. Am includingsupport-g...@laptop.org to make sure we gather microdeployment and support volunteer feedback too. While our XS Community Edition experiment ain't quite ready for showtime/download yet, its white paper & code repository are here: http://wiki.laptop.org/go/User:Holt/XS_Community_Edition The white paper that Adam is referring to can be found at https://docs.google.com/a/dhanapalan.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc I am the primary author, but it was written by canvassing feedback and opinions from schools and XS community members (including Jerry Vonau, George Hunt, Adam Holt and many others). The paper discusses several use cases and design goals, and outlines the underlying principles behind how we do things in OLPC Australia. There is some miscommunication being spread around that I'd like to clear up. Firstly, this is not a 'secret' project. The white paper explains our mission, and the code repo and issues trackers are o
Re: gathering use cases
On Thu, 2012-11-08 at 17:10 -0500, Tony Anderson wrote: > On 11/08/2012 05:01 PM, Jerry Vonau wrote: > > Hi Tony and all, > > > > On Thu, 2012-11-08 at 13:32 -0500, Tony Anderson wrote: > >> Hi, Sridhar > >> > >> One of the important potential benefits from gathering use cases is to > >> clarify the roles of the Community XS project and XS-0.7. > >> > > Why is that an issue at at all? The "Community XS" (think XS-0.8 here) > > is going to address the current shortcomings of XS-0.7. > > This is my greatest concern. The ability of a server to deliver content > is central. It is my understanding that your Community XS does not > support a LAMP stack or Moodle. Please do not refer to the Community XS > as XO-0.8 until there is a chance that it can deliver the essential > capabilities of XS-0.7. My other concern is that a lot of very talented > people are spending a lot of time solving a non-problem. > That's very interesting LAMP is installed and George tells me Moodle is now working. We just didn't quite have the time prior to SF to debug the issue and I confident that the work done will become 0.8. > Naturally, the network problem you mention is solved by connecting the > XS-0.7 to that network as the WAN. > How do you deal with the name resolution of 'schoolserver' without having the ability to alter the network dns server's entries or have the server called something other than 'schoolserver' to avoid a clash with an pre-existing server on the target network? Jerry > Yours, > > Tony > > > >> From my perspective, if you can afford to deploy a server with 2GB or > >> more main memory and 500GB or more hard drive capacity, XS-0.7 serves > >> well and easily supports adding or customizing services. The > >> configuration shown in SF costs less than $350 and draws 18w (based on > >> measurements taken by George Hunt). With a large hard drive, it is > >> perfectly to keep Moodle even if it is not used. > >> > >> In my experience, the school server is installed in the school ready > >> with XS-07 installed along with the available content. Barring hardware > >> failure, the only interaction at the school is to turn the server on at > >> the start of day and turn it off at the end. With modern computers, both > >> functions require only a push on the power button. > >> > > I'm not thinking about an XO here at all but on a server that you > > spec'd. Tell me how do you deploy the 0.7 version on a network where you > > don't have control over the DNS and have everything work? I have an idea > > on how to pull that off with avahi, I would like to hear about how you > > would implement that situation. > > > >> Community XS serves a valuable role where only XOs are available or > >> where power constraints are critical. It may also have a role in > >> supporting special network requirements. > >> > > Not to mention better hardware support for the latest hardware available > > and ARM support by using Fedora. You can get on board with the future > > and have a say in your pet interests but please don't get in the way of > > progress. > > > > Jerry > > The other XS-CE developer > > > >> Tony > >> > >> > >> On 11/08/2012 10:55 AM, devel-requ...@lists.laptop.org wrote: > >>> Message: 2 > >>> Date: Thu, 8 Nov 2012 13:57:12 +1100 > >>> From: Sridhar Dhanapalan > >>> To: Holt > >>> Cc: Devel's in the Details, Maryam Rehan El > >>> Baz, iaep, XS Devel > >>> ,Support Gangsters > >>> > >>> Subject: Re: gathering use cases > >>> Message-ID: > >>> > >>> Content-Type: text/plain; charset=ISO-8859-1 > >>> > >>> On 3 November 2012 07:46, Holt wrote: > > Thanks much Sameer. Am includingsupport-g...@laptop.org to make sure > > we > > gather microdeployment and support volunteer feedback too. > > > > While our XS Community Edition experiment ain't quite ready for > > showtime/download yet, its white paper & code repository are here: > > http://wiki.laptop.org/go/User:Holt/XS_Community_Edition > >>> The white paper that Adam is referring to can be found at > >>> https://docs.google.com/a/dhanapalan.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc > >>> > >>> I am the primary author, but it was written by canvassing feedback and > >>> opinions from schools and XS community members (including Jerry Vonau, > >>> George Hunt, Adam Holt and many others). The paper discusses several > >>> use cases and design goals, and outlines the underlying principles > >>> behind how we do things in OLPC Australia. > >>> > >>> There is some miscommunication being spread around that I'd like to > >>> clear up. Firstly, this is not a 'secret' project. The white paper > >>> explains our mission, and the code repo and issues trackers are open. > >>> Secondly, the intent is to create a flexible framework that can be > >>> adapted to suit local needs. This is*not*, as some keep asserting, a > >>> project to have the XS work only on the XO. The community XS will work >
Re: gathering use cases
On 11/08/2012 05:01 PM, Jerry Vonau wrote: Hi Tony and all, On Thu, 2012-11-08 at 13:32 -0500, Tony Anderson wrote: Hi, Sridhar One of the important potential benefits from gathering use cases is to clarify the roles of the Community XS project and XS-0.7. Why is that an issue at at all? The "Community XS" (think XS-0.8 here) is going to address the current shortcomings of XS-0.7. This is my greatest concern. The ability of a server to deliver content is central. It is my understanding that your Community XS does not support a LAMP stack or Moodle. Please do not refer to the Community XS as XO-0.8 until there is a chance that it can deliver the essential capabilities of XS-0.7. My other concern is that a lot of very talented people are spending a lot of time solving a non-problem. Naturally, the network problem you mention is solved by connecting the XS-0.7 to that network as the WAN. Yours, Tony From my perspective, if you can afford to deploy a server with 2GB or more main memory and 500GB or more hard drive capacity, XS-0.7 serves well and easily supports adding or customizing services. The configuration shown in SF costs less than $350 and draws 18w (based on measurements taken by George Hunt). With a large hard drive, it is perfectly to keep Moodle even if it is not used. In my experience, the school server is installed in the school ready with XS-07 installed along with the available content. Barring hardware failure, the only interaction at the school is to turn the server on at the start of day and turn it off at the end. With modern computers, both functions require only a push on the power button. I'm not thinking about an XO here at all but on a server that you spec'd. Tell me how do you deploy the 0.7 version on a network where you don't have control over the DNS and have everything work? I have an idea on how to pull that off with avahi, I would like to hear about how you would implement that situation. Community XS serves a valuable role where only XOs are available or where power constraints are critical. It may also have a role in supporting special network requirements. Not to mention better hardware support for the latest hardware available and ARM support by using Fedora. You can get on board with the future and have a say in your pet interests but please don't get in the way of progress. Jerry The other XS-CE developer Tony On 11/08/2012 10:55 AM, devel-requ...@lists.laptop.org wrote: Message: 2 Date: Thu, 8 Nov 2012 13:57:12 +1100 From: Sridhar Dhanapalan To: Holt Cc: Devel's in the Details, Maryam Rehan El Baz,iaep, XS Devel , Support Gangsters Subject: Re: gathering use cases Message-ID: Content-Type: text/plain; charset=ISO-8859-1 On 3 November 2012 07:46, Holt wrote: Thanks much Sameer. Am includingsupport-g...@laptop.org to make sure we gather microdeployment and support volunteer feedback too. While our XS Community Edition experiment ain't quite ready for showtime/download yet, its white paper & code repository are here: http://wiki.laptop.org/go/User:Holt/XS_Community_Edition The white paper that Adam is referring to can be found at https://docs.google.com/a/dhanapalan.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc I am the primary author, but it was written by canvassing feedback and opinions from schools and XS community members (including Jerry Vonau, George Hunt, Adam Holt and many others). The paper discusses several use cases and design goals, and outlines the underlying principles behind how we do things in OLPC Australia. There is some miscommunication being spread around that I'd like to clear up. Firstly, this is not a 'secret' project. The white paper explains our mission, and the code repo and issues trackers are open. Secondly, the intent is to create a flexible framework that can be adapted to suit local needs. This is*not*, as some keep asserting, a project to have the XS work only on the XO. The community XS will work on any x86 or ARM based hardware that works with Fedora. The white paper explains this in depth. Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: gathering use cases
Hi Tony and all, On Thu, 2012-11-08 at 13:32 -0500, Tony Anderson wrote: > Hi, Sridhar > > One of the important potential benefits from gathering use cases is to > clarify the roles of the Community XS project and XS-0.7. > Why is that an issue at at all? The "Community XS" (think XS-0.8 here) is going to address the current shortcomings of XS-0.7. > From my perspective, if you can afford to deploy a server with 2GB or > more main memory and 500GB or more hard drive capacity, XS-0.7 serves > well and easily supports adding or customizing services. The > configuration shown in SF costs less than $350 and draws 18w (based on > measurements taken by George Hunt). With a large hard drive, it is > perfectly to keep Moodle even if it is not used. > > In my experience, the school server is installed in the school ready > with XS-07 installed along with the available content. Barring hardware > failure, the only interaction at the school is to turn the server on at > the start of day and turn it off at the end. With modern computers, both > functions require only a push on the power button. > I'm not thinking about an XO here at all but on a server that you spec'd. Tell me how do you deploy the 0.7 version on a network where you don't have control over the DNS and have everything work? I have an idea on how to pull that off with avahi, I would like to hear about how you would implement that situation. > Community XS serves a valuable role where only XOs are available or > where power constraints are critical. It may also have a role in > supporting special network requirements. > Not to mention better hardware support for the latest hardware available and ARM support by using Fedora. You can get on board with the future and have a say in your pet interests but please don't get in the way of progress. Jerry The other XS-CE developer > Tony > > > On 11/08/2012 10:55 AM, devel-requ...@lists.laptop.org wrote: > > Message: 2 > > Date: Thu, 8 Nov 2012 13:57:12 +1100 > > From: Sridhar Dhanapalan > > To: Holt > > Cc: Devel's in the Details, Maryam Rehan El > > Baz, iaep, XS Devel > > ,Support Gangsters > > > > Subject: Re: gathering use cases > > Message-ID: > > > > Content-Type: text/plain; charset=ISO-8859-1 > > > > On 3 November 2012 07:46, Holt wrote: > >> >Thanks much Sameer. Am includingsupport-g...@laptop.org to make sure we > >> >gather microdeployment and support volunteer feedback too. > >> > > >> >While our XS Community Edition experiment ain't quite ready for > >> >showtime/download yet, its white paper & code repository are here: > >> >http://wiki.laptop.org/go/User:Holt/XS_Community_Edition > > The white paper that Adam is referring to can be found at > > https://docs.google.com/a/dhanapalan.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc > > > > I am the primary author, but it was written by canvassing feedback and > > opinions from schools and XS community members (including Jerry Vonau, > > George Hunt, Adam Holt and many others). The paper discusses several > > use cases and design goals, and outlines the underlying principles > > behind how we do things in OLPC Australia. > > > > There is some miscommunication being spread around that I'd like to > > clear up. Firstly, this is not a 'secret' project. The white paper > > explains our mission, and the code repo and issues trackers are open. > > Secondly, the intent is to create a flexible framework that can be > > adapted to suit local needs. This is*not*, as some keep asserting, a > > project to have the XS work only on the XO. The community XS will work > > on any x86 or ARM based hardware that works with Fedora. The white > > paper explains this in depth. > > > > Sridhar > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
13.1.0 development build 10 released
A new 13.1.0 development build is available. http://wiki.laptop.org/go/13.1.0 http://build.laptop.org/13.1.0/os10/ Changes: - The latest sugar component versions that were released on Wednesday - A handful of activity updates - XO-4 bluez command-line utility added to allow the factory to test bluetooth support on the XO-4 8787 wireless card - Latest XO-4 kernel work for suspend/resume - XO-1.75 audio recording works again (#12199) Thanks for any testing and feedback! Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: gathering use cases
Hi, Sridhar One of the important potential benefits from gathering use cases is to clarify the roles of the Community XS project and XS-0.7. From my perspective, if you can afford to deploy a server with 2GB or more main memory and 500GB or more hard drive capacity, XS-0.7 serves well and easily supports adding or customizing services. The configuration shown in SF costs less than $350 and draws 18w (based on measurements taken by George Hunt). With a large hard drive, it is perfectly to keep Moodle even if it is not used. In my experience, the school server is installed in the school ready with XS-07 installed along with the available content. Barring hardware failure, the only interaction at the school is to turn the server on at the start of day and turn it off at the end. With modern computers, both functions require only a push on the power button. Community XS serves a valuable role where only XOs are available or where power constraints are critical. It may also have a role in supporting special network requirements. Tony On 11/08/2012 10:55 AM, devel-requ...@lists.laptop.org wrote: Message: 2 Date: Thu, 8 Nov 2012 13:57:12 +1100 From: Sridhar Dhanapalan To: Holt Cc: Devel's in the Details, Maryam Rehan El Baz,iaep, XS Devel , Support Gangsters Subject: Re: gathering use cases Message-ID: Content-Type: text/plain; charset=ISO-8859-1 On 3 November 2012 07:46, Holt wrote: >Thanks much Sameer. Am includingsupport-g...@laptop.org to make sure we >gather microdeployment and support volunteer feedback too. > >While our XS Community Edition experiment ain't quite ready for >showtime/download yet, its white paper & code repository are here: >http://wiki.laptop.org/go/User:Holt/XS_Community_Edition The white paper that Adam is referring to can be found at https://docs.google.com/a/dhanapalan.com/document/pub?id=1dnhU2F6EntepVXTgN8QpkME8fZVUuPjcCoMUfAVKbcc I am the primary author, but it was written by canvassing feedback and opinions from schools and XS community members (including Jerry Vonau, George Hunt, Adam Holt and many others). The paper discusses several use cases and design goals, and outlines the underlying principles behind how we do things in OLPC Australia. There is some miscommunication being spread around that I'd like to clear up. Firstly, this is not a 'secret' project. The white paper explains our mission, and the code repo and issues trackers are open. Secondly, the intent is to create a flexible framework that can be adapted to suit local needs. This is*not*, as some keep asserting, a project to have the XS work only on the XO. The community XS will work on any x86 or ARM based hardware that works with Fedora. The white paper explains this in depth. Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Neonode low-level access
On 2012-11-08, at 17:01, Paul Fox wrote: > gonzalo wrote: >> Should be a a way to get this info, if not I don't know how this demo can >> work: >> >> http://www.youtube.com/watch?v=b-C42PGoDqY >> >> I am more than interested to get the piano working > > i'll push harder on the vendor for this. > > paul The piano is exactly what I was thinking about :) - Bert - > >> >> Gonzalo >> >> On Thu, Nov 8, 2012 at 12:47 PM, Gary Martin >> wrote: >> >>> Hi Bert, >>> >>> On 8 Nov 2012, at 14:38, Bert Freudenberg wrote: >>> How can I get at low-level data from the XO-4's touch screen in Linux? >>> I'm thinking of the actual light levels of all the sensors around the edges. >>> >>> Unfortunately not at the moment, as far as I'm aware of (happy to be >>> proven wrong). It was on the feature design list at an early stage of the >>> dev cycle (so that we could implement things like a multi-touch piano) but >>> time went to the primary use case and no driver work was done exposing this >>> data, as far as I can tell. There are some parameters exposed under >>> /sys/module/zforce/parameters, but nothing like the light level data. >>> Perhaps something to push for in the next cycle? >>> >>> Regards, >>> --Gary >>> Certain apps could benefit from this - e.g. many of Neonode's own >>> impressive demos could not be implemented using only the X11 events I get >>> in Sugar. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel >>> >>> ___ >>> Devel mailing list >>> Devel@lists.laptop.org >>> http://lists.laptop.org/listinfo/devel >>> >> part 2 text/plain 129 >> ___ >> Devel mailing list >> Devel@lists.laptop.org >> http://lists.laptop.org/listinfo/devel > > =- > paul fox, p...@laptop.org > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Neonode low-level access
gonzalo wrote: > Should be a a way to get this info, if not I don't know how this demo can > work: > > http://www.youtube.com/watch?v=b-C42PGoDqY > > I am more than interested to get the piano working i'll push harder on the vendor for this. paul > > Gonzalo > > On Thu, Nov 8, 2012 at 12:47 PM, Gary Martin > wrote: > > > Hi Bert, > > > > On 8 Nov 2012, at 14:38, Bert Freudenberg wrote: > > > > > How can I get at low-level data from the XO-4's touch screen in Linux? > > I'm thinking of the actual light levels of all the sensors around the > > edges. > > > > Unfortunately not at the moment, as far as I'm aware of (happy to be > > proven wrong). It was on the feature design list at an early stage of the > > dev cycle (so that we could implement things like a multi-touch piano) but > > time went to the primary use case and no driver work was done exposing this > > data, as far as I can tell. There are some parameters exposed under > > /sys/module/zforce/parameters, but nothing like the light level data. > > Perhaps something to push for in the next cycle? > > > > Regards, > > --Gary > > > > > Certain apps could benefit from this - e.g. many of Neonode's own > > impressive demos could not be implemented using only the X11 events I get > > in Sugar. > > > > > > - Bert - > > > > > > ___ > > > Devel mailing list > > > Devel@lists.laptop.org > > > http://lists.laptop.org/listinfo/devel > > > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > > part 2 text/plain 129 > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Neonode low-level access
Should be a a way to get this info, if not I don't know how this demo can work: http://www.youtube.com/watch?v=b-C42PGoDqY I am more than interested to get the piano working Gonzalo On Thu, Nov 8, 2012 at 12:47 PM, Gary Martin wrote: > Hi Bert, > > On 8 Nov 2012, at 14:38, Bert Freudenberg wrote: > > > How can I get at low-level data from the XO-4's touch screen in Linux? > I'm thinking of the actual light levels of all the sensors around the edges. > > Unfortunately not at the moment, as far as I'm aware of (happy to be > proven wrong). It was on the feature design list at an early stage of the > dev cycle (so that we could implement things like a multi-touch piano) but > time went to the primary use case and no driver work was done exposing this > data, as far as I can tell. There are some parameters exposed under > /sys/module/zforce/parameters, but nothing like the light level data. > Perhaps something to push for in the next cycle? > > Regards, > --Gary > > > Certain apps could benefit from this - e.g. many of Neonode's own > impressive demos could not be implemented using only the X11 events I get > in Sugar. > > > > - Bert - > > > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Neonode low-level access
Hi Bert, On 8 Nov 2012, at 14:38, Bert Freudenberg wrote: > How can I get at low-level data from the XO-4's touch screen in Linux? I'm > thinking of the actual light levels of all the sensors around the edges. Unfortunately not at the moment, as far as I'm aware of (happy to be proven wrong). It was on the feature design list at an early stage of the dev cycle (so that we could implement things like a multi-touch piano) but time went to the primary use case and no driver work was done exposing this data, as far as I can tell. There are some parameters exposed under /sys/module/zforce/parameters, but nothing like the light level data. Perhaps something to push for in the next cycle? Regards, --Gary > Certain apps could benefit from this - e.g. many of Neonode's own impressive > demos could not be implemented using only the X11 events I get in Sugar. > > - Bert - > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Neonode low-level access
bert wrote: > How can I get at low-level data from the XO-4's touch screen in > Linux? I'm thinking of the actual light levels of all the sensors > around the edges. access to more data is limited. the only events we get correlate pretty directly to the X events you already see -- i.e., motion and touch. it's possible to request other data, and i think all of those requests can be issued from either OFW or linux. for OFW, see http://wiki.laptop.org/go/XO_4_Touch_Testing for the watch-fss and watch-fll commands. i think there are more as well, but you're mainly interested in linux access. for linux, see the sysfs files under /sys/kernel/debug/zforce/. there are also a few tuneables under /sys/modules/zforce/parameters. most are self-explanatory, or are quickly explained by a glance at the driver. the driver's header file contains pretty much all the original information from the docs we got: http://dev.laptop.org/git/olpc-kernel/tree/drivers/input/touchscreen/zforce.h?h=arm-3.5 > > Certain apps could benefit from this - e.g. many of Neonode's own > impressive demos could not be implemented using only the X11 events > I get in Sugar. can you elaborate? paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC XO 1.75 replace one of the 3 usb port with a mini hdmi
On Jan 19, 2011, at 6:48 AM, Andrew Puch wrote: > Is the cost and form factor viable to replace one of the external usb > ports with a mini hdmi Type C or D port ? Yes. We finally took your suggestion on XO-4. > When students or teacher give talks it would be nice for them to show to > the class on the tv what they are doing. > The type hdmi 1.4 , D connector is 2.8 mm × 6.4 mm, where as the hdmi > 1.3 type C connector is 2.42 mm × 10.42 mm; for comparison, a micro-USB > connector is 2.94 mm × 7.8 mm and usb a is 11.5 mm × 4.5 mm. > > http://en.wikipedia.org/wiki/HDMI#Connectors > > Looks like the ARMADA 610 has support for hdmi 1.3 > http://www.slashgear.com/marvell-armada-610-app-processor-1080p-hdmi-3d-graphics-more-0567682/ As does it's successor, the PXA2128, used in the XO-4 and XO-4 Touch. > Also I hope there is a give1get1 one for this machine along with a nice > touch screen :) There is a touchscreen on the XO-4 Touch. We are thinking of ways to increase availability of these. > Maybe a usb header on the motherboard, along with pcie mini card a boy > can dream. There is a spare USB port on the motherboard, although it is accessible on resistor pads, not a connector. Sorry about the mini-PCIe --- we use that connector for the WLAN but it only has SDIO and USB. Cheers, wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Neonode low-level access
How can I get at low-level data from the XO-4's touch screen in Linux? I'm thinking of the actual light levels of all the sensors around the edges. Certain apps could benefit from this - e.g. many of Neonode's own impressive demos could not be implemented using only the X11 events I get in Sugar. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
