Skip to content

Commit b775c65

Browse files
WillStrohlWillStrohl
authored
Merge pull request #61 from UpendoVentures/dev
Syncing main & dev
2 parents 61d68e6 + 0b44ec6 commit b775c65

File tree

289 files changed

+4677
-27817
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

289 files changed

+4677
-27817
lines changed

‎.github/CODE_OF_CONDUCT.md

+46
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
* Using welcoming and inclusive language
12+
* Being respectful of differing viewpoints and experiences
13+
* Gracefully accepting constructive criticism
14+
* Focusing on what is best for the community
15+
* Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
* Trolling, insulting/derogatory comments, and personal or political attacks
21+
* Public or private harassment
22+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Our Responsibilities
26+
27+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28+
29+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30+
31+
## Scope
32+
33+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34+
35+
## Enforcement
36+
37+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at mtrutledge@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38+
39+
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40+
41+
## Attribution
42+
43+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44+
45+
[homepage]: http://contributor-covenant.org
46+
[version]: http://contributor-covenant.org/version/1/4/

‎.github/CONTRIBUTING.md

+64
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
# How to contribute
2+
3+
Community contributions are essential part of any open source project. The community has access to a large number of unique configurations which would be extremely difficult for the core maintainers to reproduce. We want to keep it as easy as possible to contribute changes that get things working in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
4+
5+
Make sure you have a [GitHub account](https://github.com/signup/free) to start with.
6+
7+
## Level 1 contributions: easy ways to contribute
8+
There are several ways to contribute, depending on your background, level of expertise and willingness to spend some time. Everybody should be able to contribute on a minimal level:
9+
* Create or document issues
10+
* Create or improve documentation
11+
* Be a tester
12+
13+
### Create issues
14+
Anybody with a GutHub account can create new issues. Please verify that a simlar issue has not been created before. Clearly describe the issue you encounter.
15+
16+
### Create or improve documentation
17+
Create an issue with suggestions for document improvements. If you have an idea about the new documenation, add that text (prefereably in markdown format) in the issue as proposed new or improved documentation.
18+
19+
### Be a tester
20+
Download an install version of the extension and test it in your own environment. If you are reviewing issues, try to reproduce issues that have been created and enhance documentation of the issue to reproduce any bugs.
21+
22+
If there is a new version of an extension, be one of the first to test that new version on a fresh install and as an upgrade of a previous version. Report your findings as issues.
23+
24+
# Level 2 contributions: Provide improved or new code
25+
If you are commited as community member and have programming skills, there is more that you can do:
26+
* Create code fixes
27+
* Create new functionality
28+
29+
We asume that you have some basic Git(Hub) knowledge and know how to work with fork, clone, create issue, commit, push, pull requests
30+
31+
## Get started with code contributions
32+
33+
### Fork the repository on GitHub
34+
If this is your first time working with the repository, you will need to fork the repository to get your system configured for local development.
35+
36+
If you are new to Dnn Development, you can start by watching this video playlist which explains how to setup the required tools, your development environment and submit pull requests for modules, the Platform and the Persona Bar.
37+
[How to make a pull requests playlist](https://www.youtube.com/playlist?list=PLIx1M8IdVvqZ0bnODGqJyxvONNPj5BzMP)
38+
39+
* Click fork on the project. You will get a fork of the repository in your own GitHub account
40+
* Clone your fork locally with `git clone
41+
* Add the *upstream connection* to the original repository, so you can rebase and update your fork with `git remote add upstream` to the base (the original) repository
42+
* To update your fork to the latest, you can then run `git fetch upstream` followed by `git push`
43+
44+
## Making Changes
45+
* Create a topic branch from where you want to base your work. This is usually a branch linked to the *issue #* your are trying to solve
46+
* Make commits of logical units
47+
* When ready to publish your changes, you can with `git push -u origin my_contribution`
48+
* Make sure your pull request description tags the GitHub issue ID, so it is clear what issue you have fixed
49+
* Make sure your commit messages are in the proper format
50+
51+
## Submitting changes
52+
* Push your changes to a topic branch in your fork of the repository
53+
* Submit a pull request to the original (upstream( repository
54+
* The committers will handle updating the associated issue in the DNN Tracker to ensure it gets the necessary code review and QA
55+
56+
## Acceptance of your changes
57+
* We have a group of fellow developers that review pull requests submitted by developers like yourself
58+
* If your changes look good, then changes are merged to an appropriate release
59+
* You should get an email notification as we complete processing of your pull request
60+
61+
# Level 3 contributions: Become a repository custodian
62+
If you are really commited, want to work with highly commited team members (like yourself?) and want to contibute by taking care of one or more repositories, you might want to become a *repository custodian*.
63+
64+
Contact one of the team members of the organisation and discuss the opportunities.

‎.github/FUNDING.yml

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
github: UpendoVentures

‎.github/ISSUE_TEMPLATE/bug-report.md

+52
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
name: Bug Report
3+
about: Create a report to help us improve
4+
5+
---
6+
7+
## Sponsorship
8+
<!--
9+
Open-Source is not free. We need to eat too. ~wink!~
10+
11+
We manage a TON of DNN extensions... Look!
12+
https://upendoventures.com/What/CMS/DNN/Extensions
13+
-->
14+
15+
If this request requires additional support (e.g., such as direct email/phone/meeting/development), I have the following interest in helping to [sponsor the effort via GitHub Sponsors](https://github.com/sponsors/UpendoVentures):
16+
17+
- [ ] None, please continute to work for me for free :P
18+
- [ ] Absolutely, I get value out of this!
19+
- [ ] Maybe later
20+
- [ ] I'm already a sponsor... Woot!
21+
22+
## Describe the bug
23+
A clear and concise description of what the bug is.
24+
25+
## Software Versions
26+
- DNN: 00.00.00
27+
- Module: 00.00.00
28+
29+
## To Reproduce
30+
Steps to reproduce the behavior:
31+
1. Go to '...'
32+
2. Click on '....'
33+
3. Scroll down to '....'
34+
4. See error
35+
36+
## Expected behavior
37+
A clear and concise description of what you expected to happen.
38+
39+
## Actual behavior
40+
A clear and concise description of what happened instead.
41+
42+
## Screenshots
43+
If applicable, add screenshots to help explain your problem.
44+
45+
## Error log
46+
**Note: Debug DLL's**
47+
Please replace the current extension DLL's with the debug DLL's (if these are available with the release) and reproduce the error with the debug DLL's before pasting the error log.
48+
49+
Paste the error log that is related to this issue.
50+
51+
## Additional context
52+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/feature-request.md

+33
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an idea for this project
4+
5+
---
6+
7+
## Sponsorship
8+
<!--
9+
Open-Source is not free. We need to eat too. ~wink!~
10+
11+
We manage a TON of DNN extensions... Look!
12+
https://upendoventures.com/What/CMS/DNN/Extensions
13+
-->
14+
15+
If this request requires additional support (e.g., such as direct email/phone/meeting/development), I have the following interest in helping to [sponsor the effort via GitHub Sponsors](https://github.com/sponsors/UpendoVentures):
16+
17+
- [ ] None, please continute to work for me for free :P
18+
- [ ] Absolutely, I get value out of this!
19+
- [ ] Maybe later
20+
- [ ] I'm already a sponsor... Woot!
21+
22+
## Is your feature request related to a problem?
23+
**Please describe.**
24+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
25+
26+
## Describe the solution you'd like
27+
A clear and concise description of what you want to happen.
28+
29+
## Describe alternatives you've considered
30+
A clear and concise description of any alternative solutions or features you've considered.
31+
32+
## Additional context
33+
Add any other context or screenshots about the feature request here.

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

+31
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
name: Help and Other Questions
3+
about: Use this to ask questions that don't relate to features and bug reports
4+
5+
---
6+
7+
## Sponsorship
8+
<!--
9+
Open-Source is not free. We need to eat too. ~wink!~
10+
11+
We manage a TON of DNN extensions... Look!
12+
https://upendoventures.com/What/CMS/DNN/Extensions
13+
-->
14+
15+
If this request requires additional support (e.g., such as direct email/phone/meeting/development), I have the following interest in helping to [sponsor the effort via GitHub Sponsors](https://github.com/sponsors/UpendoVentures):
16+
17+
- [ ] None, please continute to work for me for free :P
18+
- [ ] Absolutely, I get value out of this!
19+
- [ ] Maybe later
20+
- [ ] I'm already a sponsor... Woot!
21+
22+
## Please summarize your question in one sentence
23+
24+
25+
## Give a more extended description
26+
27+
28+
## Steps to reproduce (if needed)
29+
30+
31+
## Other comments or remarks

‎.github/PULL_REQUEST_TEMPLATE.md

+26
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
<!--- Provide a general summary of your changes in the Title above -->
2+
## Related to Issue
3+
Fixes #
4+
5+
## Description
6+
<!--- Describe your changes in detail -->
7+
8+
## How Has This Been Tested?
9+
<!--- Please describe in detail how you tested your changes. -->
10+
<!--- Include details of your testing environment, tests ran to see how -->
11+
<!--- your change affects other areas of the code, etc. -->
12+
13+
## Screenshots (if appropriate):
14+
15+
## Types of changes
16+
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
17+
- [ ] Bug fix (non-breaking change which fixes an issue)
18+
- [ ] New feature (non-breaking change which adds functionality)
19+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
20+
21+
## Checklist:
22+
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
23+
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
24+
- [ ] My code follows the code style of this project.
25+
- [ ] My change requires a change to the documentation.
26+
- [ ] I have updated the documentation accordingly.

0 commit comments

Comments
 (0)