Just to remind the list about this guidance that I think is very useful and mentions pootle, collaboration, etc.<br><br><a href="http://wiki.sugarlabs.org/go/Activity_Library/Editors/Policy"> http://wiki.sugarlabs.org/go/Activity_Library/Editors/Policy</a><br>
<br><div class="gmail_quote">On Wed, Jul 13, 2011 at 2:50 PM, Sameer Verma <span dir="ltr"><<a href="mailto:sverma@sfsu.edu">sverma@sfsu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, Jul 13, 2011 at 3:27 AM, Gonzalo Odiard <<a href="mailto:gonzalo@laptop.org">gonzalo@laptop.org</a>> wrote:<br>
> Yes.<br>
> Also, we must recommend working more in the open, I don't know why, but in<br>
> particular students in universities<br>
> are very reluctant to integrate to the community, and are happy dropping a<br>
> "finished" product without interaction.<br>
><br>
> Gonzalo<br>
><br>
<br>
</div>A lot of it has to do with motivation. Students typically pick up a<br>
project because they have a requirement, and may be passionate about<br>
the work at that moment, but needs of looking for a job, working on<br>
other course assignments etc. will quickly supersede their original<br>
project direction. The reluctance of integrating with the community<br>
stems from the requirements of the project (schedule/deliverables are<br>
course driven) and a usual lack of understanding of how FOSS projects<br>
work. Once the university requirement is satisfied, their motivation<br>
to continue typically goes away. However, if we are able to inculcate<br>
in these students, a desire for working on these projects while they<br>
are in the course, and integrate them into the community, then there<br>
is hope of continued work.<br>
<br>
cheers,<br>
Sameer<br>
--<br>
Dr. Sameer Verma, Ph.D.<br>
Associate Professor, Information Systems<br>
Director, Campus Business Solutions<br>
San Francisco State University<br>
<a href="http://verma.sfsu.edu/" target="_blank">http://verma.sfsu.edu/</a><br>
<a href="http://opensource.sfsu.edu/" target="_blank">http://opensource.sfsu.edu/</a><br>
<a href="http://cbs.sfsu.edu/" target="_blank">http://cbs.sfsu.edu/</a><br>
<a href="http://is.sfsu.edu/" target="_blank">http://is.sfsu.edu/</a><br>
<div><div></div><div class="h5"><br>
<br>
> On Wed, Jul 13, 2011 at 5:37 AM, James Simmons <<a href="mailto:nicestep@gmail.com">nicestep@gmail.com</a>> wrote:<br>
>><br>
>> I like the idea of giving certificates, but I think we should take the<br>
>> opportunity to enforce some simple best practices, like requiring a toolbar,<br>
>> requiring Share and Keep buttons to be hidden if they aren't used, requiring<br>
>> a proper icon for the Activity, etc.<br>
>><br>
>> It might be nice to have two levels of certificate. Since shared<br>
>> Activities are more difficult to develop, maybe we have a separate<br>
>> certificate for those.<br>
>><br>
>> James Simmons<br>
>><br>
>><br>
>> On Wed, Jul 13, 2011 at 2:53 AM, Martin Dengler <<a href="mailto:martin@martindengler.com">martin@martindengler.com</a>><br>
>> wrote:<br>
>>><br>
>>> On Tue, Jul 12, 2011 at 06:11:31PM -0400, Chris Ball wrote:<br>
>>> > Hi,<br>
>>> ><br>
>>> > On Tue, Jul 12 2011, Walter Bender wrote:<br>
>>> > > Can we discuss this? I think it would be good to have a certificate<br>
>>> > > program of some sort. I image that if we get sign-off by 2+<br>
>>> > > experienced developers, we should be willing to award some sort of<br>
>>> > > certificate (perhaps we can get the design team to work something<br>
>>> > > up.)<br>
>>> ><br>
>>> > Perhaps we could tie the certificate-awarding to posting an activity on<br>
>>> > ASLO and getting a review from someone on the Activity Team or<br>
>>> > something?<br>
>>><br>
>>> Perhaps even prominent reviewers on ASLO (are there any?). Either way<br>
>>> it's more sustainable and honest than herding developers to sign off<br>
>>> on certificates.<br>
>>><br>
>>> > Thanks,<br>
>>> ><br>
>>> > - Chris.<br>
>>><br>
>>> Martin<br>
>>><br>
>>> _______________________________________________<br>
>>> IAEP -- It's An Education Project (not a laptop project!)<br>
>>> <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
>>> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> IAEP -- It's An Education Project (not a laptop project!)<br>
>> <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
>> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
><br>
><br>
> _______________________________________________<br>
> IAEP -- It's An Education Project (not a laptop project!)<br>
> <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
><br>
_______________________________________________<br>
IAEP -- It's An Education Project (not a laptop project!)<br>
<a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
</div></div></blockquote></div><br>