forked from awslabs/damo
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCONTRIBUTING
44 lines (31 loc) · 1.57 KB
/
CONTRIBUTING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
General Process
===============
For contributions, please refer to the linux kernel development process[1] and
send patches to [email protected] or pull-requests via Github. The contributions
should have proper 'Signed-off-by:' tags[2]. The tag will be considered the
same as that of the linux kernel development process.
There are two branches, 'master' and 'next'. Changes first merged in 'next',
get tested, and finally merged in 'master', if the tests show no problem. So,
please base your work on 'next'.
[1] https://docs.kernel.org/process/index.html
[2] https://docs.kernel.org/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
What To Do, First?
==================
Testing First
-------------
If you want to participate in the development but are unsure what to do first,
you could consider running DAMON tests suite
(https://github.com/awslabs/damon-tests) on your system. It might reveal some
issues in DAMO or DAMON to you.
If you have more interest in development of DAMO itself than DAMON, you could
consider running only DAMO tests on your system. You can run the tests via
below command from the root of DAMO.
$ sudo ./tests/run.sh
It might reveal some issues in DAMO to you.
TODO list
---------
There is a list of times that need to be done in 'TODO' file of this repo. If
you don't have specific task to do at the moment, you could consider finding
one from the file. The list is not well managed at the moment, and the items
may not well explained. Please feel free to reach out to the original author
of the item for asking details.