Last modified: 2014-11-20 15:20:16 UTC
We should create a extension to show infos about a Moodle course. Sumana suggested to create a mentorship programm for this. I have added a programm for this: https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#MediaWiki-Moodle_extension I hope that some student are interested to work on this.
Hello Jan Luca, I am a student interested in GSoC and your project. I have previously worked with moodle. I am wondering if we could get into contact about this extension. Cheers, Rohan
Just a note to say that Rohan Verma has submitted a GSoC proposal related to this report: https://www.mediawiki.org/wiki/User:Clancer Good luck!
Just adding that for my proposed work, linked above by Quim, I will be using the gerrit repository: https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Moodle I have started research into using moodle webservices and will hopefully be able to start testing a basic extension this week. I have a question some example scripts to use Moodle webservices require curl to be included. Is it ok to simply include a copy of curl.php in my extension or does mediawiki have a specific way I should do this?
Hi Rohan, there are the classes "Http" and "MWHttpRequest" to do this. You can find the source code with documentation here: https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;f=includes/HttpFunctions.php;hb=HEAD Best regards, Jan
GSoC "soft pencils down" date was yesterday and all coding must stop on 23 September. Has this project been completed?
If you have open tasks or bugs left, one possibility is to list them at https://www.mediawiki.org/wiki/Google_Code-In and volunteer yourself as mentor. We have heard from Google and free software projects participating in Code-in that students participating in this programs have done a great work finishing and polishing GSoC projects, many times mentores by the former GSoC student. The key is to be able to split the pending work in little tasks. More information in the wiki page. If you have questions you can ask there or you can contact me directly.
(In reply to comment #6) > We have heard from Google and free software projects participating in Code-in > that students participating in this programs have done a great work finishing > and polishing GSoC projects, many times mentores by the former GSoC student. > The key is to be able to split the pending work in little tasks. The extension has no merged patches yet. For that, at the very least the initial one should be merged first, I guess (Jan?). https://gerrit.wikimedia.org/r/#/c/75109/5 It doesn't seem so reasonable for google code-in tasks to include e.g. function documentation amendments of open patches, but who knows.
(In reply to comment #7) > (In reply to comment #6) > > We have heard from Google and free software projects participating in Code-in > > that students participating in this programs have done a great work finishing > > and polishing GSoC projects, many times mentores by the former GSoC student. > > The key is to be able to split the pending work in little tasks. > > The extension has no merged patches yet. For that, at the very least the > initial one should be merged first, I guess (Jan?). > https://gerrit.wikimedia.org/r/#/c/75109/5 > It doesn't seem so reasonable for google code-in tasks to include e.g. > function > documentation amendments of open patches, but who knows. I agree that this extension would not be good for google code in. ---- I merged said patches, since gsoc over, and we should integrate work done in the repo (Trying to develop entire extensions in a single gerrit patch never works well anyways)
So things that were brought up on code review that have yet to be done: *inappropriate use of globals $wgUser *Needing to use Doxoygen comments *$dbw->begin(); and $dbw->commit(); arround things that don't need to be in a transaction There's also other obvious things *Still testing code in with in *Extension is functionally incomplete *Use $wgExtensionAliasesFiles to include the alias file *There's some example code that is copied verbatim, which needs to modified.
But maybe some of these tasks are indeed potential GCI candidates? We don't need to put the responsibility of finishing the extension to GCI students but maybe we could promote some obvious (for an experienced contributor) tasks that would get us closer to a RESOLVED FIXED. Rohan, what do you think? Would you like to help mentoring some of these tasks? Other former GSoC students are volunteering as GCI mentors now. Any other takers?
Rohan: Could you please answer comment 10?
Rohan Verma: Could you please answer comment 10? Also, I am resetting the assignee of this issue to default because there has been no signs of progress for the last months. Feel free to assign it to yourself again when you plan to work on this. Thanks for your understanding.
