− | * Has anyone every written a bot to export an IRC channel to Twitter or Facebook? It might to increase the reach of the discussion to a new audience. | + | * Has anyone every written a bot to export an IRC channel to Twitter or Facebook? It might increase the reach of the discussion to a new audience. |
| 2. Bruce Byfield wrote an article for "Activities and the move to context-oriented desktops" for LWN.net for which he interviewed Gary Martin. The article is subscriber-only, so I have extract a few quotes. | | 2. Bruce Byfield wrote an article for "Activities and the move to context-oriented desktops" for LWN.net for which he interviewed Gary Martin. The article is subscriber-only, so I have extract a few quotes. |
| 4. Between interviews, Gary has been busy cranking out mock ups for [[Marketing_Team/Boot_Logo#Sugar_Boot_Logo_Animations|a new Sugar splash screen.]] | | 4. Between interviews, Gary has been busy cranking out mock ups for [[Marketing_Team/Boot_Logo#Sugar_Boot_Logo_Animations|a new Sugar splash screen.]] |
− | 5. All in a name: We have been have a discussion on the lists and in IRC about what to call the pending Sugar on a Stick release. The confusion lies in the gulf between the "stick", which will consist of Sugar Sucrose 0.84 and Fedora 11, both of which are essentially frozen, and the needs of a school to make a successful deployment, which includes requirements beyond the individual sticks themselves, e.g., a backup mechanism, documentation, etc. On the one hand, the developer have completed their work and are preparing to move on to the next phase: Sucrose 0.86 and Fedora 12. On the other hand, we don't want to set expectations that Sugar on a Stick is complete in regard to classroom settings, where we are only just beginning to do testing. | + | 5. All in a name: We have been having a discussion on the lists and in IRC about what to call the pending Sugar on a Stick release. The confusion lies in the gulf between the "stick", which will consist of Sugar Sucrose 0.84 and Fedora 11, both of which are essentially frozen, and the needs of a school to make a successful deployment, which includes requirements beyond the individual sticks themselves, e.g., a backup mechanism, documentation, etc. On the one hand, the developers have completed their work and are preparing to move on to the next phase: Sucrose 0.86 and Fedora 12. On the other hand, we don't want to set expectations that Sugar on a Stick is complete in regard to classroom settings, where we are only just beginning to do testing. |
| One proposed solution to this communications dichotomy is to use separate names for an individual stick and a collection of sticks used in a school setting. The best I've been able to come up with for the latter is Sugar Grove. Please share any thoughts you might have on naming with the SoaS and Marketing teams. | | One proposed solution to this communications dichotomy is to use separate names for an individual stick and a collection of sticks used in a school setting. The best I've been able to come up with for the latter is Sugar Grove. Please share any thoughts you might have on naming with the SoaS and Marketing teams. |