forked from gitlabhq/gitlabhq
-
Notifications
You must be signed in to change notification settings - Fork 0
Module Proposals and Requirements
ariejan edited this page May 23, 2012
·
1 revision
There is talk about making Gitlab more modular in order to better select functionality needed by different people.
Before we go out and re-write Gitlab to be entirely modular I'd like to gather information about what modules are planned/proposed, and more importantly, what they'd need from Gitlab to function properly.
Please copy the following template and let us know what you'd need from Gitlab to write a successful module.
My module will do this and that and allow users to be 200% more productive.
- What does your module need from Gitlab?
- Does it require hooks? If so, where?
- Does it require an API? If so, what?