-
Updated
May 26, 2020 - Shell
decisions
Here are 42 public repositories matching this topic...
-
Updated
May 26, 2020
-
Updated
Feb 27, 2018
Right now we don't have any rules in place for how to write and format our feature files.
We've already decided that we don't want the name of the files to represent the feature text in ui-core, but apart from that, there has been no other decision made and it'd be nice to have a consistent style across repositories
Current inconsistencies
Steps are written from different perspec
-
Updated
Jan 15, 2020 - Jupyter Notebook
-
Updated
Jan 16, 2020 - Python
Clean up some of the default pages and language in Sails, for example to contact form to make it more project focussed and a clean slate on which to build.
As @Bachibouzouk pointed out: Information regarding OEP-metadata is scattered across this organisation. We need to clean this up and here is my proposal:
OMI would be a good place for metadata in general (I think we had a recent discussion regarding that!?). BUT: Specification, documentation and implementation are three different t
-
Updated
Mar 18, 2017 - Python
-
Updated
Jun 7, 2017 - PHP
-
Updated
Feb 11, 2019
-
Updated
Aug 20, 2019 - HTML
-
Updated
Oct 19, 2017 - Ruby
-
Updated
Sep 13, 2017 - Python
-
Updated
Dec 1, 2018 - R
-
Updated
Jul 27, 2018 - Python
-
Updated
Sep 16, 2019 - TeX
-
Updated
Aug 15, 2017
-
Updated
Jan 14, 2019 - CSS
-
Updated
May 12, 2019 - Python
-
Updated
May 29, 2020 - TeX
Improve this page
Add a description, image, and links to the decisions topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the decisions topic, visit your repo's landing page and select "manage topics."


At present the @dwyl mission statement is in multiple places and the one in HQ:
https://github.com/dwyl/hq#mission-statement
is out of sync with the recently updated dwyl/start-here#191 >> [/start-here/mission.md](https://github.com/dwyl/start-here/blob/931fb1bf29ee821b62f05ffc