... | ... | @@ -51,7 +51,32 @@ This would add both a comment and 1 hour of time to the issue. |
|
|
|
|
|
For more information on tracking time with Gitlab as well as for using more advanced comments, [check out this resource](https://docs.gitlab.com/ee/workflow/time_tracking.html).
|
|
|
|
|
|
## Importing time contributions
|
|
|
|
|
|
Some time contributions can be difficult to log on a specific ticket, or you may be using your own time tracker.
|
|
|
|
|
|
You can also use this form:
|
|
|
https://civicrm.org/civicrm/timetrack/import
|
|
|
|
|
|
The following categories are available:
|
|
|
|
|
|
* civi/dev - CiviCRM development
|
|
|
* civi/ci - Continuous integration
|
|
|
* civi/comm - Communications
|
|
|
* civi/doc - Documentation
|
|
|
* civi/infra - Server infrastructures
|
|
|
* civi/funding - Fundraising
|
|
|
* civi/governance
|
|
|
* civi/gsoc - Google Summer of Code
|
|
|
* civi/pr - PR review
|
|
|
* civi/rel - Release management
|
|
|
* civi/security
|
|
|
* civi/website
|
|
|
|
|
|
Since these categories do not map to Gitlab issues, please enter a short comment to describe the contribution.
|
|
|
|
|
|
## Thank you, community!
|
|
|
|
|
|
CiviCRM wouldn't be where it is today without the amazing contributions of many different people and organisations around the world. It is an amazing collaborative effort and we want to thank everyone that has participated so far. Thank you!
|
|
|
|
|
|
(1) We value all contributions and recognize that all have had an impact on where CiviCRM is today. Having said that, for the purposes of recognizing current contributors, we must apply some metric to demonstrate current commitment levels. For this reason, we have chosen to value contributions with the past rolling 12 months. |
|
|
\ No newline at end of file |