In all the discussions about TW’s future, I’ve been thinking alot about what data we have to discuss and make key decisions… In the recent post about backward compatibility this need was expressed as :
So lets discuss how to figure this out… My opening suggestions would be:
- Create a dedicated plugin for this - users would then be implicitly opting in by installing the plugin.
- That plugin starts with a consent banner to get more explicit consent to collect any data… Not unlike a user agreement - this will need some legal advice/discussion here so that it does express compliance with local laws.
- Any data that is collected by the plugin is available for the user to review before it is sent.
- The user decides ultimately to send the data via an api somewhere (any thoughts welcome)
- The plugin is upgraded whenver there is new set of data queries to collect - and again the user has control of these being submitted.
The other discussion point for here that may be ongoing is what data do we want to collect. Some obvious ideas based on other discussions include:
- What plugins does a user have in their wiki - This would help uncover what the total ecosystem of available plugins are and guide us to get them documented better in TW.com or added as official plugins
- What features marked for depreciation are still in use - you could search for
\definefor example to see if users have made the transition from macros to procedures … - What version of what platforms are used - help us validate the version of javascript to use in the core.
Any others that we could start with ?
Cheers : CB