I encourage all developers to participate in Julython. It's always been a great motivator for me to get back to old projects or explore new ideas.
It's also a great excuse to spend a bit of time cleaning up projects and getting them up-to-date because it rewards breadth of work more than depth.
Eldarion was the top team with 1059 points. I individually came 5th with 392 points. Don Stufft came 2nd, Patrick Altman 10th, Luke Hatcher 12th and Brian Rosner 22nd.
Eldarion was again the top team with a deliberate 1337 points. I came 2nd with 556 points. Patrick Altman came 3rd and Brian Rosner 10th.
Eldarion drops to 6th place with 907 points. I came 4th with 678 points. Patrick Altman came 23rd and Brian Rosner 358th (ouch!).
Eldarion comes 2nd with 879 points. I came 1st (yay!) with 460 points. Patrick Altman came 4th and Brian Rosner 19th.
Idea #1: Make sure all your repos have LICENSE files. http://choosealicense.com is a helpful site.
Idea #2: Check that all your repos have README files that are up-to-date.
Idea #3: Any lingering test cases that have been failing? Take some time to get all your existing tests passing.
Idea #4: Projects without tests at all? Pick one and write an automated test for it.
Idea #5: Got a project sitting locally you've never pushed (or equivalent) to a remote repo? Do it today (and don't forget to hook it up to Julython)!
Idea #6: Run something like flake8 (or equivalent) and clean up your source code.
Idea #7: hook up your tests (including things like flake8) to something like Travis CI and hook up to your source code host.
Idea #8: get a project working on Python 3.
Idea #9: get a project working on PyPy.
Idea #10: upgrade your requirements (pip list -o is great for finding out-of-date requirements).
Idea #11: presenting at a conference soon? Spend a little time each day working on the sample code.
Idea #12: improve the code coverage of the tests on one of your project.
Idea #13: if you use GitHub, take time to review some pull requests.
Idea #14: add non-ASCII strings to your unit tests via: Paul Hildebrandt
Idea #15: If you know another language (besides English) you can help I18N and L10N programs via: Paul Hildebrandt
Idea #16: put a project on PyPI
Idea #17: make sure PyPI has the latest release of all your projects
Idea #18: If you have a project on PyPI, upload a Wheel file. It’ll make things much faster for your users! via: Don Stufft
Idea #19: find an existing project you can contribute to (maybe implement one of the previously mentioned ideas)
Idea #20: review some existing project documentation and make sure it's up-to-date
Idea #21: write some new documentation