Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.9, 1.9.1
-
Fix Version/s: None
-
Component/s: Block: Quickmail
-
Labels:None
-
Affected Branches:MOODLE_19_STABLE
Description
There are few items for this to-do list.
1. Create an folder on contrib for /contrib/plugins/blocks/quickmail_for_large_classes
2. Assign Wen to have read/write access to both /contrib/plugins/blocks/quickmail_for_large_classes and the /contrib/plugins/blocks/quickmail folder
3. Change the moodle Tracker Components from "Module: Quickmail" to "Block: Quickmail" (Quickmail should be a block, not a module), also create a component called "Block:Quickmail_for_large_classes", please
4. If people create a Trac ticket and select component for "Block:Quickmail_for_large_classes", please set it up that it will automatically assign to me (by default), and hopefully I will receive a email. If ppl create a Trac ticket and select component for "Block:Quickmail", could you please see if it's possible that it will by default still assign to Mark Nielson, but also cc me on email? This way I could "co-maintain" this block (quickmail) with Mark, and if Mark doesn't have time to fix something, then I could be kept in the loop and could maybe help fixing/patching it.
4. Please also link the /contrib/plugins/blocks/quickmail_for_large_classes to http://moodle.org/mod/data/view.php?d=13&rid=764
That's it, thanks!
Issue Links
| This issue has been marked as being related by: | ||||
| CONTRIB-346 | Some Bugs in original quickmail block with GROUPS |
|
|
|
Wen - As discussed, #1 is completed and I have given you access to quickmail_for_large_classes. Could you document for me here the history of the quickmail folder (i.e. who contributed it, who is maintaining, etc.). Before I give you access to it I want to make sure we are not stepping on anyone's toes. Ideally I would think that was is good for large classes is also good for smaller classes; however, you might have more information about that (is it related to groups and some of the other things you mentioned). In any case, it would help me to have the history spelled out here as a reference. I did change the component names to reflect that they are blocks (not modules). I created a component for the large classes and you will be automatically assigned any issues created for that component so we can check #3 and #4 off the list. As for 4b - I'm not sure what you mean about the link? Where would you like the link to the M&P entry? Peace - Anthony