Update forked Dnn.Platform with latest from dnnsoftware

.github/BUILD.md

@@ -0,0 +1,37 @@
+# Building Dnn
+
+You do not always need to build the entire solution, you can download and install from the releases and only build the part you are working on, please read [How to Contribue](CONTRIBUTING.md) first.
+
+If you do need to build the entire solution and the distribution packages, you need to be aware that the entire distribution is split in multiple github repositories.
+* This repository - contains all the core APIs and the Admin Experience (Persona Bar)
+* [CKEditorProvider](https://github.com/DNN-Connect/CKEditorProvider) - The default HTML Editor Provider
+* [CDF](https://github.com/dnnsoftware/ClientDependency) - The Dnn Client Dependency Framework
+
+Also, we currently maintain two branches, the development branch is the next major release and we also maintain a release/x.x.x branch that allows doing bug fixes on the current major version.
+
+To prevent issues with long paths in some build scripts, fork this repository in a short named folder on the root of any drive such as `c:\dnnsrc\` if you fork to a long path such as `c:\users\username\documents\dnn\source\` you may encounter long path issues.
+
+In order to build the whole solution and produce the install and upgrade packages, you simply need to open PowerShell and run the following command:
+```
+.\build.ps1
+```
+
+The version you are building is the current version on the branch you are. However there are 2 external repositories that get bundled into Dnn build:
+[Dnn.Connect CKEditor provider](https://github.com/DNN-Connect/CKEditorProvider) is the default HTML editor provider and its default branch is development.	
+[Dnn.ClientDependency](https://github.com/dnnsoftware/ClientDependency), the default branch is dnn
+Under normal situations they are the branches used for the next release, however if you have a need to specify a different branch to pull during the build you can specify them as such:
+```
+.\build.ps1 -ScriptArgs '--CkBranch="branch-name"','--CdfBranch="branch-name"'
+```
+
+If you encounter any build issues, please re-run the build with more verbosity as such:
+```
+.\build.ps1 -Verbosity diagnostic
+```
+This will log much more information about the problem and allow you to open an issue with those more detailed logs.
+
+Also, the build scripts should leave you with 0 tracked modified files in git.
+If a build fails midway and you have tracked artifacts, you can simply run:
+`git reset --hard` and/or `git clean -dxf` in order to come back to a clean state.
+
+If you encounter PowerShell security issues, please read [Cake - PowerShell Security](https://cakebuild.net/docs/tutorials/powershell-security)

.github/ISSUE_TEMPLATE/bug-report.md

@@ -34,16 +34,13 @@ Paste the error log that is related to this issue.
 Add any other context about the bug that may be helpful for resolution.
 
 ## Affected version
-<!-- Check all that apply and add more if necessary -->
-
-* [x] 9.3.2
-* [x] 9.3.1
-* [x] 9.2.2
-* [x] 9.2.1
-* [x] 9.2
-* [x] 9.1.1
-* [ ] 9.1
-* [ ] 9.0
+<!-- 
+Please add X in at least one of the boxes as appropriate. In order for an issue to be accepted, a developer needs to be able to reproduce the issue on a currently supported version. If you are looking for a workaround for an issue with an older version, please visit the forums at https://dnncommunity.org/forums
+-->
+
+* [ ] 10.0.0 alpha build
+* [ ] 9.4.2 alpha build
+* [ ] 9.4.1 latest supported release
 
 ## Affected browser
 <!-- 

.github/ISSUE_TEMPLATE/feature-request.md

@@ -22,17 +22,6 @@ If applicable, provide screenshots to help explain your problem and/or feature.
 ## Additional context
 Add any other context about the feature that may be helpful with implementation.
 
-## Affected version
-<!-- Check all that apply and add more if necessary -->
-* [x] 9.3.2
-* [x] 9.3.1
-* [x] 9.2.2
-* [x] 9.2.1
-* [x] 9.2
-* [x] 9.1.1
-* [ ] 9.1
-* [ ] 9.0
-
 ## Affected browser
 <!-- 
   Check all that apply and add more if necessary.

.github/ISSUE_TEMPLATE/help-and-other-questions.md

@@ -6,6 +6,8 @@ about: Ask for help or other questions
 <!-- 
   Please read contribution guideline first: https://github.com/dnnsoftware/Dnn.Platform/blob/development/CONTRIBUTING.md 
   Any potential security issues should be sent to security@dnnsoftware.com, rather than posted on GitHub
+  We have a new community site with a very active forum at https://dnncommunity.org/forums for general questions, this is
+  often a better place to reach a wider range audience for questions.
 -->
 
 ## Summary
@@ -37,15 +39,13 @@ Paste the related error log.
 Add any other context that may be helpful.
 
 ## Affected version
-<!-- Check all that apply and add more if necessary -->
-* [x] 9.3.2
-* [x] 9.3.1
-* [x] 9.2.2
-* [x] 9.2.1
-* [x] 9.2
-* [x] 9.1.1
-* [ ] 9.1
-* [ ] 9.0
+<!-- 
+Please add X in at least one of the boxes as appropriate. In order for an issue to be accepted, a developer needs to be able to reproduce the issue on a currently supported version. If you are looking for a workaround for an issue with an older version, please visit the forums at https://dnncommunity.org/forums
+-->
+
+* [ ] 10.0.0 alpha build
+* [ ] 9.4.1 alpha build
+* [ ] 9.4.0 latest supported release
 
 ## Affected browser
 <!-- 

.github/ISSUE_TEMPLATE/request-for-comments.md

@@ -21,12 +21,10 @@ Another proposed solution to the problem
 Documentation of any other items researched for resolution.
 
 ## Affected version
-<!-- Check all that apply and add more if necessary -->
-* [x] 9.3.2
-* [x] 9.3.1
-* [x] 9.2.2
-* [x] 9.2.1
-* [x] 9.2
-* [x] 9.1.1
-* [ ] 9.1
-* [ ] 9.0
+<!-- 
+Please add X in at least one of the boxes as appropriate. In order for an issue to be accepted, a developer needs to be able to reproduce the issue on a currently supported version. If you are looking for a workaround for an issue with an older version, please visit the forums at https://dnncommunity.org/forums
+-->
+
+* [ ] 10.0.0 alpha build
+* [ ] 9.4.1 alpha build
+* [ ] 9.4.0 latest supported release

.github/PULL_REQUEST_PROCESS.md

@@ -1,10 +1,11 @@
 # DNN Platform Pull Request Proceseses
 
-The goal of this document is to set standards for the review, processing, and approval of all Pull requests into the DNN_Platform GitHub repository, as well as associated commmunity open-source repositories.  These rules apply to ALL pull requests, regardless of the submitter, or complexity of the change.
+The goal of this document is to set standards for the review, processing, and approval of all Pull requests into the DNN_Platform GitHub repository, as well as associated community open-source repositories.  These rules apply to ALL pull requests, regardless of the submitter, or complexity of the change.
 
 ## Prerequisites
 The following items must all be true prior to a pull request being submitted to the DNN_Platform, if any of the following items are not true the pull request will be returned for edits referencing the specific missing item(s).
 
+* Changes should target the branch where they should be merged, bug fixes that have no breaking changes should usually target the release/x.x.x latest branch; breaking changes, new features and major behavior changes should usually target the development branch. If you are not sure which to target, please ask in the issue comments before starting your changes.
 * Change should represent an entire solution for the issue at hand.  Partial requests will NOT be processed.
 * Change should have a supporting issue logged on the DNN_Platform GitHub account, documenting the issue resolved, following the procedures outlined on the [Contribute Page](CONTRIBUTING.md)
 * If your change was to an area that already was covered by tests those tests must be updated.  New tests for areas currently un-tested are appreciated
@@ -13,14 +14,16 @@ The following items must all be true prior to a pull request being submitted to
   * Issue #, referenced such as “Fixes #24”
   * Release Note: Suggested release note for the change such as “Improvement of user profile to improve performance when searching.”
   * Testing Steps: Suggested testing steps for validation of the change
-* Pull request must pass the Continuous Integration (CI) Build.  Failure of the build will result in no futher review of the pull request until the build has been corrected.
+* Pull request must pass the Continuous Integration (CI) Build.  Failure of the build will result in no further review of the pull request until the build has been corrected.
 * The .NET Foundation [Contributor License Agreement (CLA)] (https://cla.dotnetfoundation.org/) must be signed prior to code review.  An automated process will prompt for this as part of the Pull Request process.
 
 > NOTE: Changes to methods that have been marked as [Obsolete] will typically not be accepted due to inherit risks associated with code scheduled for removal.  If a critical bug/issue exists, please be sure to document & discuss using an RFC issue prior to submitting your contribution to ensure alignment with acceptance criteria.
 
 ## Code Review Process
 Community review of submitted pull requests is encouraged, and all pull requests must be reviewed by at least **two (2)** designated approvers before the change can be approved.  Once approved by two unique designated approvers, the change can be merged. An approver should NEVER merge their own change, even with two supporting approvals.  
 
+The DNN Platform project strives to review and comment on incoming pull requests in a timely fashion, however, it may be necessary at times to hold incoming pull requests for a period of time during releases or other administrative processes.  
+
 ### Designated Approvers
 At the current time the following community members are designated approvers.
 
@@ -30,8 +33,6 @@ At the current time the following community members are designated approvers.
 * Peter Donker ([donker](https://github.com/donker)) - Community Developer Advisory Group Lead
 * Daniel Valadas ([valadas](https://github.com/valadas))
 * Matt Rutledge ([mtrutledge](https://github.com/mtrutledge))
-* Vicenç Masanas ([vmasanas](https://github.com/vmasanas))
-* Erik van Ballegoij ([erikvb](https://github.com/erikvb))
 
 Additionally, the following individuals from ESW/DNN Corp are approved reviewers.
 
@@ -56,7 +57,7 @@ Once a pull request has been reviewed by two designated approvers it may be merg
 > This **_MUST NOT_** be done by the submitter of the Pull Request for ANY reason!  
 
 ### Execption for Build Process Pull Requests
-A special exception has been granted to reduce the number of Designed Approval reviews to 1 for all pull requests related to Build Support when incrementing versions in prepration of a release, or reconfiguration of the environment for the next version. 
+A special exception has been granted to reduce the number of Designed Approval reviews to 1 for all pull requests related to Build Support when incrementing versions in prepration of a release, adjustments of build processes, or reconfiguration of the environment for the next version. 
 
 Additionally a special exception has been granted to merge pull requests created by the Designated Approvers for the purposes of keeping release branches in sync when the pull request ONLY moves previously approved changes.  Such as moving bug fixes from a minor release into the next major release, or otherwise.
 
@@ -74,4 +75,4 @@ If an item was submitted that will be integrated into a future release that is n
 
 In this situation the reviewing team will approve the request, tag the request with a specific version milestone and add a comment noting when and why it will be included in the particularly identified release.
 
-This most often will apply to technology or dependency changes that require alignment with Major, Minor, Revision build inclusion.  
+This most often will apply to technology or dependency changes that require alignment with Major, Minor, Revision build inclusion.

.github/PULL_REQUEST_TEMPLATE.md

@@ -3,14 +3,14 @@
 -->
 
 <!-- 
-  Please make sure that there is a correcponding issue created and reference it in the PR by writing
+  Please make sure that there is a corresponding issue created and reference it in the PR by writing
   `Fixes #123` or `Closes #123`. 
   A PR without an accompanying issue will be accepted and merged on a very rare occasion
 -->
 
+
 ## Summary
 <!-- 
   Please describe the code changes as you see fit so that the reviewers have an easier task understanding what changed and why.
-
-  Any new unit tests will be highly appreciated.
+  New unit tests will be highly appreciated.
 -->

.github/VERSIONING_POLICY.md

@@ -1,7 +1,7 @@
 # DNN Platform Versioning and Deprecation Policies
 The DNN Platform follows a semantic versioning process for releases, in a manner to better communicate expectations of releases and their potential impacts to users of the platform.
 
-##Semantic Versioning
+## Semantic Versioning
 The DNN Community adopted the current semantic version policy in July of 2018.  Releases before this date may follow different standards.
 
 ### Major Releases (Ex 10.0.0)
@@ -10,14 +10,16 @@ A major release is as the name implies, a release with major changes.  These cha
 Major releases are also the time that platform requirements might be changed, such as requiring a new edition of SQL Server or otherwise.
 
 ### Minor Releases (Ex 10.1, 10.2, 10.x)
-A minor might contain smaller new features and enhancements, but will not introduce any breaking API changes, nor will it change the requirements of the hosting environment or platform to run the application.  
+A minor might contain smaller new features and enhancements, however, best efforts will be taken to minimize breaking changes.
 
 ### Revision Releases (Ex 10.1.1, 10.1.2, 10.1.x)
 These releases are created primarily to contain hot-fix style improvements from prior releases.  Any bugs or security issues identified, or missing UI/UX features from a Minor/Major release might be added to a revision release.  Similar to a Minor release a Revision release will not contain any known breaking changes.
 
 ## API Deprecation Policy
 The DNN Platform project is in a state of transition, continuing to modernize the API and work towards a transition to .NET Core.  To this point, it will be necessary for the project to remove public API's.  This will be done methodically, allowing developers to transition away from the older code with time to properly respond to change.
+
 Any API method to be removed will be flagged as deprecated in a release, major, minor or revision, and will be identified to be removed by a specific version.  This will be done using a C# annotation with a comment similar to the following "Deprecated in x.x.x.  Scheduled for removal in vy.0.0, use ____ instead".  The version number of "y" in this example must be 2 major versions ahead.  
+
 Therefore, an API marked as Deprecated in 9.2.1 can only be removed in version 11.0.  Additionally, methods marked for removal in a version will GUARANTEED be removed in that revision.
 > Example: [Obsolete("Deprecated in DotNetNuke 7.0. This function has been replaced by AddUserRole with additional params. Scheduled removal in v10.0.0.")]
 

.github/stale.yml

@@ -0,0 +1,34 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 90
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 14
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - pinned
+  - security
+  - bug
+  - noteworthy
+  - pull request submitted
+# Label to use when marking an issue as stale
+staleLabel: stale
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  We have detected this issue has not had any activity during the last 90 
+  days. That could mean this issue is no longer relevant and/or nobody has 
+  found the necessary time to address the issue. We are trying to keep the 
+  list of open issues limited to those issues that are relevant to the 
+  majority and to close the ones that have become 'stale' (inactive). If no 
+  further activity is detected within the next 14 days, the issue will be 
+  closed automatically.
+
+  If new comments are are posted and/or a solution (pull request) is 
+  submitted for review that references this issue, the issue will not be 
+  closed. Closed issues can be reopened at any time in the future. Please
+  remember those participating in this open source project are volunteers 
+  trying to help others and creating a better DNN Platform for all. Thank 
+  you for your continued involvement and contributions!
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: >
+  This issue has been closed automatically due to inactivity (as mentioned 
+  14 days ago). Feel free to re-open the issue if you believe it is still 
+  relevant.