Core Modules Development Team July, 19th 2018 meeting recording

The core modules developers team had their second meeting on July, 19th 2018 and here is the recording.

Participants:

• Daniel Valadas
• John Cornelison
• Barry Waluszko
• Andrew Hoefling
• Joe Craig
• Peter Donker
• Clint Patterson
• Ernst Petter Tamminga
• Michael Onizuka

Summary:

• Maintainer have been assigned on some modules, for the ones without a specific maintainer, the community will still maintain them as a group effort. For those modules that have a maintainer, it will be indicated in the readme file. Should a maintainer not reply for a long time, the community will take back the responsibility of the module as a group and the maintainer name would then be removed.
• For modules with specific maintainers, the maintainer is responsible for merging pull requests and publishing new releases. For the modules without a specific maintainer, we will do the same as a group.
• There is a new release of the Repository module that makes it Dnn 9.2 compatible  https://github.com/DNNCommunity/DNN.Repository/releases this is a complete code change from VB to C# and has been published as 04.00.00 pre-release. Please test on non-production environments and report back any issues you may find.
• A future for the Active Directory provider is still in the talks.
• The migration documentation from Dnn.Forums to Active Forums was found at https://github.com/ActiveForums/ActiveForums/blob/master/sql/CoreForumsToActiveForums.sql this script needs to be tested and documented. We are still trying to get in touch with the persons responsible of the ActiveForums repository.
• We talked about github branches and there are different opinions so, the decision was to leave the branches as they are now. Pull requests should be made to the default branch and if there is any special branching, it should be documented in the contributions guidelines
• A contributing.md file will be created shortly to document how to clone, build, test and publish pull requests, this will be accompanied by a walkthrough video. Maintainers will modify the general contributing.md instructions if there is any special build process for their repository.
• Some modules such as the Maps module would require a lot of effort to bring back to life for not much benefits. For instance the maps module has not been working for many years and this is not due to anything related to Dnn, but due to the google maps API having changed a long time ago. It is for this module self evident that nobody can be currently using it so reviving it is pointless since there is already many other solutions. However, the repository will stay there is anyone decides to revive it (I may sink my teeth into it at some point).
• After each published release, a new milestone will be created with the next release number. So if for instance version 2.3.4 is releases, right after the release, a 2.3.5 milestone will be created that should include only bug fixes and very minor no risk enhancements; and a 2.4.0 milestone will also be created to include new features and enhancements that are considered an important change. The first digit of the version number will only be incremented on major changes such as changing the programming language, the underlying technology stack or public APIs that module specific providers, templates or other may use.
• We may introduce Appveyor automated builds into most projects. This will validate that any Pull request builds properly and will also create the packages automatically. Which means that it will be even easier for testers to help, they can just download the package and test the changes without having to know anything about building the module.

Contributing:

• If you want to contribute in any way, please let me know here, all contributions are welcome: testing, ideas, programming, documentation, walkthroughs, etc.