We are getting small amounts of spam in the playground group but currently we have no way to deal with this.
As all the actual groups require application, they are unlikely to have this kind of spam issue, so it’s just something for the playground group.
We chatted a bit about it and a few ideas came up:
- database admins manually delete it (those being @nicksellen and @tiltec)
- we add an admin interface (using django admin, for example) that allows a select number of people to delete messages for the playground group only
- we remove the whole concept of a playground group
- periodically reset the content in the playground group
Option 3 actually seemed the best as we discussed it, the playground group isn’t used that much anyway (the idea is for people to be able to play around with the features), and we also have dev.karrot.world which could be used for that purpose… (although that has the downside that you need a separate account there).
The discussion also went in the direction of wondering if we should use karrot itself for organising ourselves more, it would make it easier for people who use karrot to participate (as they would already have an account), and also force all of us on the karrot team to actually use the software on a regular basis (so more likely to fix annoying little bugs), there was a concern though that it’s not designed as a tool for co-ordinating software projects so our needs and usage patterns might differ a lot from other groups on there… and another point though that we might want to support more open groups in the future, so make it easier for outsiders or casual contributors to participate in some way in karrot groups.
We didn’t come up with a clear idea what to do immediately though