https://bluesock.org/~willkg/blog/enContents © 2025 <a href="mailto:willkg@bluesock.org">Will Kahn-Greene</a> CC BY-SA 3.0Tue, 28 Oct 2025 18:03:12 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://bluesock.org/~willkg/blog/dev/phil_1.0.htmlWill Kahn-Greene<p><a class="reference external" href="http://mediagoblin.org">Mediagoblin</a> has monthly project meetings. One of the things I wanted to automate was meeting reminders that gets sent x days in advance, contain the link to the Meetings page in the wiki, and specify the date and time of the next meeting. I figure if we automate it, it's one less thing we have to think about---it just happens.</p> <p>To do this, I decided to write <a class="reference external" href="http://github.com/willkg/phil">phil</a>. For the most part, it's sort of a throw-away project, but it was so small that I decided to go through a complete project development cycle with it and make sure it had all the bits a mature Python project should have: proper packaging, license, configuration, tests, project infrastructure, ...</p> <p>I think it took about 10 hours over the course of 2 weeks. I was learning the icalendar library and python-dateutil and also figuring out exactly what I wanted it to do as I went along. For a small project like this, that's fine. For a larger project, I'd prefer to spend more time researching and designing ahead of time.</p> <p>It was nice to "take a vacation" and put all the other projects I normally work on on hold to throw something together from scratch.</p> <ul class="simple"> <li><p>Github page: <a class="reference external" href="https://github.com/willkg/phil">https://github.com/willkg/phil</a></p></li> <li><p>PyPI page: <a class="reference external" href="http://pypi.python.org/pypi/phil">http://pypi.python.org/pypi/phil</a></p></li> </ul>devmediagoblinphilpythonhttps://bluesock.org/~willkg/blog/dev/phil_1.0.htmlSat, 03 Dec 2011 22:29:38 GMT