You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-22Lines changed: 4 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,32 +7,17 @@ Please note we have a [CODE OF CONDUCT](/docs/Code_of_Conduct.md), please follow
7
7
8
8
## Overview
9
9
10
-
In this section you should provide a semi-detailed overview of your project. This overview should include a statement of the
11
-
problem you're looking to solve, maybe some bullet points, and a statement defining the solution.
10
+
This project aims to offer simple utilities for API development on AWS Lambda. Some of these utilities may work for other frameworks like Express, however this is just a happy coincidence.
12
11
13
12
### Non Goals
14
13
15
-
This should be a list of bullets of related features you are not planning to add to the project. This should be adjusted based
16
-
on the maturity of the product.
17
-
18
-
### Minimum Viable Product
19
-
20
-
As with the _Non Goals_ this should be a bulleted list of features you will include in your product. This list can be adjusted
21
-
based on the maturity of the product.
22
-
23
-
### Roadmap
24
-
25
-
Provide an esitmate of when work will be completed, or a link to any kanban boards you may have.
14
+
This product does not aim to offer everything needed for RESTful development on AWS Lambda, just a jump-start. We are getting the low hanging fruit to speed up development, nothing more.
26
15
27
16
## Technology and Code
28
17
29
-
Provide a bulleted list of your applicable tech stack. Below is the standard sentence to link to the Best_Practices doc. You can also link
30
-
to the Tech_Spec.
31
-
32
-
Please update the [Tech Spec](/docs/Tech_Spec.md) with a full breakdown of the project and workflows then link it here.
18
+
This is an npm package so it's Typescript/Javascript.
33
19
34
-
Please update the [Best Practices](/docs/Best_Practices.md) with code standards, git standards, and other guidance for writing clean and well
35
-
documented code then link it here.
20
+
Please see [Best Practices](/docs/Best_Practices.md) for Typescript coding standards.
36
21
37
22
### Pull Request Process
38
23
@@ -52,6 +37,3 @@ The best ways to get in touch with us is via Slack. An active Slack link can be
0 commit comments