-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate introp testing suite output? #160
Comments
While I find it a useful idea to integrate the Interop Suite output into o.o, in some manner, I'd be hesitant to present it as a quantified measure of a library's properties (the test suite itself warns against that approach to its output, after all). My suggestion for a straightforward next step would be to define some cutoff date (i'd suggest 1.1.2020), and move all entries that haven't seen movement in their source repos since that cutoff date to a list of "sleeping OpenPGP software". |
If that approach sounds reasonable, then I could start prepare a PR for it soonish |
That sounds like a reasonable first step, however this would only apply to open source software... |
Agreed that the approach doesn't neatly apply to closed source software. However, I'm hoping that in practice we could find sufficiently serviceable alternative metrics (such as recent releases). But sure, that's a gray area, and it can't be conclusively un-greyed, as I see it. I'd favor a best effort approach of guesstimating "seems to be worked on". We'd also probably not count merely "cosmetic" commits on open source projects (e.g. a project where only the |
We should consider how we can best indicate to site visitors the health/activity of projects listed on the various pages. It would be preferable if this was done using some reasonably objective mechanism, and better still if this was automated/unattended. One suggestion is that we could use the output of the interop test suite (https://sequoia-pgp.gitlab.io/openpgp-interoperability-test-suite/results.html).
The text was updated successfully, but these errors were encountered: