| ... | @@ -57,11 +57,21 @@ Possible use of Gitlab for Extensions: |
... | @@ -57,11 +57,21 @@ Possible use of Gitlab for Extensions: |
|
|
|
|
|
|
|
# Translation
|
|
# Translation
|
|
|
|
|
|
|
|
|
https://lab.civicrm.org/development-team/translations/
|
|
|
|
|
|
|
* Currently people sometimes open issues on Transifex, where they are mostly ignored.
|
|
* Currently people sometimes open issues on Transifex, where they are mostly ignored.
|
|
|
* Could be an issue tracker equivalent to other projects in the dev-team group (for patches & support).
|
|
* Issue tracker for translation-specific issues (whether bugs in translations themselves, or bugs with translation mechanisms)
|
|
|
* Space for wiki docs.
|
|
* Space for wiki docs:
|
|
|
|
* Roadmap: https://lab.civicrm.org/development-team/translations/wikis/roadmap
|
|
|
|
|
|
|
|
# Security
|
|
# Security
|
|
|
|
|
|
|
|
* Security issues can be handled in a private Gitlab project (currently issues are in non-public JIRA issues).
|
|
* Security issues can be handled in a private Gitlab project (currently issues are in non-public JIRA issues).
|
|
|
* Possibility usable for security-related pull-requests (which Gitlab calls merge-requests), but could require changes to the continuous-integration. |
|
* Possibility usable for security-related pull-requests (which Gitlab calls merge-requests), but could require changes to the continuous-integration.
|
|
\ No newline at end of file |
|
|
|
|
|
# Google Summer of Code
|
|
|
|
|
|
|
|
https://lab.civicrm.org/community-team/gsoc2018/
|
|
|
|
|
|
|
|
* Project ideas are in markdown files in the git repository: https://lab.civicrm.org/community-team/gsoc2018/tree/master
|
|
|
|
* Students can apply to GSoC by opening an issue. |
|
|
|
\ No newline at end of file |
