Open oxalorg opened 4 years ago
This along with #8 will make it cleaner to not merge all data into a single list, and instead maintain multiple lists.
So each importer will only be responsible to maintain their own list, which will avoid conflicts.
Okay these are the sources we have available:
projects.json
which lists the "better" alternatives, and rejected.ls
- a LiveScript file which lists the projects to "avoid". The problem is that the avoid list does not have URLs to those servicesTo automate prism-breaks data, we'll have to write the script in Javascript as we will have to transpile their LiveScript data block into JS/JSON. We will also have to provide our own mapping of slug: urlPattern
.
To automate switching software data we need to parse markdown files. Once again we will have to provide our own mapping of slug: urlPattern
.
Prism-break has 73 entries in their avoid list, and S.S has 54. But I feel "switching.software" has more commonly used services, and thus it looks like the better list.
Maybe we should start with importing from switching.software first then.
Projects like switching.software, and others recommended in #7 are already doing the hard work of maintaing better suggestions.
We should write a script which imports from their data source to ours.
The importers can be made to run using Github actions CRON scheduling and to create a PR if there is a change detected.