## How one would search to find if an encountered problem was a known issue, an issue being addressed, etc.?
## How one would search to find if an encountered problem was a known issue, an issue being addressed, etc.?
Main issue: #823
> "It would really help if a non-developer, non Github user could get some sense of how to use the proposed repository and, specifically, how one would search to find if an encountered problem was a known issue, an issue being addressed, etc." (@dtarrant)
> "It would really help if a non-developer, non Github user could get some sense of how to use the proposed repository and, specifically, how one would search to find if an encountered problem was a known issue, an issue being addressed, etc." (@dtarrant)
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).
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).
...
@@ -159,6 +161,7 @@ So far, ~~quick~~ recap:
...
@@ -159,6 +161,7 @@ So far, ~~quick~~ recap:
* We might not want to be very aggressive about splitting either. Only where it makes sense.
* We might not want to be very aggressive about splitting either. Only where it makes sense.
* They may want to have their own wiki space (draft docs, roadmap/planning)
* They may want to have their own wiki space (draft docs, roadmap/planning)
* While we can do part of this with labels, having subprojects makes it possible to have more granular labels. Ex: taxes have different challenges for Canada (HST/GST per province) than for VAT in Europe. Having a single "taxes" label would be limiting.
* While we can do part of this with labels, having subprojects makes it possible to have more granular labels. Ex: taxes have different challenges for Canada (HST/GST per province) than for VAT in Europe. Having a single "taxes" label would be limiting.
* It's easier to subscribe to issue notifications for a specific sub-project.
## Document the account creation, permissions, workflow
## Document the account creation, permissions, workflow