A lot of good things come out of the discussions in the various branches, issues and pull requests of the repo, which do have conclusions. However, we cannot expect that members who want to make contributions first read all discussions of past weeks to get up to date what the implicit decisions on policies, concept, programming paradigms and best practice are. Essential things that the developers like to be obeyed, especially if they deviate from past practices should be summarized and updated on a separate Developers Guide. This should be separate from a Users Guide. This will ensure that the developer group for this repo remains engage or ideally grows.
If policies/concepts need more discussion that can happen here.
A lot of good things come out of the discussions in the various branches, issues and pull requests of the repo, which do have conclusions. However, we cannot expect that members who want to make contributions first read all discussions of past weeks to get up to date what the implicit decisions on policies, concept, programming paradigms and best practice are. Essential things that the developers like to be obeyed, especially if they deviate from past practices should be summarized and updated on a separate Developers Guide. This should be separate from a Users Guide. This will ensure that the developer group for this repo remains engage or ideally grows.
If policies/concepts need more discussion that can happen here.