#2467 NORM Trial-3: UI for registration

[Zarro Boogs per Child]

#2467: UI for registration
---------------------+------------------------------------------------------
  Reporter:  cscott  |       Owner:  Eben    
      Type:  defect  |      Status:  assigned
  Priority:  normal  |   Milestone:  Trial-3 
 Component:  distro  |     Version:          
Resolution:          |    Keywords:          
  Verified:  0       |  
---------------------+------------------------------------------------------
Changes (by Eben):

 * cc: krstic (added)
  * status:  new => assigned

Comment:

 I think that making registration an option within the secondary rollover
 for the school server is a good idea, in general.  From a user experience
 perspective, we should prevent the need for offering an "unregister"
 option, if possible.  Registering with one would implicitly unregister it
 with the previous one.  This may require some direct contact between
 school servers, or through a higher authority. (Since Ivan wants to track
 each laptop anyway, we may already be needing the change in registration
 info at a higher level anyway)

 Now, as far as the school server goes, it seems we ''may'' need to
 visually identify it within the UI differently than other access points.
 We proposed this at one point and chose not to for simplicity, but it may
 be important if it's required for special functionality.

 As far as auto-registration goes, it's a good thing as long as we can make
 it dependable and deterministic.  What kinds of circumstances could we
 encounter?  Multiple servers in one school?  Multiple servers for nearby
 schools?  Are both of these a problem, or only the latter?  Perhaps we can
 eliminate the need to manually register assuming only one server is
 located, and leave it up to human intervention when an explicit choice
 must be made.  Whatever we do, the more we can do without the need for
 interaction, the better.

-- 
Ticket URL: <http://dev.laptop.org/ticket/2467#comment:1>
One Laptop Per Child <http://laptop.org/>