Sascha, Speaking as a teacher, this workflow seems really good. Gerald <div class="gmail_quote">On Fri, Apr 23, 2010 at 7:49 AM, Sascha Silbe <<a href="mailto:sascha-ml-ui-sugar-iaep@silbe.org">sascha-ml-ui-sugar-iaep@silbe.org</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">On Fri, Apr 23, 2010 at 11:18:14AM +0200, Tomeu Vizoso wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> On Fri, Apr 23, 2010 at 02:08, Gonzalo Odiard <<a href="mailto:godiard@gmail.com" target="_blank">godiard@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> In the context of Sugar we need a simple way to students to send their work to the teacher and a simple way to the teacher to group these works, and follow the progress. Can we start with it? </blockquote> You mean something that works without a server such as Moodle? If so, I think we should start by thinking who is going to review and stabilize that work, as we are getting very short of maintainers. </blockquote> Maybe we should start by designing a work flow / UI for this? I believe the actual code changes could be fairly small and easily reviewed if done right. If we transfer metadata during "file transfer" (Journal "Send To" feature) as suggested in #1344 [1], we have everything needed for the most basic workflow: 1. Student opens completed work in Journal details view. 2. Student adds tags as instructed by the teacher (e.g. "Class-6a homework bees"). 3. Student uses "Send To <name of teacher>". 4. Teacher accepts file transfer. 5. Teacher opens Journal and uses full text search with the given tags. 6. Teacher annotates the work (either inline or (ab)using the "description" field). 7. Teacher uses "Send To <name of student>". 8. Student accepts file transfer. There are obviously quite a few ways to improve on this workflow, but we can get there step by step with incremental, self-contained changes that are easy enough to review. [1] <a href="https://bugs.sugarlabs.org/ticket/1344" target="_blank">https://bugs.sugarlabs.org/ticket/1344</a> CU Sascha -- <a href="http://sascha.silbe.org/" target="_blank">http://sascha.silbe.org/</a> <a href="http://www.infra-silbe.de/" target="_blank">http://www.infra-silbe.de/</a> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJL0YlXAAoJELpz82VMF3DaCfkH/1ZEPp9HBAmg98TjuwbQZtT1 ZTMEXchIGEWl2ZoTJj0+B5s5v1/6fkTsA2YgfC8E2NizL0xowrv+VmpNkNE3yarw nlyhPVfRgWqSdQa39ux+O2pWv+dWX5dgLd2R653t6/8tdsgOaNLtEQT1iL10kLg4 K6ht4QzK7xNN5aMRhHOezMcmG2U8vhMBAhxb1P2gP2ESrWtGTSnqqjmeRy3S4qr4 EVyDysnX94BNQqjsNkk2qjCceQt5R/Dzdpk9eeJT4ipfc+zRpF+DXJNvY/LlE6Zv uEzFNEP2IlshBHVFoevDhGI3r/rAKpFY1R2siL9W+0RTryXXwpneQ4gPS7k+yPA= =EHSi -----END PGP SIGNATURE----- _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a> </blockquote></div>