WP1 Selection Tools: Create a new list builder module

[audiodude]

This issue is a master tracking issue for a P0 critical user journey for WP1 Selection Tools. This issue is not expected to be closed by a single PR, but rather for additional sub-issues to be attached to it.

The steps of the CUJ are:

1. Although the WP1 selection tool provides already many way to create a list, a user may desire something else.
2. The user creates a ticket in WP1 selection tool github repo
3. The WP1 developers invite the user to create a new Python module in a form of a Python class implementing a specific 1. predefined/documented interface
4. The user or a friend codes the module in Python in PR
5. The module is reviewed, merged and deployed
6. The user now has a new way to create list and use the module UI

[kelson42]

@audiodude Should we keep this ticket open? It seems the job is done so far to me.

[audiodude]

This issue is really more of a "project" in github terminology, where each of the sub steps could be its own issue. It is tracking the steps for a contributor to add their own selection methods to WP1. It was an original goal of WP1 selection, but has been significantly put on the "back burner".

[kelson42]

@audiodude At this stage, the documentation about how to build a selection module is probably the only missing part. Seems important to me to ease onboarding of third parties.

[audiodude]

My apologies if this isn't clear, but the real goal of this issue is that the potential contributor could write only python. So it encompasses a system where the parameters of the module are declared or inferred and the relevant UI is generated automatically.

Otherwise, step 4.5 would be "The user codes the frontend of the module in Vue Javascript and integrates it with the Python".

Really, without an API for parameters this does just boil down to a CONTRIBUTING doc that says "Yes, to add a module you have to do all these steps and become a WP1 contributor" as you implied.