calyx 0.17.0 → 0.17.1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 9661f918b6f2a9bed30724381dc5236d84e9aa1f
4
- data.tar.gz: b0afda09a017d87616971ad7b9b13eb88bf84958
3
+ metadata.gz: 80489e301bc4d995dea429bda6759c17fe8c0311
4
+ data.tar.gz: a16583ceeb4bc13711fe94fa5cecdde6167b4fde
5
5
  SHA512:
6
- metadata.gz: 24bb224aea5f2bc8a0e414b783206abb1a00cb47a2ec0ad1f94aee44dc0970adb476c9527e37bf1e443212c410694b1d0b435eb4c7ef4227d8e406165f2fa3d7
7
- data.tar.gz: 5d2892b7c9a3b363a7b702c9972b2d7f00e158a386b4026fa5d04f24ce1f978abb70dd6bfed24196e0656c0ef4913208a2313602ce591bb2cf7d98eaee7f17bd
6
+ metadata.gz: 3dd4f9428eae4ce7d454de3c9ea1572253dda2d43e97297c1daabdbb00ac3c1473ffe9e997af1ccce3988435a380d196071ea42d1eabeb35bec9b2e64c01211f
7
+ data.tar.gz: 4fc6835c4986f63bf80d014bd787d6bc1160eb5e169f8bd2fcfd9c35da9ddfb04af4ab4341127c6fa2084f5654c3e28875f7a310f22376d03c93911bf5b06e39
@@ -0,0 +1,46 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ 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.
6
+
7
+ ## Our Standards
8
+
9
+ Examples of behavior that contributes to creating a positive environment include:
10
+
11
+ * Using welcoming and inclusive language
12
+ * Being respectful of differing viewpoints and experiences
13
+ * Gracefully accepting constructive criticism
14
+ * Focusing on what is best for the community
15
+ * Showing empathy towards other community members
16
+
17
+ Examples of unacceptable behavior by participants include:
18
+
19
+ * The use of sexualized language or imagery and unwelcome sexual attention or advances
20
+ * Trolling, insulting/derogatory comments, and personal or political attacks
21
+ * Public or private harassment
22
+ * Publishing others' private information, such as a physical or electronic address, without explicit permission
23
+ * Other conduct which could reasonably be considered inappropriate in a professional setting
24
+
25
+ ## Our Responsibilities
26
+
27
+ 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.
28
+
29
+ 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.
30
+
31
+ ## Scope
32
+
33
+ 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.
34
+
35
+ ## Enforcement
36
+
37
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [me@maetl.net](mailto:me@maetl.net). 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.
38
+
39
+ 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.
40
+
41
+ ## Attribution
42
+
43
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44
+
45
+ [homepage]: http://contributor-covenant.org
46
+ [version]: http://contributor-covenant.org/version/1/4/
data/CONTRIBUTING.md CHANGED
@@ -1,10 +1,6 @@
1
1
  # Contributing to Calyx
2
2
 
3
- Calyx is an open source project and contributions are welcome with the caveat that this is very much a personal creative project by Mark Rickerby, so keep that context in mind if you’re considering drastic code changes.
4
-
5
- Changes that fix bugs and improve test coverage will generally be merged on-the-spot. Larger changes that introduce new features should harmonise with the vision, goals and style of the project. If in doubt, just ask in advance.
6
-
7
- Should Calyx become more popular, these guidelines are likely to become more community-oriented, and I’ll look at handing project stewardship over to the community with a more formal project charter and structure.
3
+ Calyx is an open source project and contributions are welcome.
8
4
 
9
5
  ## General Contributions
10
6
 
@@ -14,6 +10,8 @@ It’s really helpful to contribute to discussion on open issues, reporting bugs
14
10
 
15
11
  ## Code Contributions
16
12
 
13
+ Changes that fix bugs and improve test coverage will generally be merged on-the-spot. Larger changes that introduce new features should harmonise with the vision, goals and style of the project. If in doubt, just ask in advance.
14
+
17
15
  ### Submitting Changes
18
16
 
19
17
  Changes to the source code and documentation should be submitted as a pull request on GitHub, corresponding to the following process:
@@ -21,9 +19,9 @@ Changes to the source code and documentation should be submitted as a pull reque
21
19
  - Fork the repo and make a new branch for your changes
