What should be done, in the Vamp plugins Github org?

[cannam]

Hello all!

I recently created this organisation with a view to making Vamp plugin developer resources easier to find, maintain, and contribute to.

I imagine it to hold anything useful for people developing Vamp plugins and hosts, but mostly not for end-users of plugins (that's what the website is for) or for development of specific hosts such as Sonic Visualiser (they have their own homes).

Obvious goals might be:

1. Put APIs, SDKs, test tools etc where developers expect to find them, and make them work in ways developers expect
2. Take fullest advantage of free facilities like CI and artifact builds
3. Make it easier for people to contribute, particularly in the areas of documentation or examples, but also generally keeping things up-to-date and working nicely

Here's a first draft list of things to consider. I'm just jotting things down here as a preliminary to creating any individual tracker items, would appreciate more thoughts and contributions for this list:

• Ensure the front-page README (i.e. the one shown here) is coherent, helpful, and well organised, and links to all necessary info
• Update developer resource links on vamp-plugins.org so that they point here - probably the whole "for developers" aspect of the site should be removed and replaced with a link here
• Go through the individual projects (SDK, testers, etc) and update each with:
  • Friendly Markdown READMEs
  • Build tools that people today know how to invoke (i.e. CMake, much as I loathe it)
  • CI builds for Win, Mac, Linux that all produce downloadable artifacts
  • Code review for warnings etc generated by more modern compilers
  • General tidy to acknowledge Github-first arrangements, e.g. removing old Mercurial branches and metadata
• Decide what to do about the Python projects! There are at least:
  • VamPy for writing plugins in Python, which is of very little use because it has never been updated to Python 3 (unless anyone ever forked it for this?)
  • VamPy Host for writing hosts in Python, which approximately works and was uploaded to PyPI as vamp, but which I then failed to maintain so it doesn't really work, leading to...
  • Vamp Host, @gesellkammer's fork of VamPy Host, which I think he has continued to maintain within PyPI, as vamphost
  • And a set of Python host bindings in @lukasberbuer's RT Vamp Plugin SDK, available in PyPI as rtvamp
• Wiki-ify all the extant documentation, including the old PDF programmers guide and suchlike
• Update and make new builds of the Vamp Plugin Pack
• Although the goal is to totally replace the code.soundsoftware resources as far as third-party developers are concerned (and so to fully embrace the long-inevitable), it would be good to consider how to be helpful to anyone who does continue to land over there

What else?

On the admin side, I need to take steps to raise the "bus factor" and make it possible for doc updates and uncontroversial code fixes to be merged more readily.

And, it's possible I'm fixating on small updates and missing the big picture in some way - if so, how?