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
+20-15Lines changed: 20 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,25 @@
1
-
# Contributing to feed-reader
1
+
# Contributing to `@extractus/feed-extractor`
2
2
3
-
While `feed-reader` is just a simple library with personal purpose, I'm happy if it can be useful for you too.
3
+
Glad to see you here.
4
4
5
-
Anyway, I hope it always gets better, so pull requests are welcome, though larger proposals should be discussed first.
5
+
Collaborations and pull requests are always welcomed, though larger proposals should be discussed first.
6
6
7
-
As an OSS, it should follow the Unix philosophy: "do one thing and do it well".
7
+
As an OSS, it's better to follow the Unix philosophy: "do one thing and do it well".
8
8
9
-
## Installation
10
9
11
-
- Ensure you have `node` and `npm` installed.
12
-
- After cloning the repository, run `npm install` in the root of the repository.
13
-
- Run `npm test` to ensure that everything works correctly in your environment.
10
+
## What you can contribute?
14
11
15
-
If it works well, you can start modifying your fork.
12
+
We are planing to re-write this tool in TypeScript and make it Deno-first library.
13
+
If you are interested, please join our team.
16
14
17
-
In this process, you can use [`node eval.js` command](https://github.com/ndaidong/feed-reader#quick-evaluation) to evaluate your changes.
15
+
Besides that, you can also:
16
+
17
+
- Test and report bugs
18
+
- Fix unresolved issues
19
+
- Improve performance
20
+
- Write better documentation
21
+
- Create examples or build demos
22
+
- Feedback on software design and APIs
18
23
19
24
20
25
## Third-party libraries
@@ -32,7 +37,7 @@ Make sure your code lints before opening a pull request.
32
37
33
38
34
39
```bash
35
-
cd feed-reader
40
+
cd feed-extractor
36
41
37
42
# check coding convention issue
38
43
npm run lint
@@ -49,18 +54,18 @@ npm run lint:fix
49
54
Be sure to run the unit test suite before opening a pull request. An example test run is shown below.
50
55
51
56
```bash
52
-
cd feed-reader
57
+
cd feed-extractor
53
58
npm test
54
59
```
55
60
56
-

61
+

57
62
58
63
If test coverage decreased, please check test scripts and try to improve this number.
59
64
60
65
61
66
## Documentation
62
67
63
-
If you've changed APIs, please update README and [the examples](https://github.com/ndaidong/feed-reader/tree/main/examples).
68
+
If you've changed APIs, please update README and [the examples](https://github.com/extractus/feed-extractor/tree/main/examples).
64
69
65
70
66
71
## Clean commit histories
@@ -79,6 +84,6 @@ For people new to git, please refer the following guides:
79
84
80
85
## License
81
86
82
-
By contributing to `feed-reader`, you agree that your contributions will be licensed under its [MIT license](https://github.com/ndaidong/feed-reader/blob/main/LICENSE).
87
+
By contributing to `@extractus/feed-extractor`, you agree that your contributions will be licensed under its [MIT license](https://github.com/extractus/feed-extractor/blob/main/LICENSE).
-[article-extractor](https://github.com/extractus/article-extractor): extract main article from given URL
17
+
-[oembed-extractor](https://github.com/extractus/oembed-extractor): extract oEmbed data from supported providers
18
18
19
19
You can use one or combination of these tools to build news sites, create automated content systems for marketing campaign or gather dataset for NLP projects...
0 commit comments