22
20
  - Submit your branch as a pull request against the master branch
23
21
 
24
- If any aspects of your changes are ambiguous or unclear, use the pull request description to explain and provide further context (including code samples as necessary).
22
+ If any aspects of your changes need further explanation, use the pull request description to provide further detail and context (including code samples as necessary).
25
23
 
26
- Please don’t bump the version as part of your changes (this happens separately).
24
+ Please don’t bump the version as part of your pull request (this happens separately).
27
25
 
28
26
  ### Pull Request Checklist
29
27
 
@@ -36,14 +34,4 @@ Please don’t bump the version as part of your changes (this happens separately
36
34
 
37
35
  ## Code of Conduct
38
36
 
39
- 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.
40
-
41
- 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.
42
-
43
- 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.
44
-
45
- The maintainer has 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.
46
-
47
- Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported by opening an issue or contacting the maintainer.
48
-
49
- *From the [Contributor Covenant](http://contributor-covenant.org), version 1.0.0, available at [http://contributor-covenant.org/version/1/0/0/](http://contributor-covenant.org/version/1/0/0/).*
37
+ Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
data/README.md CHANGED
@@ -545,7 +545,7 @@ Rough plan for stabilising the API and features for a `1.0` release.
545
545
  | `0.14` | ~~Support for Ruby 2.4~~ |
546
546
  | `0.15` | ~~Options config and ‘strict mode’ error handling~~ |
547
547
  | `0.16` | ~~Improve representation of weighted probability selection~~ |
548
- | `0.17` | Return result object from `#generate` calls |
548
+ | `0.17` | ~~Return result object from `#generate` calls~~ |
549
549
 
550
550
  ## Credits
551
551
 
data/docs/404.html CHANGED
@@ -1,24 +1,7 @@
1
1
  ---
2
2
  layout: default
3
3
  ---
4
-
5
- <style type="text/css" media="screen">
6
- .container {
7
- margin: 10px auto;
8
- max-width: 600px;
9
- text-align: center;
10
- }
11
- h1 {
12
- margin: 30px 0;
13
- font-size: 4em;
14
- line-height: 1;
15
- letter-spacing: -1px;
16
- }
17
- </style>
18
-
19
- <div class="container">
20
- <h1>404</h1>
21
-
22
- <p><strong>Page not found :(</strong></p>
23
- <p>The requested page could not be found.</p>
4
+ <div class="content">
5
+ <h1>Not found</h1>
6
+ <p>Whatever you were looking for is not here.</p>
24
7
  </div>
data/docs/_config.yml CHANGED
@@ -12,6 +12,8 @@ markdown: kramdown
12
12
  plugins:
13
13
  - jekyll-feed
14
14
 
15
+ highlighter: rouge
16
+
15
17
  # Exclude from processing.
16
18
  # The following items will not be processed, by default. Create a custom list
17
19
  # to override the default setting.
@@ -4,13 +4,30 @@
4
4
  <meta charset="utf-8">
5
5
  <meta name="viewport" content="width=device-width, initial-scale=1">
6
6
  <title>Calyx</title>
7
+ <link href="https://fonts.googleapis.com/css?family=Oxygen+Mono" rel="stylesheet">
8
+ <link href="https://fonts.googleapis.com/css?family=Arimo:400,700|Libre+Franklin:300,400,500,600,700|Work+Sans:700,800" rel="stylesheet">
7
9
  <link rel="stylesheet" href="/assets/calyx-docs.css">
8
10
  </head>
9
11
  <body>
10
- <section class="section">
11
- <div class="container">
12
- {{ content }}
12
+ <div class="container">
13
+ <div class="row">
14
+ <div class="col docs-sidebar">
15
+ {% include contents.html %}
16
+ </div>
17
+ <div class="col docs-content">
18
+ <div class="content">
19
+ {{ content }}
20
+ </div>
21
+ <div class="content-footer">
22
+ <div class="content-footer-col">
23
+ <a href="#">Prev</a>
24
+ </div>
25
+ <div class="content-footer-col">
26
+ <a href="#">Next</a>
27
+ </div>
28
+ </div>
29
+ </div>
13
30
  </div>
14
- </section>
31
+ </div>
15
32
  </body>
16
33
  </html>