Hi everyone, We have a few housekeeping tasks that are basically a shared effort and never completely ended, like improving our test code coverage, docstrings or pylint scores.
Generic blueprints are very bad at tracking that kind of effort, since those are not assigned to specific people, or targeted against a specific release. However, not having any tracking generally result in those tasks being ignored, while they make really nice goals for newcomers in the project. So I propose to keep them as blueprints, not targeting them to a specific release, and assign them to the project teams (~nova, ~swift, etc). That way we can find them by looking at specs assigned to generic teams, like for nova: https://blueprints.launchpad.net/~nova/+specs?role=assignee I exposed that development task in the http://wiki.openstack.org/HowToContribute doc so that newcomers can find them. If you have any housekeeping task that should be on that list, feel free to ping me, or directly file a blueprint / assign the project team to them. Should this one be part of the list, for example ? https://blueprints.launchpad.net/nova/+spec/unittest-coverage We should review the progress on those at each design summit to see if that's successful enough, or if we need to change how we track them. Cheers, and happy new year ;) -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
