| ... | ... | @@ -76,3 +76,21 @@ 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.
|
|
|
|
|
|
|
|
# Frequently asked questions (FAQ)
|
|
|
|
|
|
|
|
## How one would search to find if an encountered problem was a known issue, an issue being addressed, etc.?
|
|
|
|
|
|
|
|
The proposed Gitlab structure would be to have project spaces around components/themes of CiviCRM (financial, cloud-native, translation, reports, etc, but there would still be a "core" project).
|
|
|
|
|
|
|
|
This would aim to create somewhat more manageable spaces where teams can prioritise within those spaces). We can also search across projects in Gitlab.
|
|
|
|
|
|
|
|
It might also be necessary to also search the pull-request queue on Github, in case someone directly opened a pull-request.
|
|
|
|
|
|
|
|
## What about the 2000 open issues in JIRA that are not confirmed?
|
|
|
|
|
|
|
|
We would encourage more triage before making JIRA read-only. CiviCRM does occasionally purge issues that have not had activity in 18 months. Batch-closed issues can then be re-opened by people watching them (who will receive an email notification) and still interested on working on the issue.
|
|
|
|
|
|
|
|
## What about Stack Exchange?
|
|
|
|
|
|
|
|
Stack Exchange is the front-line of support. Sometimes the answer is "this is a bug, therefore it needs to be tracked in an issue". As with Gitlab, we will discourage people from opening support requests in Gitlab. |
|
|
\ No newline at end of file |
