Coding style and organization

[vixsomnis]

Style isn't consistent in the source. It's not a major issue, but I'd like some written rules for hacking on the codebase.

It doesn't matter what the rules are, just that there are some. I think clarity and organization are good traits for security and crypto.

(I recommend an 80-character line wrap and 4-space indentation, for the sake of standards.)

[L-Henke]

80 chars is 1980 style and why annoying spaces instead of tabs?

[L-Henke]

But of course we need to define a style guide, or maybe even provide a template for Android Studio.

[vixsomnis]

Like I said, I can do whatever. I prefer 80 since it forces me to to write clearer code, but 100 or 120 is fine too. Don't really have a preference for tabs/spaces.

I don't use android studio, so we should probably have a CONTRIBUTING file as well.

[L-Henke]

I would vote for 100 or 120 chars and tabs instead of spaces. But there are a lot more things that can be defined. e.g. the order of android lifecycle methods like onCreate and similar methods which should be on top of a file, ...
Maybe we should just use this issue to collect proposals and then create a contributing file from it.

[vixsomnis]

100-char and tabs sounds good. I think we should default to the AOSP guidelines when we don't have anything specified.