Style and Contributing questions

[sbehrens]

I'm currently investigating the post-breach/simulation space and was considering building my own framework for this. Dumpster Fire looks like it would solve some of my use cases, specifically the modules you have provided.

Menu driven support wont work for our end goal, which is more autonomous game days launched via our CI pipelines. We'd like to end up in a place where we'd run simulations at random with various configurations, driven by config files/json and not user controlled input.

I'm considering writing that portion based on Dumpster Fire but I had some questions around the style before beginning. It seems that Dumpster Fire uses a combination of Java and Python style. Some of the fire modules have class names in lower case and method names in Java case which is the opposite of Pep8. some method definitions call self like this:

def foo( self ):

or

def Foo(self):

Would you have any problems if I started normalizing/linting the code as I'm contributing to be in line with Pep8 style format? In addition, would a config/json test initialization support be useful for contributing?

-Scott