└── README.md /README.md: -------------------------------------------------------------------------------- 1 | # The Journal of Open Source Education 2 | 3 | [![Powered by NumFOCUS](https://img.shields.io/badge/powered%20by-NumFOCUS-orange.svg?style=flat&colorA=E1523D&colorB=007D8A)](http://numfocus.org) [![Join the chat at https://gitter.im/openjournals/jose](https://badges.gitter.im/openjournals/jose.svg)](https://gitter.im/openjournals/jose?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) 4 | 5 | The [Journal of Open Source Education](http://jose.theoj.org) (JOSE, pronounced [hoe-zay]) is a journal for open educational software and open-source educational content. 6 | 7 | JOSE is a sibling journal to [Journal of Open Source Software](http://joss.theoj.org) (JOSS), which publishes open research software. 8 | JOSE relies on the journal management infrastructure and tools developed for JOSS. 9 | 10 | JOSE publishes two types of (brief) articles that describe: 11 | 12 | 1. open-source educational materials 13 | 14 | 2. open-source educational software tools 15 | 16 | ### Why is this journal needed? 17 | 18 | Currently, academia lacks a mechanism for crediting efforts to develop software for assisting teaching and learning *or* open-source educational content. As a result, beyond personal motivation, there is little incentive to develop and share such material. 19 | 20 | The Journal of Open Source Education (JOSE) is a scholarly journal with a formal peer review process designed to _improve the quality of the software or content submitted_. Upon acceptance into JOSE, a CrossRef DOI is minted and we list your paper on the JOSE website. 21 | 22 | ### What do you mean by "open-source educational materials"? 23 | 24 | "Open-source" implies that there are source files that are converted and 25 | rendered into a final learner-presentable form. Examples include Jupyter 26 | notebooks or plaintext/markup language documents like LaTeX, Markdown, 27 | ReStructuredText, AsciiDoc, and R Markdown. These documents should contain the 28 | lesson content and be designed to be reusable by other instructors. Lastly, 29 | the course content should make use of computation for learning with embedded 30 | or associated code snippets/programs. 31 | 32 | We do **not** mean openly available slides, lecture notes, or YouTube videos, though these may be acceptable as supplementary materials. In addition, course syllabi by themselves are not suitable for submission ([*Syllabus*](http://syllabusjournal.org/) may be more appropriate). 33 | 34 | tl;dr: your course or lesson content must contain or use code to teach. We are not focused exclusively on learning to code, but coding to learn. 35 | 36 | ### What do you mean by "open-source educational software tools"? 37 | 38 | Open-source software that serves as educational technology; examples include (but are not limited to) alternatives to learning management systems, autograders, cloud systems for lesson delivery, student collaboration tools. For these tools, peer review will follow a similar process as [JOSS](http://joss.theoj.org/about#reviewer_guidelines). 39 | 40 | ### Scope 41 | 42 | We consider submissions from all areas of academia, although our computational focus may result in more natural submissions from STEM fields—but all are welcome! 43 | 44 | Submissions must be "feature complete" to the extent that another educator could adopt, reuse, and/or extend for their purposes. 45 | 46 | The ideal submission size is a course *module*, although entire courses are also acceptable. 47 | 48 | ## The team 49 | 50 | Founding members of the editorial board: 51 | - Lorena A. Barba (editor-in-chief), George Washington University 52 | - Jason Moore, University of California, Davis 53 | - Kyle Niemeyer, Oregon State University 54 | 55 | 56 | 57 | ## The site 58 | 59 | The JOSE submission tool is hosted at http://jose.theoj.org. 60 | 61 | ## JOSE Reviews 62 | 63 | If you're looking for the JOSE reviews repository, head over here: https://github.com/openjournals/jose-reviews/issues 64 | 65 | ## Code of Conduct 66 | 67 | In order to ensure an open and welcoming community, JOSE adheres to a code of conduct adapted from the [Contributor Covenant](https://contributor-covenant.org) code of conduct. 68 | 69 | Please adhere to this code of conduct in any interactions you have in the JOSS community. It is strictly enforced on all official JOSE repositories, the JOSE website, and resources. If you encounter someone violating these terms, please let the Editor-in-Chief ([@labarba](https://github.com/labarba)) or someone on the [editorial board](http://jose.theoj.org/about#editorial_board) know and we will address it as soon as possible. 70 | 71 | > See also the [JOSE Conflict of Interest Policy](https://github.com/openjournals/joss/blob/jose/COI.md) 72 | 73 | ## Contributing 74 | 75 | The source code for this project is managed [as a branch](https://github.com/openjournals/joss/tree/jose) (`jose`) in the repository for our partner journal, the Journal of Open Source Software 76 | --------------------------------------------------------------------------------