• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1## Contributing to lws
2
3### How to contribute
4
5Sending a patch with a bug report is very welcome.
6
7For nontrivial problems, it's probably best to discuss on the mailing list,
8or on github if you prefer, how to best solve it.
9
10However your contribution is coming is fine:
11
12 - paste a `git diff`
13
14 - send a patch series by mail or mailing list
15
16 - paste in a github issue
17
18 - github PR
19
20are all OK.
21
22### Coding Standards
23
24Code should look roughly like the existing code, which follows linux kernel
25coding style.
26
27If there are non-functional problems I will clean them out when I apply the
28patch.
29
30If there are functional problems (eg broken error paths etc) if they are
31small compared to the working part I will also clean them.  If there are
32larger problems, or consequences to the patch will have to discuss how to
33solve them with a retry.
34
35### Funding specific work
36
37If there is a feature you wish was supported in lws, consider paying for the
38work to be done.  The maintainer is a consultant and if we can agree the
39task, you can quickly get a high quality result that does just what you need,
40maintained ongoing along with the rest of lws.
41
42