I remember last quarter we had a sort of nebulously defined goal of making Sheriff-o-Matic more self-serve. I think that still might be a good thing to aim for though being able to completely expose everything people would need in configuration is unlikely. 

But right now there are a lot of little things being hard coded into special cases. Like the help links that show up for webkit tests and such. And there are a lot of things that would be nice to make configurable. Like the message that appears at the top of the tree telling sheriffs to start at the top and try to clear all the alerts. 

And there would be a lot of little other things in the future that would be nice to expose in configuration. For example, it looks like many clients have some sort of bug queue but they seem to handle them in completely different ways. More configuration will make our lives easier to adapt to changing needs and allow us to better reuse code between different use cases. 

The current admin panel has some configuration but it should be reworked to allow for more configuration. We might want to create separate pages for each tree so that there can be a lot more configuration options. 

Or, perhaps it might make sense to change the configuration to be JSON-based instead? Right now there is a decent amount of configuration that has to be synced between production and staging. Using JSON files that are part of the repo could help add some more stability here, especially as the configuration gets more complex. It'd also be easier to represent complex configuration modes this way (not having to flatten all configuration into something easy to represent in user input). Having to edit code to change tree settings is a disadvantage here though. 

Or something else. Just random thoughts here. 
 

Right now there are a lot of little things being hard coded into special cases. Like the help links that show up for webkit tests and such. And there are a lot of things that would be nice to make configurable. Like the message that appears at the top of the tree telling sheriffs to start at the top and try to clear all the alerts. 

And there would be a lot of little other things in the future that would be nice to expose in configuration. For example, it looks like many clients have some sort of bug queue but they seem to handle them in completely different ways. More configuration will make our lives easier to adapt to changing needs and allow us to better reuse code between different use cases. 

The current admin panel has some configuration but it should be reworked to allow for more configuration. We might want to create separate pages for each tree so that there can be a lot more configuration options. 

Or, perhaps it might make sense to change the configuration to be JSON-based instead? Right now there is a decent amount of configuration that has to be synced between production and staging. Using JSON files that are part of the repo could help add some more stability here, especially as the configuration gets more complex. It'd also be easier to represent complex configuration modes this way (not having to flatten all configuration into something easy to represent in user input). Having to edit code to change tree settings is a disadvantage here though. 

Or something else. Just random thoughts here.