Skip to content

Commit 2fa7d22

Browse files
authored
docs: add community-contributed README (#515)
Signed-off-by: chjmil <[email protected]>
1 parent e777557 commit 2fa7d22

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

docs/community/README.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
2+
# Community-Contributed Features
3+
4+
Community contributed features are submitted by community members to help expand the set of features that the project maintainers are capable of adding to the project on their own.
5+
6+
> [!CAUTION]
7+
> Community members are responsible for maintaining these features. While project maintainers try to verify these features work as expected when merged, they cannot guarantee future releases will not break them. If you encounter issues while using these features, start a [GitHub Discussion](https://github.com/sassoftware/viya4-iac-azure/discussions) or open a Pull Request to fix them. As a last resort, create a GitHub Issue for the concern.
8+
9+
## Community-Contributed Feature Expectations
10+
11+
- As with other features, community contributed features should include unit tests which add to the level of community confidence for the feature. Unit tests should also help indicate if a problem occurs with the feature in a future release.
12+
13+
- Community contributed features should be disabled by default. If applicable, a boolean configuration variable named COMMUNITY_ENABLE_<COMMUNITY_FEATURE> should be implemented for the community feature. The boolean configuration variable should serve as a way to enable or disable the community feature.
14+
15+
- Multiple community contributed feature configuration variables may exist for the same feature, although if the feature is disabled, they should have no effect on the overall behavior of the project.
16+
17+
- Additional community contributed feature configuration variables should use the COMMUNITY_ prefix to indicate they are part of a community contributed feature.
18+
19+
## Submitting a Community-Contributed Feature
20+
21+
Submit a community contributed Feature by creating a GitHub PR in this project. The PR should include the source code, unit tests and any required documentation including expected content for the [docs/community/community-config-vars.md](community-config-vars.md) file.
22+
23+
## What if a Community-Contributed Feature breaks
24+
25+
If you encounter issues while using a community contributed feature, start a [GitHub Discussion](https://github.com/sassoftware/viya4-iac-azure/discussions) or open a Pull Request to fix the issue. As a last resort, you can create a GitHub Issue to inform the community about the problem.
26+
27+
If a community contributed feature is implemented as required, disabling the community feature should serve as a way to remove any impact that it has on the project. Community contributed features that affect the project when disabled should be re-worked to prevent that behavior.

0 commit comments

Comments
 (0)