On Fri, 2011-04-08 at 16:25 +0200, Alexander Sack wrote:
On Fri, Apr 8, 2011 at 4:14 PM, James Westby james.westby@linaro.org wrote:
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.
Wonder, does this test instance really need to use authentication of launchpad staging? Just noticed that, because it neither logged me in automatically nor where my credentials properly filled out in my browser.
In order to have patches associated with the logged in user, we need the user's email address, which is only sent by the Launchpad Login Service to certain authorized consumer sites. I didn't want to add that ec2 host as an authorized site to login.lp.net so I chose to use login.staging.lp.net instead.