Leopold,

Many thanks for sharing this plugin with the Moodle community.

In order to review this plugin, the version(s) of Moodle for which it is intended needs to be specified. You can find this by navigating to the plugin, going to the Download versions tab, and clicking on the Edit details link for the most recent version. Under the Supported and/or required software section, select the Moodle versions for which that particular version of the plugin is designed to work with and then Save changes.

I noticed that you did not specify an issue tracker for your plugin. Providing a place for users of your plugin to report issues encourages participation and provides a way for users to report bugs, make feature requests, or suggest other types of improvements.

There are a couple of options. You are welcome to request that a component be created in the Moodle Tracker. This will allow for you to become more familiar with how issues are managed in Moodle core but may take a little more time to setup. Alternatively, for folks like yourself who are using Github.com, you can use the issues feature of Github to handle such requests. Kindly let me know which of these two options seems best for you.

For now, I am going to mark this plugin as needing more work until we get these issues resolved. Thanks for your patience with the review and approval process. Please do not hesitate to let me know if there is anything I can do to be supportive of your efforts.

Peace - Anthony

p.s. Please provide a documentation URL. You are welcome to create your documentation in Moodle Docs, See http://docs.moodle.org/dev/Plugin_documentation for more information.

Please consider adding a screenshot of your plugin to help folks get an idea of what it looks like when installed.

Dear Anthony,

Thank you very much for the instant review and helpful comments!

Since you were so quick to answer after I submitted the plugin, I am starting to wonder whether you received my email from March 29th. So, I am going to try my luck here on the board.

- I have now specified the Moodle versions that I tried out with the
plugin.
- I am going to use the ‘issues’ tracker on github as you suggested and I
have updated the corresponding link.
- I have created a wiki page for the documentation on
http://docs.moodle.org/en/qformat_qtex.
Once the plugin is published, I can also open a discussion thread in the
general add-ons section.
- I have added two screenshots meant to illustrate the purpose of the
plugin.

During preparation of the screenshots I realized a bug in the version I
uploaded ;)
If possible, I would like to update the .zip file to v0.1.1 before
publishing.

Finally, I have a question - did I now contribute a plugin or an add-on?

Best regards,
Leopold

Hi Leopold,
Thanks for your email to me.
If you have a quick read through http://docs.moodle.org/dev/Plugin_validation#The_process

The document describes the review process, your plugin is in 'Needs more work' at the moment.
I can confirm the system sent out email notification to me ("Subj:Plugin approver's notification: QuestionTeX format"). I presume Anthony did too.
This process works best when a plugin that is ready for another review is rescheduled for approval. The section linked in the doc link above states how to.
Rescheduling it for approval puts the plugin onto our 'needs a review' radar , so that works best. We do try to respond to the 'needs more work' status plugins however the 'waiting for review' takes priority.

I've now added a note (3) to https://moodle.org/plugins/registerplugin.php to further highlight this.

I'll move yours now along in the process.

Thanks for contributing this Add-on Leo
I've looked through it and just two minor notes that you might look into improving in future:
- https://github.com/leoteo/moodle-qformat_qtex/tree/master/qtex is the actually root of the plugins source, this could be clarified.
- qtex/examples/ex02-images.zip is in your plugin as well as your git. I've confirmed it contains images, however its preferred that there aren't multiple zips within the zip. This is to allow easier visibility of contents (security) for everyone. Double zips don't add any compression benefit.

ps : Installation ran fine

pps: some warnings seen -
'Strict Standards: Declaration of qformat_qtex::readquestion() should be compatible with qformat_default::readquestion($lines) in /Users/aparup/git/stable_26/question/format/qtex/format.php on line 2124' and on the same page..
'Declaration of qformat_qtex::readquestion() should be compatible with qformat_default::readquestion($lines)'
'Warning: Illegal string offset 'text' in /Users/aparup/git/stable_26/question/type/questiontypebase.php on line 1090
Notice: Uninitialized string offset: 0 in /Users/aparup/git/stable_26/question/type/questiontypebase.php on line 1090'

Thanks, i think this is awesome how it helps importing more questions! Feel free to add a video !

Dear Aparup,

Thanks a lot for helping me out! I knew that I must have been missing something.

I have updated the Source control URL as you suggested.
As for the .zip file inside the git repository - if users include images in their LaTeX questions, uploading a zip file is the only way how they can provide both the .tex file and the images at the same time. I would therefore prefer to keep the .zip file (which just an example of how to use the plugin).

The strict warnings you mentioned will be addressed in a future release.

Thanks a lot,
Best regards,
Leopold