Hi everyone,
One of the topics we discussed in last week's meeting was to adopt a set of
coding standards for our project. This will greatly increase the
consistency and readability of our code and hopefully prevent some issues
and bugs. We agreed on the standards defined in PEP 8 by the Python
developers. Everyone should read the page linked below and try to follow
the standards as closely as they can. Many IDEs and text editors have
plugins that will notify you if you are breaking some of the standards (but
not all of them), so I would encourage you to use one if possible. You may
also have to configure your editor to match some of these standards (for
example 4 spaces instead of tabs).
http://legacy.python.org/dev/peps/pep-0008/
I will be submitting a pull request to bring the existing code base up to
standards soon and all future pull requests should meet these standards too.
Thanks
Ben Zeghers (umzegher)
Hey guys,
1. A note that if you ever require to build the python package manually,
(I'm still working on the debian package), the command from the main
directory of the source code is:
python setup.py bdist
2. I have created a Mega Cron Team email address for publishing in the
setup.py (pypi index). It is:
megacronteam(a)gmail.com
Let me know personally if you would like the password, but I think
you'll find it is identical to a popular, delicious, refreshing drink
(made with natural fruit) at the coding sprint.
3. What we determined at Friday's meeting is as follows:
1) Combine scheduler and worker
2) Create a config file for the clusters of workers (getting workers
to run on distributed machines via shared filesystem)
3) Unit test API
4) Handle packaging issues
5) Follow PIP style guide
6) Build documentation
4. A reminder that our next meeting is on Tuesday February 4th, at
9:00pm EST on the IRC megacron channel.
Cheers,
John