Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 0 additions & 13 deletions 7-contributing/CONDUCT.md

This file was deleted.

1 change: 1 addition & 0 deletions 7-contributing/CONDUCT.md
50 changes: 0 additions & 50 deletions 7-contributing/LICENSE.md

This file was deleted.

1 change: 1 addition & 0 deletions 7-contributing/LICENSE.md
114 changes: 0 additions & 114 deletions 7-contributing/README.md

This file was deleted.

1 change: 1 addition & 0 deletions 7-contributing/README.md
13 changes: 13 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# Contributor Code of Conduct

As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, or religion.

Examples of unacceptable behaviour by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.

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. Project maintainers who do not follow the Code of Conduct may be removed from the project team.

Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported by opening an issue or contacting one or more of the project maintainers.

This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.0.0, available at [https://contributor-covenant.org/version/1/0/0/](https://www.contributor-covenant.org/version/1/0/0/).
114 changes: 114 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,114 @@
(contributing-lesson)=
# Contributing

[FCC Software][fcc-software] tutorials, as well as the whole [Key4hep][key4hep]
ecosystem, is an open source project, and we welcome contributions of all kinds:

* New lessons;
* Fixes to existing material;
* Bug reports; and
* Reviews of proposed changes.

By contributing, you are agreeing that we may redistribute your work under
[these licenses][license].
You also agree to abide by our [contributor code of conduct][conduct].


## Getting Started

1. We use the [fork and pull][gh-fork-pull] model to manage changes.
GitHub also provides more information about [forking a repository][gh-fork]
and [making a Pull Request][gh-pull] on their website.

2. For our lessons, you should branch from and submit pull requests against
the `main` branch.

3. When editing lesson pages, you need to only commit changes to the Markdown
source files.

4. To build the tutorials please follow the
[instructions](#building-the-tutorials).

5. If you're looking for things to work on, please see
[the list of issues for this repository][issues]. Comments on issues and
reviews of pull requests are equally welcome.


## Building the tutorials

### Requirements

Make sure you have `venv` (virtual environment) in your working directory. It
can be created with the following command:
```bash
python3 -m venv venv
```
Activate it in your shell and install the requirements, which are gathered in a
file provided by the repository.
```bash
source venv/bin/activate
pip3 install -r requirements.txt
```
After sourcing, your shell prompt will be augmented by the `(venv)` prefix, e.g.
```
(venv) mylaptop:~/fcc/fcc-tutorials
```

:::{admonition} Building `fcc-tutorials` in the Key4hep stack
:class: callout dropdown

In case you are editing the tutorials using the FCC Software (Key4hep) stack, it
is necessary to clear the `PYTHONPATH` environment variable after sourcing of
the stack
```bash
source /cvmfs/sw.hsf.org/key4hep/setup.sh
unset PYTHONPATH
```

Using of the FCCSW stack might also be needed in cases when the Python provided
by your OS is too old.
:::

### Building

The documentation pages are build by executing
```bash
sphinx-build -b html . build
```

### Browsing the result

Start a web server to host the generated files from `build` directory
```bash
python -m http.server -d build
```

You should be able to see your local version by opening a web-browser and
navigating to [http://localhost:8000](http://localhost:8000).


## How to Write

More information about how to write the tutorials for the FCC Software visit
[](./../6-developing-fccsw/FccDocPage.md#how-to-write-mardown).


## Legal

```{eval-rst}
.. toctree::

CONDUCT.md
LICENSE.md
```


[fcc-software]: https://fccsw.web.cern.ch/
[key4hep]: https://key4hep.web.cern.ch/
[conduct]: CONDUCT.md
[license]: LICENSE.md
[issues]: https://github.com/HEP-FCC/fcc-tutorials/issues
[pro-git-chapter]: https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project
[gh-fork]: https://help.github.com/en/articles/fork-a-repo
[gh-pull]: https://help.github.com/en/articles/about-pull-requests
[gh-fork-pull]: https://reflectoring.io/github-fork-and-pull/
50 changes: 50 additions & 0 deletions LICENSE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
# License

## Instructional Material

All instructional material is made available under the [Creative Commons
Attribution license][cc-by-human]. The following is a human-readable summary of
(and not a substitute for) the [full legal text of the CC BY 4.0
license][cc-by-legal].

You are free to:

* to **Share** --- copy and redistribute the material in any medium or format
* to **Adapt** --- remix, transform, and build upon the material for any
purpose, even commercially.

The licensor cannot revoke these freedoms as long as you follow the license
terms.

Under the following terms:

* **Attribution** --- You must give appropriate credit, provide a [link to the
license][cc-by-human], and indicate if changes were made. You may do so in
any reasonable manner, but not in any way that suggests the licensor endorses
you or your use.

* **No additional restrictions** --- You may not apply legal terms or
technological measures that legally restrict others from doing anything the
license permits.

Notices:

* You do not have to comply with the license for elements of the material in
the public domain or where your use is permitted by an applicable exception
or limitation.
* No warranties are given. The license may not give you all of the permissions
necessary for your intended use. For example, other rights such as publicity,
privacy, or moral rights may limit how you use the material.


## Software

Except where otherwise noted, the example programs and other software provided
by FCC Software are made available under the [OSI][osi]-approved
[Apache 2.0][apache-license] license.


[cc-by-human]: https://creativecommons.org/licenses/by/4.0/
[cc-by-legal]: https://creativecommons.org/licenses/by/4.0/legalcode
[apache-license]: https://opensource.org/license/apache-2-0/
[osi]: https://opensource.org
2 changes: 2 additions & 0 deletions conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,8 @@
'venv',
'.github',
'README.md',
'CONTRIBUTING.md',
'LICENSE.md',
'archive'
]

Expand Down
Loading