|
Amr - Sorry for not being clear. We have had some problems in the past with folks putting references to their own sites as a way of promoting themselves and it is not clear when folks click on a link that goes to a general website what specifically it has to do with documentation. There is no problem with maintaining documentation for various modules, patches, and plugins; however, the links to them should specifically direct the person to that documentation. For example, it would probably be less than helpful to simply direct folks to docs.moodle.org so I think the more specific we are the better. Secondly, in my role as CONTRIB Coordinator, I try to encourage folks to make use of the services provided by Moodle. I think documentation for Moodle things best maintained with Moodle Docs but recognize that sometimes folks have good reason for maintaining their own documentation. Perhaps what might work best for you would be to have a documentation page in Moodle docs and from there reference your custom support. Perhaps a better link would be http://3mro.wordpress.com/amr-hourani-moodle-support/
 . Although, you may want to check with Martin Dougiamas if it is OK to say that you offer Moodle support since Moodle is trademarked. I realize that you are applying to be a Moodle Partner; however, before that I believe there is an expectation that you get permission (if you have not already done so) from Martin in order to use the term 'Moodle support'. I think my goal is to help make the experience for the users of contributed code a consistent one so that if they need support for a bug, with to suggest improvements or new features they can interact with the developer via the tracker. If they have general questions about how to use the code, they have Moodle docs. If they want to ask a question of other users or discuss issues related to the code, they can use the Moodle.org forums. The intent is not to limit or dictate how you provide support but I do think there is value in to making the experience as consistent as possible for the users of the code. So please consider them suggestions, recommendations or guidelines. They are not intended to be rules or dictates. Does that help to clarify things? If not or if you have questions, please feel free to let me know and I'll try be of help. Peace - Anthony Amr - I sometimes tend to be a bit zealous in defending the Moodle trademark but it struck me as something that you may want to consider. I think http://docs.moodle.org/en/License
may provide some good information for you and then you can determine what you think is best. Please know that I am only here to offer suggestions and attempting to be helpful. Where and how you choose to share the files is your choice. Please know that I appreciate your generosity and all that you do in the Moodle community. I hope that circumstances will allow you to continue to contribute however you feel able and appropriate. Peace - Anthony Hi Amr,
Please, there's no need to "withdraw" ... we appreciate your contributions greatly. And yes, it does make sense to keep the discussion/download links for contributed software separate from any commercial interests you may have (as you have done) irrespective of being a Moodle Partner or not. Thank you. We will work on a forum somewhere on moodle.org for discussion of your modules. I've gone ahead and approved the Modules and Plugins entry for the enhanced message block patch . Thanks for making the links more specific. Moodle offers the forums for discussion, the tracker for issues, CVS for download, and docs for documentation. Feel free to make use of those tools as you provide support for this code. As far as names for the directory rather than calling it enhanced message block, I think I might be a little more specific and call it check_messages or even refresh_messages. If you look at the patches directory at http://cvs.moodle.org/contrib/patches/
you will see there is already: message_enhancements_hack/ and messaging_v2/. I think that might help distinguish your patch from these others. Peace - Anthony |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
Sub-task
Closed
Minor
 |
|
All content on this web site is made available under the GNU General Public License, unless otherwise stated.
all these links are temporal and will be put into CVS.