lucas.mathieu/cachet-docker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix issues links

Browse Source
This commit is contained in:
James Brooks
2014-11-24 16:58:56 +00:00
parent ff37e13221
commit b5529bcb2b
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -18,11 +18,11 @@ See the [INSTALL.md](/INSTALL.md) document for more information. If you'd like t
Are you looking to help out and contribute towards Cachet, awesome! There is a lot to do before the [first milestone](https://github.com/jbrooksuk/Cachet/milestones/First%20Release) is reached, including:
- **Revamp the existing design** [#2](/issues/2). Whether you think that we should drop Bootstrap and we use a custom framework or we apply awesome styles, fork Cachet, make your changes and propose them!
- **Revamp the existing design** [#2](https://github.com/jbrooksuk/Cachet/issues/2). Whether you think that we should drop Bootstrap and we use a custom framework or we apply awesome styles, fork Cachet, make your changes and propose them!
+ A good design for Cachet needs to also support a Setup and Management backend.
- **Setup Page** [#12](/issues/12). Work has started on this, but there is a lot more that needs to be setup including; users, components, incidents and templates.
- **Dashboard** [#11](/issues/11). Currently there is no way to get the incidents and components into the database without a bit of messing around.
- **API** [#3](/issues/3). All good services need an API and Cachet is no exception. An API will allow third-party integration and vice-versa.
- **Setup Page** [#12](https://github.com/jbrooksuk/Cachet/issues/12). Work has started on this, but there is a lot more that needs to be setup including; users, components, incidents and templates.
- **Dashboard** [#11](https://github.com/jbrooksuk/Cachet/issues/11). Currently there is no way to get the incidents and components into the database without a bit of messing around.
- **API** [#3](https://github.com/jbrooksuk/Cachet/issues/3). All good services need an API and Cachet is no exception. An API will allow third-party integration and vice-versa.
However, if you're not looking to work on anything big then some of our issues will be tagged with the **enjoy** label. Feel free to take a look at these as they should be much easier to deal with.