<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
While supporting a new file type might seem like a big thing I decided<br>
it was worth doing since it would provide interoperability with other<br>
software such as Moodle etc. However, I had trouble narrowing down<br>
decent use cases for the software and so I think I was trying to make<br>
it do too much. I think KEduca really needs some well-defined goals,<br>
use cases and expected work-flows as well as reasons why it is<br>
preferred over other software such as Moodle. We need to know where it<br>
fits in the software landscape. Without this, it is impossible to be<br>
able to plan which features should be added.<br></blockquote><div><br>Good explanation. I think this is one of the reasons the porting effort needs to be approached with care and planning, and plenty of time available.<br>
</div><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"><br>
> KEduca ships by default in the KDE 3.5.9 based Linux Educacional distro,<br>
> delivered to thousands of schools by the Brazilian government.<br>
> (<a href="http://piacentini.livejournal.com/7871.html" target="_blank">http://piacentini.livejournal.com/7871.html</a>). So its user base is actually<br>
> increasing, which is a problem as these people will get orphaned soon (next<br>
> year) when Linux Educacional finally makes the switch to KDE 4.x.<br>
<br>
</div>For this reason, a raw port alone must be achieved somehow.<br><div class="im"></div></blockquote><div><br>..</div><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"><br>
</div>Give the experience I had, I think that finding someone to do an<br>
almost direct port to KDE4 without adding any new features would be<br>
the best way. It's a simple enough codebase that a full direct port is<br>
well within the scope of GSoC with perhaps even potential for much<br>
cleanup and code simplification.<br>
<br>
Once the port is done, then work could start on adding fancy new features.<br>
<div class="im"></div></blockquote><div><br>That is why I mentioned it needs to be something that starts as a GSoC, but needs to be carried on for at least a couple of KDE releases. Otherwise we will end up with another orphan...<br>
</div><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"> </div>I am willing to help be a mentor for this but I am not sure I have the<br>
time to do it by myself. If someone would be willing to co-mentor with<br>
me then I will be able to help.<br><br></blockquote><div><br>OK, let us wait a bit more for opinions. I think the time commitment for the mentor is inversely proportional to the experience of the student with KDE technology. In this case your guidance would probably be needed more at the planning phase, so we could learn from what was already tried and see what worked, and not very much at the actual coding/KDE integration.<br>
<br>Regards,<br>Mauricio Piacentini <br></div></div><br>