Update readme, add travis, pep fixes, python3 compatibility

[brennv]

No description provided.

[bdewilde]

Hi @brennv , I'd love to see this PR get merged! Is there anything I can do to push the process forward?

[brennv]

I think we need to get LinkedIn's attention. I'm guessing this was an intern project that no longer has a clear maintainer.

[bdewilde]

Aha. Hey @RiteshMaheshwari, are you still developing/maintaining this project? If not, do you know who might be?

[bdewilde]

Well, I could just start tagging people in the linkedin github org... unless you have a better idea, @brennv ? :)

[brennv]

That sounds like a good plan. What do you think @jodzga ?

[jodzga]

Not it, but I'll try to find the right person :-)

[brennv]

Thanks @jodzga, I'm happy to simplify things by splitting out the issues further if need be. As is, this includes #11 and #13.

I'm also happy to help maintain the repo if new owners are needed.

[RiteshMaheshwari]

@brennv We haven't updated the codebase on luminol in a while as another internal project has replaced it. I am happy to merge simple pull requests though. Can you please split them into logical separate requests? Thanks!

[brennv]

Thanks @RiteshMaheshwari, much appreciated. I think adding travis and getting tests passing would good start. That way we can watch follow-on PRs pass or fail.

I think the logical order for the current proposed changes would be:

• add travis Add travis #11
• fix tests fix tests #20
• add test runner with linting and coverage
• pep8 fixes
• add Python3 support
• update readme
• bump pypi release

The first two are ready to go now. Depending on your thoughts I can start splitting out the rest.

[brennv]

Moving the conversation to #22. Closing this PR in favor of #11 #20 #21 #13 etc