diff --git a/source/components/footer.md b/source/components/footer.md index 34a4b6f..2ad5b6b 100644 --- a/source/components/footer.md +++ b/source/components/footer.md @@ -24,12 +24,21 @@ Projects that were once on this list but removed - usually due to abandonement o ## FAQ
- Will there ever be a definitive-opensource website?
+ How about a definitive-opensource website?
A website is definitely on the roadmap. It would provide much requested features like tag based filtering and, on the backend, automate much of what we currently have to do manually. However, for the foreseeable future, the list will remain as a markdown file for one reason: to keep things simple. The current system lets me focus solely on the projects within. The complexities of web development seem unnecessary and an added pain for a task that can suffice, for now, as a markdown file.

 

The current system could also be considered a stepping stone to guage the community's needs prior to building a website, which would inherently be far more complex.
+
+ Stars aren't a good metric to guage popularity/quality.
+The minimum star count of 1k has been a major point of contention. Admittedly, star counts don't always reflect project popularity and quality. Stars are biased towards developers because they are the ones with a GitHub account, thus leaving out the input of the end users. But no solution is going to be a __one size fits all__ solution. It's critically important that as the list scales it doesn't devolve into a clutter trap, even if the price is some projects getting left out. +

 

+Stars tend to be synonomous with community recognition, making it a good starting point for further vetting to check for contributors, future plans, and popularity. Most compotent software will have no trouble reaching the 1k star count. This requirement is also just the first step for further vetting. +

 

+Artificial star counts (EX: buying stars) has also been brought up. This isn't that big of a problem, again, stars are just to quality a project for further vetting. A popular project should have lots of community activity, GitHub issues, pr's, etc. Evidence of foul play will disquality a project. +
+ ## License This project is released under the `MIT license`, hereby granting anyone to use, distribute, or modify this project for, but not limited to, commercial purposes. See the license tab for further information. diff --git a/source/components/header.md b/source/components/header.md index 873f1f2..1237e59 100644 --- a/source/components/header.md +++ b/source/components/header.md @@ -37,9 +37,9 @@ This list aims to serve as a single centralized location for the best of open so Definitive-opensource was initially a single markdown file that was edited directly. However, as the list scaled, this manual approach proved cumbersome and limited. Additionally, as popularity increased, we recieved many requests for README's of individual platforms - something that would be not be realistic to do manually.

 

- As of v0.6.2-beta, the project was fundamentally re-made. Categories and applications were put in categories.json and applications.json, respectively. Python scripts were made to generate one main list and more platform-specific lists. This was paired with GitHub actions to run the scripts when any changes were made. This makes refactoring the list format far easier and eliminates typos. + As of v0.6.2-beta, the project was fundamentally re-made. Categories and applications were put in categories.json and applications.json, respectively. Python scripts were made to generate one main list and more platform-specific lists. This was paired with GitHub actions to run the scripts when any changes were made. This opened up a world of possibilies, making refactoring the list format far easier whilst eliminating typos.

 

- This list aims to stand in the middle ground between human input and automation. Fully automated websites exist for finding open source projects, but statistics alone fails to encompass the complete picture. This list has scripts to automate markdown formatting, updating project stats, and finding potentially abandoned projects. However, the actual process of choosing which projects make it onto the list, which ones should be removed, and what tags to assign is controlled entirely by humans. + This list aims to stand in the middle ground between human input and automation. Mostly automated websites exist for finding open source projects, but statistics alone fails to encompass the complete picture. This list has scripts to automate markdown formatting, updating stats, and finding potentially abandoned projects. However, the actual processes of choosing which projects make it onto the list, which ones should be removed, and what tags to assign are controlled entirely by humans. ## Project Status diff --git a/source/scripts/generators/mainheader_generator.py b/source/scripts/generators/mainheader_generator.py index 98230eb..9309f52 100644 --- a/source/scripts/generators/mainheader_generator.py +++ b/source/scripts/generators/mainheader_generator.py @@ -15,7 +15,7 @@ def generate_mainheader():

[ definitive-opensource ]

-

A definitive list of the best of everything open source

+

The definitive list of the best of everything open source

Status: Active - Projects: {project_count}

"""