Alyssa Coghlan

Current status at the PyCon AU sprints: I'm taking the flask-oidc dependency and the related README notes from Fedora Hubs and adapting them for Anitya.

@jeremycline The main difference between #42 and this proposal is that #42 proposed defining the API in terms of the internal Anitya project IDs (so it could be used for...

So given that qualifier, +1 for closing #42 in favour of this one - the internal Anitya IDs are much harder to work with from a client perspective than the...

I should note that the patch for this is currently living at https://github.com/bkabrda/anitya-docker/tree/master/patches We haven't pushed it back upstream yet because it would be a really bad idea to merge...

https://github.com/fedora-infra/anitya/issues/329#issuecomment-240665177 on #329 has links to my working repo where the API patches applied to the docker image originated.

+1 Having multiple boards sharing a common issue pool with different filters applied makes it straightforward to have different teams focusing on different aspects of a service, while still being...

I'm more familiar with the way JIRA Agile works than I am with Taiga (my usage of the latter is only very basic to date), but the way the former...

This was roughly the topic of my PyGotham and PyCon Poland keynotes earlier this year. - [Source Markdown](https://bitbucket.org/ncoghlan/misc/src/default/talks/2015-08-pygotham/talk.md) for slides & presenter's notes - [Additional notes](https://bitbucket.org/ncoghlan/misc/src/default/talks/2015-08-pygotham/miscellaneous-notes.txt) (Since giving the PyCon...

I also wrote an article for Red Hat's community blog earlier this year on _why_ an organisation might fund their employees spending time working in the open: http://community.redhat.com/blog/2015/02/the-quid-pro-quo-of-open-infrastructure/

Tidelift are pursuing an idea along these lines by offering a "business model as a service" platform: https://tidelift.com/about/lifter