Skip to content

Commit e1c0e6a

Browse files
Update Readme.
1 parent b90df4a commit e1c0e6a

File tree

1 file changed

+3
-55
lines changed

1 file changed

+3
-55
lines changed

README.md

Lines changed: 3 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -1,57 +1,5 @@
1-
# General Repository Template
1+
# access-parsers
22

3-
A general template repository for default settings when creating new repositories.
3+
*A Python package of various functions to read and write configuration files for the models developed at [ACCESS](https://github.com/ACCESS-NRI).*
44

5-
This repository uses the Apache-2.0 license. `COPYRIGHT.txt` contains a current copyright statement which should be included at the top of all files.
6-
7-
When creating a new repository you [can use this repository as a template](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template), to automate the creation of the correct license and COPYRIGHT statement.
8-
9-
## COPYRIGHT Header
10-
11-
Best practice suggests adding a copyright statement at the top of every source code file, or text file where it is possible to add a copyright statement without interfering with the purpose of the file. The reasoning is if a file is separated from the repository in which it resides then it may not be possible to ascertain it's licensing, which may hamper re-use.
12-
13-
Making this as short and concise as possible reduces the overhead in including such a copyright statement. To that end using [SPDX identifiers](https://spdx.dev/ids/) is simple, efficient, portable and machine-readable.
14-
15-
### Examples
16-
17-
An example, short, copyright statement is reproduced below, as it might appear in different coding languages. Copy and add to files as appropriate:
18-
19-
#### plaintext
20-
It is common to include copyright statements at the bottom of a text document or website page
21-
```text
22-
© 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details.
23-
SPDX-License-Identifier: Apache-2.0
24-
```
25-
26-
#### python
27-
For code it is more common to include the copyright in a comment at the top
28-
```python
29-
# Copyright 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details.
30-
# SPDX-License-Identifier: Apache-2.0
31-
```
32-
33-
#### shell
34-
```bash
35-
# Copyright 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details.
36-
# SPDX-License-Identifier: Apache-2.0
37-
```
38-
39-
##### FORTRAN
40-
```fortran
41-
! Copyright 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details.
42-
! SPDX-License-Identifier: Apache-2.0
43-
```
44-
45-
#### C/C++
46-
```c
47-
// Copyright 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details.
48-
// SPDX-License-Identifier: Apache-2.0
49-
```
50-
51-
### Notes
52-
53-
Note that the date is the first time the project is created.
54-
55-
The date signifies the year from which the copyright notice applies. **NEVER** replace with a later year, only ever add later years or a year range.
56-
57-
It is not necessary to include subsequent years in the copyright statement at all unless updates have been made at a later time, and even then it is largely discretionary: they are not necessary as copyright is contingent on the lifespan of copyright holder +50 years as per the [Berne Convention](https://en.wikipedia.org/wiki/Berne_Convention).
5+
![CI](https://github.com/ACCESS-NRI/access-parsers/actions/workflows/ci.yml/badge.svg) [![License](https://img.shields.io/badge/license-Apache%202.0-blue?style=flat-square)](https://opensource.org/license/apache-2-0) [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)

0 commit comments

Comments
 (0)