Added core files

OpenScienceMOOC · May 10, 2018 · 83c60923a3396d0d157f2ced18640fac6ea807af · 83c6092
1 parent 26047f0
commit 83c60923a3396d0d157f2ced18640fac6ea807af
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -0,0 +1,74 @@
+  
+# Contributor Covenant Code of Conduct
+  
+
+  
+## Our Pledge
+  
+
+  
+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.
+  
+
+  
+## Our Standards
+  
+
+  
+Examples of behavior that contributes to creating a positive environment
+  
+include:
+  
+
+  
+* Using welcoming and inclusive language
+  
+* Being respectful of differing viewpoints and experiences
+  
+* Gracefully accepting constructive criticism
+  
+* Focusing on what is best for the community
+  
+* Showing empathy towards other community members
+  
+
+  
+Examples of unacceptable behavior by participants include:
+  
+
+  
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  
+advances
+  
+* Trolling, insulting/derogatory comments, and personal or political attacks
+  
+* Public or private harassment
+  
+* Publishing others' private information, such as a physical or electronic
+  
+  address, without explicit permission
+  
+* Other conduct which could reasonably be considered inappropriate in a
+  
+  professional setting
+  
+
+  
+## Our Responsibilities
+  
+
+  
+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.
+  
+
+  
+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.
+  
+
+  
+## Scope
+  
+
+  
+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.
+  
+
+  
+## Enforcement
+  
+
+  
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+  
+reported by contacting the project team at [jon.tennant.2@gmail.com](mailto:jon.tennant.2@gmail.com) or [bianca.kramer@gmail.com](mailto:bianca.kramer@gmail.com). All
+  
+complaints will be reviewed and investigated and will result in a response that
+  
+is deemed necessary and 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.
+  
+
+  
+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.
+  
+
+  
+## Attribution
+  
+
+  
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+  
+available at [http://contributor-covenant.org/version/1/4][version]
+  
+
+  
+[homepage]: http://contributor-covenant.org
+  
+[version]: http://contributor-covenant.org/version/1/4/gibbon.toolbox@gmail.com
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -0,0 +1,62 @@
+  
+# Contribution Guidelines
+  
+These are the main contributing guidelines for the development of this MOOC, and apply to each module within. The development structure for this is based on a combination of two things:
+  
+1. Invited experts as part of a core development team, led by one or two managers for each module.
+  
+1. Open participation, where anyone can contribute using the standard processes on GitHub.
+  
+
+  
+Feedback and contributions of any form are welcomed. Feel free also to [contact us](https://opensciencemooc.eu/contact-us/) to discuss anything further.
+  
+
+  
+At the present, development is in very early stages, as this is an entirely crowd-sourced and volunteer-led project. We are focusing inititally on [Module 5](https://github.com/OpenScienceMOOC/Module-5-Open-Research-Software-and-Open-Source) to run as a pilot for testing and receiving feedback. After this, the protocol and content will be revised, and then applied accordingly to the development of the remaining modules.
+  
+
+  
+## Contact us
+  
+
+  
+If you want to contribute, add yourself to the [contributors list](https://docs.google.com/spreadsheets/d/1FEbnxBkmIQFDEViTgZDn0AJ0MSK6eDSBEgZuCkW_B5s/edit?usp=drive_web) and join our open [Slack channel](https://openmooc-ers-slackin.herokuapp.com/).
+  
+
+  
+If you have questions about the project, please [email us](info@opensciencemooc.eu) directly.
+  
+
+  
+Stay tuned on what's happening on Twitter with [@OpenSci_MOOC](https://twitter.com/OpenSci_MOOC).
+  
+
+  
+## Getting started
+  
+1. [Forming a team for collaborative design](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MODULE_DESIGN_PROTOCOL.md#forming-a-team-for-collaborative-design).
+  
+1. [The development process](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MODULE_DESIGN_PROTOCOL.md#the-development-process).
+  
+1. Familiarise yourself with the [script writing guide](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/Writing_a_script.md), the [script template](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/Script_template.md) and the [video management protocol](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/Video_management_protocol.md).
+  
+
+  
+Each team will adhere to the [MOOC planning template](https://github.com/OpenScienceMOOC/Main/blob/master/Production_Files/MOOC%20planning%20template.docx) to structure development in a systematic way. 
+  
+
+  
+
+  
+## Reporting issues
+  
+
+  
+- **Search for existing issues.** Please check to see if someone else has reported the same issue.
+  
+- **Share as much information as possible.** Include operating system and version, browser and version. Also, include steps to reproduce the bug.
+  
+
+  
+## Project Setup
+  
+Refer to the [README](README.md).
+  
+
+  
+## Content style
+  
+This is flexible to each module as required, and defined by each development team in advance as part of the protocol.
+  
+
+  
+## Code style
+  
+Flexible, as long as it is consistent. Ideally, all content would be drafted in markdown, for increasing re-use. This can be easily performed in R Studio, for example, which also has a GitHub interface to make collaborating on this project even simpler.
+  
+
+  
+Please read [this guide](https://support.rstudio.com/hc/en-us/articles/200532077-Version-Control-with-Git-and-SVN) to familiarise yourself with this process. Which in itself, is actually fairly powerful for Open Science!
+  
+
+  
+## Pull requests
+  
+
+  
+Please refer to each project's style guidelines and guidelines for submitting patches and additions. In general, we follow the "fork-and-pull" Git workflow.
+  
+
+  
+- Fork the repo on GitHub
+  
+- Clone the project to your own machine
+  
+- Commit changes to your own branch
+  
+- Push your work back up to your fork
+  
+- Submit a Pull request so that we can review your changes
+  
+
+  
+NOTE: Be sure to merge the latest from "upstream" before making a pull request!
+  
+
+  
+
+  
+- Try not to pollute your pull request with unintended changes – keep them simple and small. If possible, squash your commits.
+  
+- Try to share how your code has been tested before submitting a pull request.
+  
+- If your PR resolves an issue, include **closes #ISSUE_NUMBER** in your commit message (or a [synonym](https://help.github.com/articles/closing-issues-via-commit-messages)).
+  
+- Review
+  
+    - If your PR is ready for review, another contributor will be assigned to review your PR
+  
+    - The reviewer will accept or comment on the PR.
+  
+    - If needed address the comments left by the reviewer. Once you're ready to continue the review, ping the reviewer in a comment.
+  
+    - Once accepted your code will be merged to `master`
diff --git a/LICENSE_CONTENT.md b/LICENSE_CONTENT.md
@@ -0,0 +1,116 @@
+  
+CC0 1.0 Universal
+  
+
+  
+Statement of Purpose
+  
+
+  
+The laws of most jurisdictions throughout the world automatically confer
+  
+exclusive Copyright and Related Rights (defined below) upon the creator and
+  
+subsequent owner(s) (each and all, an "owner") of an original work of
+  
+authorship and/or a database (each, a "Work").
+  
+
+  
+Certain owners wish to permanently relinquish those rights to a Work for the
+  
+purpose of contributing to a commons of creative, cultural and scientific
+  
+works ("Commons") that the public can reliably and without fear of later
+  
+claims of infringement build upon, modify, incorporate in other works, reuse
+  
+and redistribute as freely as possible in any form whatsoever and for any
+  
+purposes, including without limitation commercial purposes. These owners may
+  
+contribute to the Commons to promote the ideal of a free culture and the
+  
+further production of creative, cultural and scientific works, or to gain
+  
+reputation or greater distribution for their Work in part through the use and
+  
+efforts of others.
+  
+
+  
+For these and/or other purposes and motivations, and without any expectation
+  
+of additional consideration or compensation, the person associating CC0 with a
+  
+Work (the "Affirmer"), to the extent that he or she is an owner of Copyright
+  
+and Related Rights in the Work, voluntarily elects to apply CC0 to the Work
+  
+and publicly distribute the Work under its terms, with knowledge of his or her
+  
+Copyright and Related Rights in the Work and the meaning and intended legal
+  
+effect of CC0 on those rights.
+  
+
+  
+1. Copyright and Related Rights. A Work made available under CC0 may be
+  
+protected by copyright and related or neighboring rights ("Copyright and
+  
+Related Rights"). Copyright and Related Rights include, but are not limited
+  
+to, the following:
+  
+
+  
+  i. the right to reproduce, adapt, distribute, perform, display, communicate,
+  
+  and translate a Work;
+  
+
+  
+  ii. moral rights retained by the original author(s) and/or performer(s);
+  
+
+  
+  iii. publicity and privacy rights pertaining to a person's image or likeness
+  
+  depicted in a Work;
+  
+
+  
+  iv. rights protecting against unfair competition in regards to a Work,
+  
+  subject to the limitations in paragraph 4(a), below;
+  
+
+  
+  v. rights protecting the extraction, dissemination, use and reuse of data in
+  
+  a Work;
+  
+
+  
+  vi. database rights (such as those arising under Directive 96/9/EC of the
+  
+  European Parliament and of the Council of 11 March 1996 on the legal
+  
+  protection of databases, and under any national implementation thereof,
+  
+  including any amended or successor version of such directive); and
+  
+
+  
+  vii. other similar, equivalent or corresponding rights throughout the world
+  
+  based on applicable law or treaty, and any national implementations thereof.
+  
+
+  
+2. Waiver. To the greatest extent permitted by, but not in contravention of,
+  
+applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and
+  
+unconditionally waives, abandons, and surrenders all of Affirmer's Copyright
+  
+and Related Rights and associated claims and causes of action, whether now
+  
+known or unknown (including existing as well as future claims and causes of
+  
+action), in the Work (i) in all territories worldwide, (ii) for the maximum
+  
+duration provided by applicable law or treaty (including future time
+  
+extensions), (iii) in any current or future medium and for any number of
+  
+copies, and (iv) for any purpose whatsoever, including without limitation
+  
+commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes
+  
+the Waiver for the benefit of each member of the public at large and to the
+  
+detriment of Affirmer's heirs and successors, fully intending that such Waiver
+  
+shall not be subject to revocation, rescission, cancellation, termination, or
+  
+any other legal or equitable action to disrupt the quiet enjoyment of the Work
+  
+by the public as contemplated by Affirmer's express Statement of Purpose.
+  
+
+  
+3. Public License Fallback. Should any part of the Waiver for any reason be
+  
+judged legally invalid or ineffective under applicable law, then the Waiver
+  
+shall be preserved to the maximum extent permitted taking into account
+  
+Affirmer's express Statement of Purpose. In addition, to the extent the Waiver
+  
+is so judged Affirmer hereby grants to each affected person a royalty-free,
+  
+non transferable, non sublicensable, non exclusive, irrevocable and
+  
+unconditional license to exercise Affirmer's Copyright and Related Rights in
+  
+the Work (i) in all territories worldwide, (ii) for the maximum duration
+  
+provided by applicable law or treaty (including future time extensions), (iii)
+  
+in any current or future medium and for any number of copies, and (iv) for any
+  
+purpose whatsoever, including without limitation commercial, advertising or
+  
+promotional purposes (the "License"). The License shall be deemed effective as
+  
+of the date CC0 was applied by Affirmer to the Work. Should any part of the
+  
+License for any reason be judged legally invalid or ineffective under
+  
+applicable law, such partial invalidity or ineffectiveness shall not
+  
+invalidate the remainder of the License, and in such case Affirmer hereby
+  
+affirms that he or she will not (i) exercise any of his or her remaining
+  
+Copyright and Related Rights in the Work or (ii) assert any associated claims
+  
+and causes of action with respect to the Work, in either case contrary to
+  
+Affirmer's express Statement of Purpose.
+  
+
+  
+4. Limitations and Disclaimers.
+  
+
+  
+  a. No trademark or patent rights held by Affirmer are waived, abandoned,
+  
+  surrendered, licensed or otherwise affected by this document.
+  
+
+  
+  b. Affirmer offers the Work as-is and makes no representations or warranties
+  
+  of any kind concerning the Work, express, implied, statutory or otherwise,
+  
+  including without limitation warranties of title, merchantability, fitness
+  
+  for a particular purpose, non infringement, or the absence of latent or
+  
+  other defects, accuracy, or the present or absence of errors, whether or not
+  
+  discoverable, all to the greatest extent permissible under applicable law.
+  
+
+  
+  c. Affirmer disclaims responsibility for clearing rights of other persons
+  
+  that may apply to the Work or any use thereof, including without limitation
+  
+  any person's Copyright and Related Rights in the Work. Further, Affirmer
+  
+  disclaims responsibility for obtaining any necessary consents, permissions
+  
+  or other rights required for any use of the Work.
+  
+
+  
+  d. Affirmer understands and acknowledges that Creative Commons is not a
+  
+  party to this document and has no duty or obligation with respect to this
+  
+  CC0 or use of the Work.
+  
+
+  
+For more information, please see
+  
+<http://creativecommons.org/publicdomain/zero/1.0/>
diff --git a/README.md b/README.md
@@ -1 +1,30 @@
-  
-# Module-8-Citizen-Science-and-Science-Communication
+  
+# Module 8: Citizen Science and Science Communication
+  
+
+  
+## Rationale <a name="Rationale"></a>
+  
+
+  
+Science communication is often seen as a unidirectional process from scientist to non-scientists, but with careful and strategic engagement it can be so much more. For this, a deeper understanding of the basics and existing structures is needed, as well as the capabilities of newer channels like social media. This module will teach effective techniques for communicating your research with a wider audience, as well as engaging them with the process itself.
+  
+
+  
+
+  
+## Learning outcomes <a name="Learning outcomes"></a>
+  
+
+  
+1. The researcher will be able to identify and describe some of the major different types of audience and stakeholder involved in science communication, what their needs and viewpoints are, and the importance of citizen science and public engagement with science.
+  
+1. By working either individually or their research group, each researcher will be able to use a range of communication channels, including social media, to strategically engage different types of audience with their research.
+  
+1. If there are relevant policy-related issues to their discipline, the researcher will be able to engage with them through available channels and make sure that their research field is appropriately represented.
+  
+11. Each researcher will be able to identify relevant press/communication contacts at their institute, and be able to convey to them why their research is of importance for wider dissemination.
+  
+1. The researcher will be able to write a blog post or non-specialist summary about either their own research or research that they are familiar with, and communicate this to wider non-academic audiences.
+  
+
+  
+## Development team
+  
+TBC
+  
+
+  
+## Key documents <a name="Key documents"></a>
+  
+
+  
+- [Contributing](CONTRIBUTING.md)
+  
+- [Module design protocol](https://github.com/OpenScienceMOOC/Module-8-Citizen-Science-and-Science-Communication/tree/master/production_toolkit/MODULE_DESIGN_PROTOCOL.md)
+  
+- [Code of conduct](CODE_OF_CONDUCT.md)
+  
+- [Key elements](key_elements.md)
+  
+
+  
+
+  
+## Licenses <a name="Licenses"></a>
+  
+
+  
+### Content 
+  
+MOOC content license: [![CC0 Public Domain Dedication](https://img.shields.io/badge/License-CC0%201.0-lightgrey.svg)](https://creativecommons.org/publicdomain/zero/1.0/)