Category:Contributed code: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
An index of documentation pages about contributed code. | An index of documentation pages about contributed code. | ||
Contributed code, or "contrib" for short, is understood to be all code contributed to Moodle which is not included in the standard Moodle distribution. | Contributed code, or "contrib" for short, is understood to be all code contributed to Moodle which is not included in the standard Moodle distribution. The standard Moodle distribution, sometimes known as "Core" code is the code stored and developed at [http://git.moodle.org/gw?p=moodle.git;a=summary git.moodle.org]. | ||
Contributed code is usually managed by the developer of the plugin or patch; however, as people change jobs or move on for whatever reason others can volunteer to step in to serve as the primary maintainer of a contribution. | |||
The code is hosted on a the version control system (VCS) of the developers choice. Previously, CVS was used for both [http://cvs.moodle.org/moodle/ core Moodle code] and [http://cvs.moodle.org/contrib/ CONTRIB code]. Git is now the preferred VCS for both Moodle core and CONTRIB code. There are various Git repositories; however, the most commonly used Git repository is [http://github.com/ Github.com]. | |||
Developers of CONTRIB code can create their own publicly accessible Git repository of the code (for an example see https://github.com/moodlehq/). Plugins typically use the following naming convention: moodle-{type}_{name} so that the book activity module would be named moodle-mod_book. Developers are encouraged to be consistent. | |||
At the moment, all CONTRIB code (and core code) should be indexed in the [http://moodle.org/mod/data/view.php?id=6009 Modules and plugins database]. That said, work is being done to create a new Plugins database that will allow much more flexibility in how CONTRIB code is shared and reviewed. Those interested can follow that work at [http://tracker.moodle.org/browse/MDLSITE-571 MDLSITE-571]. | |||
Anthony Borrow, the CONTRIB Coordinator, is happy to answer any questions related to CONTRIB code and will help direct folks to the appropriate developer. Feel free to contact the CONTRIB Coordinator via Moodle message. | |||
==See also== | ==See also== |
Revision as of 08:17, 14 June 2011
An index of documentation pages about contributed code.
Contributed code, or "contrib" for short, is understood to be all code contributed to Moodle which is not included in the standard Moodle distribution. The standard Moodle distribution, sometimes known as "Core" code is the code stored and developed at git.moodle.org.
Contributed code is usually managed by the developer of the plugin or patch; however, as people change jobs or move on for whatever reason others can volunteer to step in to serve as the primary maintainer of a contribution.
The code is hosted on a the version control system (VCS) of the developers choice. Previously, CVS was used for both core Moodle code and CONTRIB code. Git is now the preferred VCS for both Moodle core and CONTRIB code. There are various Git repositories; however, the most commonly used Git repository is Github.com.
Developers of CONTRIB code can create their own publicly accessible Git repository of the code (for an example see https://github.com/moodlehq/). Plugins typically use the following naming convention: moodle-{type}_{name} so that the book activity module would be named moodle-mod_book. Developers are encouraged to be consistent.
At the moment, all CONTRIB code (and core code) should be indexed in the Modules and plugins database. That said, work is being done to create a new Plugins database that will allow much more flexibility in how CONTRIB code is shared and reviewed. Those interested can follow that work at [https://tracker.moodle.org/browse/MDLSITE-571 MDLSITE-571].
Anthony Borrow, the CONTRIB Coordinator, is happy to answer any questions related to CONTRIB code and will help direct folks to the appropriate developer. Feel free to contact the CONTRIB Coordinator via Moodle message.
See also
Pages in category "Contributed code"
The following 200 pages are in this category, out of 318 total.
(previous page) (next page)A
- Accessibility Block
- Active Forums block
- ad-hoc contributed reports
- Add-ons
- Adding/editing a hotpot
- Admin alert block
- Admin presets block
- Admin Report Roles capabilities
- admin/setting/blocksettingslideshow
- admin/setting/themesettingaigne
- Adminer
- Adobe Connect block
- Ajax marking block
- Algebra question type
- All or nothing multiple choice question type
- Analytics Recommendations block
- Anonymous posting plugin
- Attendance module
- Attendance module requests
- Atto Word import
- AuthMoodle
- Autoattendance block
- Autoattendance module
- Availability dataformcontent
B
C
- Calculated Objects question type
- Capabilities/block/email list:createfolder
- Capabilities/block/email list:editsettings
- Capabilities/block/email list:sendmessage
- Capabilities/mod/certificate:manage
- Capabilities/mod/certificate:printteacher
- Capabilities/mod/project:create
- Certificate module
- Cloze editor module
- Collapsed Topics course format
- Combined question type
- Concept map question type
- Correct writing question type
- Course checks block
- Course contents block
- Course Management block
- Course Menu block
- Course Publishing block (publishflow)
- Course rate block
- course/view/slides
- Creating a pcast
- Criteria reference block
- Custom SQL queries report
D
- Dashboard Block
- Dataform Activity administration
- Dataform Activity navigation
- Dataform Applications
- Dataform building
- Dataform capabilities
- Dataform Entries
- Dataform entry access block
- Dataform FAQ
- Dataform field access block
- Dataform Grading
- Dataform Import Export
- Dataform installation
- Dataform Manage Access
- Dataform Manage CSS
- Dataform Manage Fields
- Dataform Manage Filters
- Dataform Manage Javascript
- Dataform Manage Notifications
- Dataform Manage Presets
- Dataform Manage Views
- Dataform module
- Dataform notification block
- Dataform Notifications
- Dataform Overview
- Dataform Photo Galleries
- Dataform Plugins
- Dataform releases
- Dataform search sort
- Dataform settings
- Dataform setup
- Dataform Site settings
- Dataform System events
- Dataform Tests
- Dataform view access block
- Dataform view block
- Dataform view module
- Dataform Workflow
- Dataformfield checkbox
- Dataformfield commentmdl
- Dataformfield duration
- Dataformfield entryactions
- Dataformfield entryauthor
- Dataformfield entrygroup
- Dataformfield entrystate
- Dataformfield entrytime
- Dataformfield file
- Dataformfield number
- Dataformfield picture
- Template:Dataformfield plugin info
- Dataformfield radiobutton
- Dataformfield ratingmdl
- Dataformfield select
- Dataformfield selectmulti
- Dataformfield text
- Dataformfield textarea
- Dataformfield time
- Dataformfield url
- Dataformview Aligned
- Dataformview chart
- Dataformview CSV
- Dataformview Grid
- Dataformview Interval
- Dataformview PDF
- Template:Dataformview plugin info
- Dataformview RSS
- Dataformview Tabular
- Datalynx Calculations
- Datalynx create
- Datalynx CSV view
- Datalynx Fields
- Datalynx Filter, Search and Sort
- Datalynx global settings
- Datalynx Grid view
- Datalynx installation
- Datalynx JavaScript, CSS
- Datalynx module
- Datalynx Notifications
- Datalynx PDF view
- Datalynx permissions
- Datalynx settings
- Datalynx Statistics
- Datalynx Tabular view
- Datalynx Tags
- Datalynx View settings
- Datalynx Views
- Days course format
- Decaf theme
- Development:Dialogue 2.0 specification
- Dialogue module
- Drag and drop image or text question type
- Drag and drop into text
- Drag and drop marker question type
- Drag and drop matching question type
- Drag and drop onto image question type
- Drag and drop organic chemestry nomenclature question type