Standup is a system for capturing standup-style posts from individuals making it easier to see what's going on for teams and projects. It has an associated IRC bot standups for posting messages from IRC.
This post talks a bit about the Standup v2 rewrite. Why and how we did it and what's next.
Standup is a system for capturing standup-style posts from individuals making it easier to see what's going on for teams and projects. It has an associated IRC bot standups for posting messages from IRC.
Paul and I did a ground-up rewrite of the Standup web-app to transition from Persona to GitHub auth, release us from the shackles of the old architecture and usher in a new era for Standup and its users.
We're done with the most minimal of minimal viable products. It's missing some features that the current Standup has mostly around team management, but otherwise it's the same-ish down to the lavish shade of purple in the header that Rehan graced the site with so long ago.
If you're a Standup user, we need your help testing Standup v2 on the -stage environment before Thursday, September 22nd, 2016!
We've thrown together a GitHub issue to (ab)use as a forum for test results and working out what needs to get fixed before we push Standup v2 to production. It's got instructions that should cover everything you need to know.
Why you would want to help:
You get to see Standup v2 before it rolls out and point out anything that's missing that affects you.
You get a chance to discover parts of Standup you may not have known about previously.
This is a chance for you to lend a hand on this community project that helps you which we're all working on in our free time.
Once we get Standup v2 up, there are a bunch of things we can do with Standup that will make it more useful. Freddy is itching to fix IRC-related issues and wants https support [1]. I want to implement user API tokens, a cli and search. Paul want's to have better weekly team reports and project pages.
There are others listed in the issue tracker and some that we never wrote down.
We need to get over the Standup v2 hurdle first.
Why you wouldn't want to help:
You're on PTO.
Stop reading--enjoy that PTO!
It's the end of the quarter and you're swamped.
Sounds like you're short on time. Spare a minute and do something in the Short on time, but want to help anyhow? section.
You're looking to stop using Standup.
I'd love to know what you're planning to switch to. If we can meet peoples' needs with some other service, that's more free time for me and Paul.
Some fourth thing I lack the imagination to think of.
If you have some other blocker to helping, toss me an email.
Hooray for the impending Standup v2!
| [1] | This is in progress--we're just waiting for a cert. |
pyvideo.org is an index of Python-related conference and user-group videos on the Internet. Saw a session you liked and want to share it? It's likely you can find it, watch it, and share it with pyvideo.org.
This is my last update. pyvideo.org is now in new and better hands and will continue going forward.
Over the weekend, I wanted to implement something that acted as both a class and function decorator, but could also be used as a context manager. I needed this flexibility for overriding configuration values making it easier to write tests. I wanted to use it in the following ways:
as a function decorator:
@config_override(DEBUG='False') def test_something(): ...
as a class decorator that would decorate all methods that start with test_:
@config_override(DEBUG='False') class TestSomething: def test_something(self): ...
as a context manager that allowed for multiple layer of overriding:
def test_something(): with config_override(DEBUG='False'): with config_override(SOMETHING_ELSE='ou812'): ...
This kind of need comes up periodically, but infrequently enough that I forget how I wrote it the last time around.
This post walks through how I structured it.
pyvideo-data is a collection of Python-related conference video data in JSON format.
This is an update of what's going on with pyvideo.org and pyvideo-data.
pyvideo.org is an index of Python-related conference and user-group videos on the Internet. Saw a session you liked and want to share it? It's likely you can find it, watch it, and share it with pyvideo.org.
This is the latest status report for all things happening on the site.
It's also an announcement about the end.
Note
Update: See the March 16th blog post covering the current status of pyvideo.org and pyvideo-data.
My 2015 retrospective. Kind of like 2014, but less terrible and more snow.
Things to know:
This is the quarter in review for Mozilla Input!
Things to know:
This is the quarter in review for Mozilla Input!
Dennis is a Python command line utility (and library) for working with localization. It includes:
It's been 10 months since the last release. In that time, I:
I thought I was close to 1.0, but now I'm less sure. I want to unify the .po and .pot linters and generalize them so that we can handle other l10n file formats. I also want to implement a proper plugin system so that it's easier to add new rules and it'd allow other people to create separate Python packages that implement rules, tokenizers and translaters. Plus I want to continue fleshing out the tests.
At the (glacial) pace I'm going at, that'll take a year or so.
If you're interested in dennis development, helping out or have things you wish it did, please let me know. Otherwise I'll just keep on keepin on at the current pace.
For more specifics on this release, see here: https://dennis.readthedocs.org/en/v0.7/changelog.html#version-0-7-0-october-2nd-2015
Documentation and quickstart here: https://dennis.readthedocs.org/en/v0.7/
Source code and issue tracker here: https://github.com/willkg/dennis
Source code and issue tracker for Denise (Dennis-as-a-service): https://github.com/willkg/denise
47 out of 80 Silicon Valley companies say their last round of funding depended solely on having dennis in their development pipeline and translating their business plan into Dubstep.