Git Migration Workflows

Quite a number of developers are now familiar with git and are enthusiastic about the power and flexibility it brings to the development process. It is not clear how workflows in the current development process will transfer if a switch to git is made.

Git doesn't place constraints to one model of development which is both a feature and a hindrance for people understanding how the development process takes place. A number of workflows need to be developed in order that developers can understand how git would fit into moodle development.

Please edit this page to add your suggested workflows or questions for a workflow to do something.

General Model for Commiting to HEAD

Summary: How do developers 'commit' to the canonical repository?

• Developers 'push' to a central repository as happens with CVS now. Commit access is granted via ssh. (But external contributors can publish their git repository branches to developers with commit access for inclusion to the mainline)
• Developers push to their personal repository and an integrator/gatekeeper approves and merges changes (e.g. linus kernel branch)
• Others/hybrid approaches?

Commiting to STABLE branches

Summary: How do developers commit to the stable branches? How do we ensure changes have been merged into head?

Customizing a CONTRIB plugin

Summary: This suggested workflow can be used by developers who are working on a customization or a fix of a contributed Moodle plugin. You want to keep the track of your local changes and eventually send some of you changes back to the upstream.