Roadmap - things to work on

[timeyyy]

This is a road map for anyone who wants to help out

Issues

• lack of documentation on known issues
• esky fails with py2exe
• getting root on windows
• everything in issues/pull requests
• pypi needs to be updated
• pep8 codebase
• update registry or other system meta data after a successful update

New Features

• travis-ci on linux
• ci on windows
• ci on mac
• get python 3.5 tests passing
• python3 compatible code
• support pyinstaller
• use tuf library under the hood for a nice boost in security
• support code signing

Refactors

• Use requests instead of urllib

[timeyyy]

@rfk thanks for the tips always appreciated. I've come across the tuf project recently, http://theupdateframework.com/, its a framework for developing secure update systems, i think pypi and some other people are using it. Would you be able to take a butchers at it and estimate how long it might take (if at all possible) to integrate into esky? I'm a fairly new programmer and would appreciate your input.

[rfk]

It looks like it could be a good fit, at first glance the level of abstraction seems to match what we do in esky. It seems the integration would look something like a TUFVersionFinder class, implementing the interface defined by esky.finder.VersionFiner, and using the functions exported by the tuf module in [1]. Prototyping this seems like a relatively small undertaking - if we're lucky, the two could fit together quite nicely.

If you're keen to dive in and have a go at this, I suggest spinning it off into a separate issue and we can chat more about the details.

[1] https://github.com/theupdateframework/tuf/blob/develop/tuf/client/README.md

[cbenhagen]

Hi there,

i would recommend to do the pep8 part as fast as possible as this is going to completely mess up the history. As in blame will show almost every line changed by that commit. The faster it is done the faster blame will be useful again.

You might consider using yapf to do most of the hard work. Some manual work will still be needed but in most cases it will do a good job.

[rfk]

Thanks for reaching out. Unfortunately this project is no longer actively maintained, so I'm going to move it into archive mode:

https://rfk.id.au/blog/entry/archiving-open-source-projects/