| Create from Template | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
The Ed-Fi Alliance is committed to supporting the Ed-Fi Community in managing the codebase and facilitating the ability to share code and features with each other as well as to the core codebase. To do so, guidelines have been set for all licensees to help streamline the process and management of code. This page outlines how the Ed-Fi Alliance tech team handles issues. For us, issues represent actionable work that should be done at some future point. It may be as simple as a small bug or as large as the work tracking the design of a new feature. However, it should be work that falls under the charter of our core tech components. We will keep issues open even if the Ed-Fi Alliance technical team internally has no plans to address in an upcoming release, as long as we consider the issue to fall under our purview. |
General Contributing Guide
...
If an issue is complex, consider filing it and giving us time to respond before sending a corresponding PRPull Request. If you want to work on the issue, just let it be known on the issue thread. Giving us a chance to review the issue will help save time. For example, we might let you know why existing behavior can't be changed or about particular implementation constraints you need to keep in mind, etc.
Don't feel obliged to match every issue with a PRPull Request. Simply filing issues for problems you encounter is a great way to contribute too!
| Tip |
|---|
We use JIRA to keep track of issues, see Ed-Fi Issue Tracker. Keep in mind that some tech components require a license, for access level check out our feature matrix. |
Licensing
- DO NOT submit PRs that alter licensing related files or headers. If you believe there's a problem with them, file an issue and let us take care of it.
| Note |
|---|
We borrowed these awesome guidelines from the .NET CoreFX team https://github.com/dotnet/corefx/wiki/Contributing |