|
1 |
| -# Contributing to Atom |
2 |
| - |
3 |
| -:+1::tada: First off, thanks for taking the time to contribute! :tada::+1: |
| 1 | +# Contributing to DataASAP |
4 | 2 |
|
| 3 | +:+1::tada: First off, thanks for taking the time to contribute! :tada::+1 |
5 | 4 | There is a lot of work that I'd like to do to this application to make it more useful.
|
6 | 5 |
|
7 | 6 | DataASAP was developed using the following technologies:
|
8 | 7 | * Electron
|
9 | 8 | * React-Redux-Router
|
| 9 | +* [Electron-React boilerplate](https://github.com/jschr/electron-react-redux-boilerplate) |
10 | 10 | * Semantic UI React
|
11 | 11 | * Javascript
|
12 | 12 | * Electron Builder
|
13 | 13 |
|
14 | 14 | #### Current State
|
15 |
| -The current state is that it supports most current NCPDP transactions (Telecom D.0, SCRIPT 10.6 and the newer SCRIPT 20170714), though I can't guarantee all. Ideally, I'd like to include X12 and HL7 transactions. |
| 15 | +The current state of DataASAP is that it supports most current NCPDP transactions (Telecom D.0, SCRIPT 10.6 and the newer SCRIPT 20170714), though I can't guarantee all. Ideally, I'd like to include X12 and HL7 transactions. |
16 | 16 |
|
17 |
| -I've tried to keep the interface clean and simple, the interface goal is for someone to install the software and start using it by just looking at it. |
| 17 | +I've tried to keep the interface clean and simple with the interface goal being that someone can use it by just looking at it. |
18 | 18 |
|
19 |
| -The [Issues section](https://github.com/dcheli/dataASAP/issues) contains items I am aware of that need work. Some items are very broad and can/will be broken down into smaller items in time. |
| 19 | +The [Issues section](https://github.com/dcheli/dataASAP/issues) contains items I am aware of that need work. Some items are quite broad and can/will be broken down into smaller items in time. |
20 | 20 |
|
21 | 21 | #### Developers
|
22 |
| -If you are a developer, are interested in the tech stack I am using and want to contribute, please contact me. I know that there are many opportunities for refactoring, some identified in the issues section and others that I may not be aware of. |
| 22 | +If you are a developer, have an interest in the tech stack I am using and want to contribute, please contact me. I know there there are many opportunities for refactoring, some identified in the issues section and others that I may not be aware of. |
23 | 23 |
|
24 |
| -As mentioned above, I'd like to add X12 and HL7, but am open to other transaction sets as well. |
| 24 | +New features I'd like to add inlcude adding support for X12 and HL7. I am open to supporting other transaction sets as well. |
25 | 25 |
|
26 | 26 | #### Testers
|
27 |
| -If you are a tester, I can use some help. Does this run on your platform? Are there transactions that aren't supported well? Do the features work? Do you have sample data that you can add to the test folder? Is there a good way to automate testing this? |
| 27 | +If you are a tester, I can use some help. Does this run on your platform? Do the current features work? Do you have sample data that you can add to the test folder? Is there a good way to automate testing this? |
28 | 28 |
|
29 | 29 | #### Suggestors
|
30 | 30 | I am open to suggestions and will prioritize suggestions based on my time, interest from others, and time that possibly some other developers and testers would want to work on them.
|
|
0 commit comments