Problem: With an increasing number of users and messages, the number of days with saved history on Slack is currently 10 (as noted by Makie’s layout creator, Julius Krumbiegel). This means that searching for past solutions, comments, or anything is quickly becoming impossible on the free plan.
Solution: Write a Slack app that allows all users to select an interval of messages, one or more packages the questions and answers in these messages pertain to, and auto submit a PR to a standard FAQ page in the documentation of those packages. The maintainers of those packages can 1) reject the PR, 2) blindly accept the PR (to later review it more carefully perhaps), or 3) curate and edit it into the documentation (either into the FAQ page or into the actual documentation of the package).
- We don’t need to worry about the lack of history on Slack (assuming of course that the history is longer than the time span it takes questions to get answers). So no need for migrating to some other web-chat service.
- Packages get a free boost to their documentation: with what I believe would be 4 user-actions (message span starts here, ends there, the relevant packages are these, send auto generated PR), the amount of effort would be minimal and more users would just do it™.
Feasibility: @SaschaMann said he can do it!
Personally, I have no idea how that would actually work (he mentioned also coupling it to github actions).
- What do you think, do you like it? Do you hate it?
- What difficulties do you foresee? How do you think we can solve these?
- Can we involve Documenter.jl somehow? Any specific format or structure this FAQ page should follow?
Alternative solutions: We could solve it with money (and pay Slack for full functionality), that’s about 850 USD or 6000 USD per month (pending on an open-source discount). Alternatively, we could spin our own web-chat server, and or use Matrix, requiring a mass-migration.