Skip to content

Commit 6e5312e

Browse files
authored
Merge pull request COMCIFS#11 from vaitkus/add-readme
Add README.md
2 parents bc45448 + e01a969 commit 6e5312e

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed

README.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
[![CIF syntax check](https://github.com/COMCIFS/Restraints_Dictionary/actions/workflows/main.yml/badge.svg)](https://github.com/COMCIFS/Restraints_Dictionary/actions)
2+
3+
# Restraints Dictionary (rstrCIF)
4+
5+
CIF data item definitions for description of restraints or constraints applied in least-squares refinement of crystal structures.
6+
7+
## Warning
8+
9+
[This dictionary](cif_rstr.dic) is the latest **draft** version.
10+
Definitions are subject to change and software should be careful not to hard-code information.
11+
The latest approved restraints dictionary is available from the [IUCr CIF website](https://www.iucr.org/resources/cif/dictionaries).
12+
13+
## Contributing
14+
15+
Contributions are very welcome, both from least-squares refinement experts and people with technical CIF knowledge.
16+
Ways of contributing include:
17+
18+
1. Raising an issue, including suggesting a new data name (see "Issues" tab above).
19+
2. Creating a pull request with suggested improvements to the dictionary.
20+
3. Commenting on already existing issues.
21+
4. Reviewing pull requests.
22+
23+
If the "Github way" is not familiar to you, we suggest looking at [some closed issues](https://github.com/COMCIFS/Restraints_Dictionary/issues?q=is%3Aissue+is%3Aclosed) and [some closed pull requests](https://github.com/COMCIFS/Restraints_Dictionary/issues?q=is%3Apr+is%3Aclosed) to see how the process works.
24+
You may also find [this wiki entry](https://github.com/COMCIFS/cif_core/wiki/Getting-started-with-Github-and-Git-for-development-of-CIF-dictionaries) helpful.
25+
26+
## Update guidelines
27+
28+
In general, any changes to the semantic content of the dictionary should be presented as a pull request.
29+
Someone other than the author of the original pull request should merge the pull request once they are satisfied that the pull request is suitable for inclusion.
30+
This protocol is not necessary for changes to the layout of the dictionary that do not change the meaning of any data names.

0 commit comments

Comments
 (0)