Hi,
This service is going to be used by management to get an idea of the number of patches going to each project over time, the number of patches submitted upstream by each team over time, the % of patches accepted upstream, the average time from submission to acceptance for each project, and other things like that.
For this to work well, and for your work to be accurately counted, you are going to be expected to keep it up to date as you submit patches upstream.
Now is the time to speak up if the interface doesn't have what you need to do this. Obviously it would be better if it took care of everything for you, but we don't think that everything can be automated. If you know better then we would obviously like to hear about that too.
Thanks,
James
On Thu, 07 Apr 2011 11:45:06 -0300, Guilherme Salgado guilherme.salgado@linaro.org wrote:
Hi folks,
I've been working on this app[1] (based on Patchwork) to track patches submitted/accepted upstream by Linaro engineers. It's still a work in progress and we're waiting for IS to deploy it but I wanted to show you what I have so far and ask for feedback, so I've deployed it on an ec2 instance:
http://ec2-184-73-78-92.compute-1.amazonaws.com/As you'll notice, that's the same front page you get on a regular Patchwork instance, which allows you to browse the patches of every project. You probably won't have to use that often, as everything you need to deal with should be on the page below:
http://ec2-184-73-78-92.compute-1.amazonaws.com/user/submitted/This one contains all patches you submitted that haven't received feedback yet. We want that to reflect reality to make sure our metrics are accurate, so we already have a script to mark the ones that are committed upstream and may use a similar approach to track rejected/superseded ones, but for now we'll need to manually mark the rejected/superseded ones.
The script mentioned above will scan a git repo for each project and update the state of patches that are found to be committed there, but it's not running yet as first I need to know the git (http works too) URL of every project listed there. if you know it for any of them, please do let me know.
Finally, the page below has some basic metrics to demo how we'll be using this data
http://ec2-184-73-78-92.compute-1.amazonaws.com/metrics/Some things to notice:
- This is a temporary deployment, so don't bother making changes (other
than those when playing around) as those will probably be lost
- Login via OpenID using the Launchpad login service, so there's no need
to register
- Not all of your patches may be shown under /user/submitted. if that's
the case, make sure all your email addresses are registered in Launchpad as we're sucking that data from there periodically and the next time we do so we'll merge all your email addresses under a single user
- Some numbers in /metrics are skewed because of patches that have
multiple versions; you'll be asked to flag superseded versions so that they're not included in the counts, and you're encouraged to do so for some of them to see how it works, but given that changes will be lost, don't bother doing it for more than a few
- The other-unknown project is where we put patches for which we can't
guess a project.
- in some cases this is because the patches are sent only to patches@linaro.org so they need to be manually moved to the appropriate project (there's a form at the bottom of every patch list which allow you to do that).
- in other cases it's because we're missing a project in patchwork. if that's the case we can register that project and there's a script which runs periodically and will move these patches to the new project
[1] https://wiki.linaro.org/Platform/Infrastructure/Specs/PatchTracking
-- Guilherme Salgado https://launchpad.net/~salgado
Non-text part: application/pgp-signature
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev