<div dir="ltr">Added both gsettings and activity unit test tasks to the table.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 9 November 2013 01:34, Walter Bender <span dir="ltr"><<a href="mailto:walter.bender@gmail.com" target="_blank">walter.bender@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Nov 8, 2013 at 7:19 PM, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com">dwnarvaez@gmail.com</a>> wrote:<br>
> On 8 November 2013 13:10, Walter Bender <<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>> wrote:<br>
>><br>
>> Classmate and Classmate variants are already quick wide spread in some<br>
>> deployments, e.g., Argentina<br>
><br>
><br>
> I wonder if we should try to get some classmates in the hands of Sugar Labs<br>
> community members. It seems like the most solid hardware option we have for<br>
> deployments at the moment.<br>
<br>
</div>I'll look into it.<br>
<div><div class="h5"><br>
><br>
>><br>
>> > * Chromebook<br>
>><br>
>> At least one deployment is looking at this option.<br>
>><br>
><br>
> Looking forward to know how this goes :)<br>
><br>
><br>
>><br>
>> ><br>
>> > Another couple more for community evaluation (evaluation, testing,<br>
>> > marketing)<br>
>> ><br>
>> > * Linux compatible ARM boards<br>
>> > * Virtualbox<br>
>><br>
>> SoaS is our current offering for Virtualbox (As you pointed out in a<br>
>> previous thread, it is a two-step process to install. In my<br>
>> experience, that is 1 too many for our audience. Something we may be<br>
>> able to address by approaching some of the VM suppliers.)<br>
><br>
><br>
> We are crossing threads here but... I think it would be great to have a<br>
> single installer but (without having tried it!) the current installation<br>
> process doesn't seem terribly bad. I feel that documenting it better and<br>
> turning it into the first thing you see when you click "downloads" could go<br>
> a long way.<br>
><br>
>><br>
>> > - R&D resources<br>
>> ><br>
>> > I feel balance with addressing existing deployments needs is not a<br>
>> > question<br>
>> > Sugar Labs can or should answer. We should encourage and support both,<br>
>> > it's<br>
>> > up to companies and volunteers involved to see how much of either they<br>
>> > could<br>
>> > or should be doing.<br>
>><br>
>> +1<br>
>><br>
>> That said, the discipline you have imparted on us regarding unit tests<br>
>> is a step that the community can take. Maybe one of our priorities<br>
>> should be to dust off some basic automatic testing for activities as<br>
>> well. OLPC used to have such a system in place.<br>
>><br>
><br>
> Of course I'm all for more unit tests :)<br>
><br>
> The buildbot is already trying to start and close activities on every build<br>
> but it would be great if people wrote more comprehensive unit and UI tests,<br>
> similarly to what we are doing in the shell. Get them to run into<br>
> sugar-build/buildbot would be trivial...<br>
<br>
</div></div>Maybe we can work on an example for an activity and then propagate (via GCI).<br>
<div class="im"><br>
><br>
>><br>
>> ><br>
>> > We are not a company, we have no resources to allocate. But there are<br>
>> > lots<br>
>> > of concrete things we can do to encourage people to allocate them. I'm<br>
>> > really glad to see that Activity Central figured out how to devote<br>
>> > resources<br>
>> > to R&D. I hope you will be able to keep it up and more people will<br>
>> > follow<br>
>> > that example. We can leverage initiatives like Google Code. We can try<br>
>> > crowd<br>
>> > funding. We can apply for grants, as we have been doing sometimes<br>
>> > successfully. We can keep lowering the barriers for volunteers, we have<br>
>> > been<br>
>> > making great progress on that. We can finally solve the un-marketability<br>
>> > issue, attracting attention and energies and hence hopefully<br>
>> > contributions.<br>
>><br>
>> Google Code In starts on Nov. 18. But we can keep adding tasks over<br>
>> the course of the contest. Please don't be shy about suggesting tasks.<br>
>> And we could also use a few more mentors.<br>
><br>
><br>
> I don't think I'm able to commit to be an "official" mentor but, as usual,<br>
> I'll be answering as many questions as possible in irc/mailing lists when I<br>
> am around.<br>
><br>
> Sort of thinking to puth GConf -> GSettings on the list... And Wayland<br>
> support but that's probably too complex for GCI.<br>
<br>
</div>GConf to GSettings is definitely GCI caliber introductory task worthy.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Walter Bender<br>
Sugar Labs<br>
<a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Daniel Narvaez<br>
</div>