Initial commit moved from https://github.com/sydseter/dungeons-and-da…

…emons

.gitignore

@@ -1,4 +1,28 @@
+# OWASP site
 /Gemfile
 /Gemfile.lock
 /favicon.ico
-_site/
+_site/
+
+# https://dungeonsanddaemons.org/
+node_modules
+
+# Output
+.output
+.vercel
+/.svelte-kit
+/build
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Env
+.env
+.env.*
+!.env.example
+!.env.test
+
+# Vite
+vite.config.js.timestamp-*
+vite.config.ts.timestamp-*

CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+Adopted by the Board 02-Dec-2020.
+
+Participation in the OWASP Foundation is conditional upon individuals following the Code of Conduct, and as such, individuals agree to conduct themselves per the following Code of Conduct:
+
+## Code of Conduct
+
+- Perform all professional activities and duties in accordance with all applicable laws and the highest ethical principles;
+- Promote the implementation of and promote compliance with standards, procedures, controls for application security;
+- Maintain appropriate confidentiality of proprietary or otherwise sensitive information encountered in the course of professional activities;
+- Discharge professional responsibilities with diligence and honesty;
+- Communicate openly and honestly;
+- Refrain from any activities which might constitute a conflict of interest or otherwise damage the reputation of employers, the information security profession, or the Foundation;
+- Maintain and affirm our objectivity and independence;
+- Reject inappropriate pressure from industry or others;
+- Not intentionally injure or impugn the professional reputation or practice of colleagues, clients, or employers;
+- Treat everyone with respect and dignity;
+- Not violate the OWASP trademarks, copyrights, or licenses;
+- Provide proper attribution to avoid plagiarism and copyright infringement, both within and outside of OWASP;
+- Ensure work submitted to OWASP is entirely yours and not copied, whole or in part, without proper attribution or permission;
+- Abide by all provisions in applicable OWASP Foundation organizational documents, agreements, and policies
+ (i) requiring adherence to applicable export laws, including the export control rules and regulations of the United States; or
+ (ii) requiring adherence to the applicable antitrust and competition laws, including the antitrust rules and regulations of the United States.
+- Not engage in any intimidating, harassment, discriminatory, abusive, derogatory, or demeaning speech or actions ("harassment" includes, but is not limited to: Communication or conduct that a reasonable person in the individual's circumstances would consider unwelcome, intimidating, hostile, threatening, violent, abusive or offensive, such communication may be related to gender, gender identity and expression, sexual orientation, disability, national origin, race, age, religion; it also includes stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention);
+- Avoid relationships that impair — or may appear to impair — the OWASP Foundation's objectivity and independence; and
+- Not engage in any illegal activities or commit violations of applicable law, including but not limited to the laws of the United States and its states or the European Union, that
+ (i) could result or actually result in liability or harm to OWASP Foundation; or
+ (ii) are related to your participation in OWASP Foundation, including use of OWASP Foundation materials and publications, sponsored activities; or
+ (iii) are related to your use of software developed in a project sponsored by OWASP Foundation.
+
+## Sanctions
+
+The Executive Director can suspend participation in OWASP for 30 days for perceived or actual breaches of the OWASP Code of Conduct or US law. Depending on the severity of the breach, the member or participant can accept the 30-day suspension, or in serious cases, the member or participant will be referred to the Compliance Committee for a decision regarding their ongoing participation or membership by the OWASP Board at the next available Board meeting.
+
+**For first time Code of Conduct breaches, where no violation of US law has occurred:**
+
+The member or participant can agree to comply with a temporary suspension imposed by the Executive Director of all OWASP participation for no more than 30 days. Membership will not be extended to cover the suspension.
+
+**For repeat or serious breaches of the Code of Conduct, or where a participant
+has been charged with a crime:**
+
+The Executive Director must suspend the member, refer the matter to the Compliance Committee, who will make an independent evaluation on if the Board should strip leadership, revoke participation, or membership privileges. The period of suspension will remain in place until after the Board votes on the matter.
+
+If the Board decides to take no action, full participation can resume immediately. If the participant is a member, their membership will be extended by the period of the suspension served.
+
+### Transparency and Oversight
+
+To provide transparency and oversight of sanctions, the Executive Director will inform the Board privately of the actions being taken under these sanctions, informing the Compliance Committee as required, and providing recommendations from the Compliance Committee to the Board and scheduling a vote as necessary.

CONTRIBUTING.md

@@ -1,6 +1,13 @@
-# Contributing Guidelines
+# Contributing
 
-Thank you for your interest in contributing to an OWASP project. We welcome all contributions and appreciate your efforts to improve our projects.
+Thank you for your interest in contributing to an OWASP project.
+The Dungeon & Daemons project is an open source effort and welcome all kinds of contributions and feedback.
+
+## Help us to improve & join our community by:
+
+- Reporting an error (typos, grammer) or fix it on a pull-request.
+- Give feedback.
+- Ask questions
 
 ## Getting Started
 
@@ -34,6 +41,36 @@ Before submitting a pull request, please make sure:
 
 5. Your pull request includes a clear and concise description of the changes you have made.
 
+## Contribute with content:
+
+- Propose ideas or suggest improvements. If it qualifies, we'll promote it to an issue.
+- Create a pull request for concrete fixes or translations for games that is ready to be played (e.g grammer/typos/fix). Changes need to be approved by the core team.
+- Create a pull request for games where help is needed (e.g any type of change). Any type of change is welcome.
+- Create a pull request for games where work is in progress (e.g any type of change). All fixes are welcome, but feature requests or changes to the game rules, story arc, need to be discussed before being made.
+- Create a pull request for games labeled "R.I.P" (e.g: any type of change). All changes are welcome, but it might get removed at a later stage unless you can considerably improve the quality of the game.  
+
+## Where can I start?
+
+- A good idea would be to go to https://dungeonsanddaemons.org/games when you click on a game, each game will be labeled: ready, w.i.p, r.i.p or help wanted. These labels tells you how you may proceede contributing to the game.
+
+Some of the games that got created where storytelling/storybook games. These games were created using yaml and you may simply change the yaml under [characters](characters), [games](games), [rules](rules), [static/images](images). Keep in mind that when adding content please add it into the game's respective folder under the main folders above. This way, your game will be made available correctly online.
+
+<img src="static/images/help.svg" width="100rem" />
+
+"Help wanted!" Means that any contribution is more then welcome. The game is dependent on your contributions to get ready and playable by the comunity.
+
+<img src="static/images/wip.svg" width="100rem" />
+
+"W.I.P", means that this is work in progress, contributions are welcome, but the original creator might want you to make contributions according to the ideas of the game creator. It may be a good idea to ask a question in the github forum, create a github issue or discuss the finer point on slack with the game creator befor making any larger contributions.
+
+<img src="static/images/rip.svg" width="100rem" />
+
+"R.I.P", means the game is dead. We won't be maintaining it and it might get removed. You can just restart the development of the game, but you will have to get it up to a level where you can play it before we change the status back to "W.I.P" or "READY".
+
+<img src="static/images/ready.svg" width="100rem" />
+
+"Ready", means the game can be played and are in maintanence mode, bugfixes, changes and translations are still needed, but there won't be any large changes to the story or game rules. If you want to change the game, you should discuss it with the game creator before proposing your changes.
+
 ## Code of Conduct
 
 We ask that all contributors to OWASP projects abide by our [Code of Conduct](https://owasp.org/www-policy/operational/code-of-conduct). This code outlines our expectations for behavior within the project community and helps us maintain a welcoming and inclusive environment for all contributors.