<div dir="ltr"><div>Apart from on a flat network, we are not going to solve the problem of working on "corporate-style" school networks using Avahi. That presumes you can get multicast support working across the desired region.<br>
<br></div><div>The equivalent for larger networks would be DNS service records, presuming you can get permission to create them.<br></div><div><br></div>Without going into whom is doing what, I personally know that Sugar is being used:<br>
<ul><li>On networks where DHCP is controlled by centralized IT.</li><li>Where the schoolserver's DNS name has to match an existing naming scheme.</li><li>Where there is no DNS hierarchy, so computers at every school are named like <a href="http://computer-xyz.example.edu">computer-xyz.example.edu</a><br>
</li><li>Where various forms of wireless authentication (PSK, 802.11x, etc.) are required for wireless access, and the students are not supposed to know the password.<br><br></li><li>Where the schoolserver is required to be in the School District's central datacenter.</li>
<li>Where a single schoolserver has to support more than one school.<br></li><li>Where a single network IP address range is used by multiple schools spaced several miles apart.</li></ul><p>Some might think that these are insane network setups. But when you get into larger organizations things like this become the norm.<br>
</p><p>Teaching Sugar to use these sorts of resources instead of a hardcoded name should not be that hard. The catch is there are a lot of historical places which independently have hardcoded this name.</p><p>I may toss out some design proposals on Sugar-devel later this weekend to address some of these. I think the basics should be simple enough to be GCI tasks.<br>
</p></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 29, 2013 at 7:48 AM, Jerry Vonau <span dir="ltr"><<a href="mailto:jvonau@shaw.ca" target="_blank">jvonau@shaw.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I agree that deployment on preexisting networks has not really been given any attention given the long standing issues that have been ticketed in the past[1][2]. I like the idea of using avahi to advertise the "schoolserver's" services offered, just need to address the sugar side[3][4]. The changes would entail both a change to the server side and the sugar client side, that is outside of the scope of just "schoolserver" and is part of "sugar"-land.<br>
<br>
I don't think the documentation of the XSCE is any better or worse than what is provided for the XS-0.7 but there is always room for improvement.<br>
<br>
Jerry<br>
<br>
<br>
1. <a href="http://dev.laptop.org/ticket/11775" target="_blank">http://dev.laptop.org/ticket/11775</a><br>
2. <a href="http://dev.laptop.org/ticket/12156" target="_blank">http://dev.laptop.org/ticket/12156</a><br>
3. <a href="http://dev.laptop.org/ticket/8499" target="_blank">http://dev.laptop.org/ticket/8499</a><br>
4. <a href="http://bugs.sugarlabs.org/ticket/1976" target="_blank">http://bugs.sugarlabs.org/ticket/1976</a><br>
<div class="im"><br>
----- Original Message -----<br>
From: "Samuel Greenfeld" <<a href="mailto:samuel@greenfeld.org">samuel@greenfeld.org</a>><br>
To: "James Cameron" <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>>, "Anish Mangal" <<a href="mailto:anish@activitycentral.com">anish@activitycentral.com</a>>, "server-devel" <<a href="mailto:server-devel@lists.laptop.org">server-devel@lists.laptop.org</a>><br>
Sent: Friday, 29 November, 2013 4:10:03 AM<br>
Subject: Re: [Server-devel] Feedback: Problems with XSCE<br>
<br>
<br>
<br>
<br>
<br>
<br>
I think you need to be careful how you phrase that -- you just half implied that all <a href="http://laptop.org" target="_blank">laptop.org</a> hosting is going away. There has been a fair amount of fear that resources may suddenly disappear, and I have been concerned about fragmentation where hosting of resources ends up all over the place.<br>
<br>
<br>
If there is a perceived need to migrate resources then that should be made clear, as others have already offered potential alternative hosting. But there needs to be coordination.<br>
<br>
<br>
Focusing on the Deployment side, I would tend to agree with John's comments as well.<br>
<br>
Both Sugar and the Schoolserver have been historically focused on being their own ecosystem. This has never changed, yet Sugar and the XS are often offered for use where existing DHCP, DNS, and other services already exist.<br>
<br>
<br>
Due to local policies, you may not be allowed to name your schoolserver "schoolserver". You may have to support 802.11x network authentication, etc. It is possible to kludge these but the solutions are not elegant.<br>
<br>
<br>
If the Sugar and XSCE communities feel that the "enterprise"/first-world use case is a desired scenario where Sugar, IIAB, and/or Moodle may only be a part of a school's network instead of the primary role, then this specifically needs to be targeted.<br>
<br>
---<br>
<br>
SJG<br>
<br>
<br>
<br>
<br>
<br>
On Fri, Nov 29, 2013 at 3:33 AM, James Cameron < <a href="mailto:quozl@laptop.org">quozl@laptop.org</a> > wrote:<br>
<br>
<br>
I agree with John. Every point in his documentation section should be<br>
</div>handled. Especially the point about <a href="http://wiki.laptop.org" target="_blank">wiki.laptop.org</a> , which has so<br>
<div class="HOEnZb"><div class="h5">many distracting links on the navigation bar that we are all used to,<br>
but which new people become lost in.<br>
<br>
With regard to forums, the type that Google Groups has where they can<br>
also be received in mail may suffice.<br>
<br>
<br>
<br>
On Fri, Nov 29, 2013 at 11:44:33AM +0530, Anish Mangal wrote:<br>
> Hi,<br>
><br>
> I would like to share this blog post from John Ellis with the XSCE community:<br>
> John is a high school student who is trying to setup XSCE in his class/school<br>
> under the supervision of his teacher Jeff Elkner.<br>
><br>
> <a href="http://johnmichaelffs.blogspot.in/2013/11/problems-with-xsce.html" target="_blank">http://johnmichaelffs.blogspot.in/2013/11/problems-with-xsce.html</a><br>
><br>
> Some of the stuff he points out certainly makes a lot of sense to me, I think<br>
> the core underling message is to make XSCE more approachable to the end user<br>
> and the advanced end-user/deployer. He has gone to some lengths to point out<br>
> specific aspects which could be improved.<br>
><br>
> As we think about the possibilities for XSCE-0.6, I would like to further the<br>
> discussion along these topics here and/or on IRC. I think the project could do<br>
> well listening to end users' needs for the 0.6 cycle, especially that we now<br>
> seem to have our house in order codewise thanks to the terrific work by all the<br>
> software hackers here :-)<br>
><br>
> Thoughts?<br>
><br>
> Cheers,<br>
> Anish<br>
><br>
><br>
><br>
<br>
> _______________________________________________<br>
> Server-devel mailing list<br>
> <a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
> <a href="http://lists.laptop.org/listinfo/server-devel" target="_blank">http://lists.laptop.org/listinfo/server-devel</a><br>
<br>
<br>
--<br>
James Cameron<br>
<a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a><br>
_______________________________________________<br>
Server-devel mailing list<br>
<a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/server-devel" target="_blank">http://lists.laptop.org/listinfo/server-devel</a><br>
<br>
<br>
_______________________________________________<br>
Server-devel mailing list<br>
<a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/server-devel" target="_blank">http://lists.laptop.org/listinfo/server-devel</a><br>
</div></div></blockquote></div><br></div>