Bart Feenstra

## Definition of Done - Deploy an authoritative list of all Betty releases - Have Betty, if it is run as a packaged release, periodically check this list for updates...

- Allow Python packages to provide link types - Add links to the project configuration, such as for social media, contact details, etc - For Cotton Candy, display known link...

Refactor code that fetches associated entities for use in templates so they are Cotton Candy Jinja2 filters. Include `HasFiles.associated_files` and existing template logic.

Add a package building API that takes over the part of the `Npm` extension that builds assets for packaging. This new API then becomes useful for packaging the entire demo...

Refactor the Gramps extension to no longer parse Gramps XML directly but have Gramps APIs parae files, and perform the actual loading/importing by reading all objects from a Gramps family...

Create this as a new extension (enabled automatically?) that comes after the Wikipedia extension.

Make the existing Privatizer rules configurable through project configuration files and the GUI. A simple on/off per rule will suffice. Make each rule its own object. Perhaps leverage the future...

Does multiprocesing actually benefit Betty much now that everything is asynchronous and threaded? If we remove it, we no longer lose time pickling and can remove `Pickleable`.