57 karma · joined January 31, 2020
Do you have a blog post about your automated fail2ban rule generation?
I have noticed this issue that Fork Freshness tries to solve. My example is Twitter's project murder https://github.com/lg/murder When a project becomes unmaintained whether officially or unofficially, the future home is often lost unless the original points to the new home at the top of the README file. You can dig within GitHub in the Insights > Network section to get a visual glimpse of what has changed since. https://github.com/lg/murder/network The original repository put up a notice that the project is unmaintained and archived the project which effectively ends the project in practice. In this case, ervinb's fork seems to be the most active commits before being abandoned. https://github.com/ervinb/murder Other forks also had independent commits that never were pulled into other projects. Looking at the network method fails to differentiate 30 grammar fixes from 30 new features without digging into each promising looking fork. Even then, you may miss a single commit that included more work then the entirety of the other commits. Disclosure: I have not worked on murder.
This is a serious problem and I hope we solve it.
* It is an injustice to require students to sacrifice their freedom to proprietary software in pursuit of an education.
* Using free software in the classroom communicates the importance of values key to a free society: sharing, social responsibility, and independence.
* With its focus on study and collaboration, free software is far more suited to the spirit of pedagogy than the dependence and abuse caused by proprietary software.