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
A set of components for makers to ship better products faster 🚀.
14
+
[Stack](https://github.com/paralect/stack) is an number of open-source components, resulted from years of hard work on a number of awesome products. We carefully select, document and share our production-ready knowledge with you. Stack aims to help to improve your product quality and time to market. Every component can be used as standalone component and you can combine different components to create your product or just use [Ship](https://github.com/paralect/ship).
4
15
5
16
Main concepts:
6
17
1. Every component has an owner who maintain and contribute to the component, keeping it up to date all the time and fixing any issues.
7
18
2. Every Product Stack component has extensive documentation which allow to learn it quite quickly.
8
19
9
20
## Tools
10
21
11
-
Get in touch for invitations with Andrew Orsich.
22
+
Tools we use internally to collaborate on the project. If you have any questions, suggestions or ideas — just [create an issue](https://github.com/paralect/stack/issues/new).
@@ -34,20 +45,18 @@ We distribute Product Stack components in four main ways:
34
45
3. As public docker images for isolated services under common `paralect` DockerHub account.
35
46
4. As Ansible roles for common deployment tasks
36
47
37
-
### Contribute to Product Stack
48
+
## Change Log
49
+
50
+
This project adheres to [Semantic Versioning](http://semver.org/).
51
+
Every release is documented on the Github [Releases](https://github.com/paralect/ship/releases) page.
38
52
39
-
We want contributing to Product Stack to be enjoyable, educational and fun for everyone. There are multiple ways to contribute:
53
+
## License
40
54
41
-
1. Help with documentation. Great documentation is a key.
42
-
2. Submitting bug fixes or grammar fixes.
43
-
3. Adding unit or functional tests.
44
-
4. Adding new ideas to include into Product Stack.
45
-
5. Implementing new solutions, that will be used across many products.
46
-
6. Helping answering questions in the github issues.
55
+
Ship is released under the [MIT License](LICENSE).
47
56
48
-
Read more at the [contributor guide](./CONTRIBUTOR_GUIDE.md).
57
+
## Contributing
49
58
50
-
Do you enjoy build great products just like we are? Join us!
59
+
Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
51
60
52
61
#### Contributors
53
62
@@ -60,27 +69,4 @@ Do you enjoy build great products just like we are? Join us!
60
69
7. Evgeny Leschev
61
70
8. Nastya Kostukova
62
71
63
-
TODO: find a nice way to display all contributors, their activity, packages they contribute to and their stats
64
-
65
-
### Structure of the repository
66
-
67
-
Eventually we want to group solutions into logical groups, but since there is high probability of mistake. As we just starting we will keep things simple in the beginning and come up with a structure later on. For the moment every solution should just lie in his own folder and contain README.md with comprehensive description.
0 commit comments