Hello, World
In response to my last post, I’ve added a new feature — report-issue.
This will let any Launchpad user file a ( private ) bug against a project just for LoCo issues. This will also automatically subscribe the LoCo council, and let us know that it’s a problem.
This will be faster then RT, or IRC. This will also log stuff and let us update the issue as we do stuff ( rather then not hearing anything back for a while ).
Here’s what a report-issue session looks like:
tag@loki:~$ lca report-issue
N: Connecting to Launchpad...
N: Identified as Paul Tagliamonte!
N:
N: OK. I'm going to fetch your teams now, and figure out
N: what LoCo team(s) you're on
N:
N: 0) Ubuntu Iowa LoCo Team ( ubuntu-us-ia )
N: 1) Ubuntu LoCo Council ( ubuntu-lococouncil )
N: 2) Ubuntu North East Ohio ( ubuntu-us-ohio-ne )
N: 3) Ubuntu Ohio LoCo Team ( ubuntu-us-ohio )
N: 4) Ubuntu United States, Massachusetts ( ubuntu-us-ma )
N:
N: Which team would you like to file against?
N:
3
N: Let's send a report about team `ubuntu-us-ohio'
N:
N: I'm going to need some info about what this is about
N: Just write up what the problem is, treat this like
N: an email. To end the comment section put a . on it's own
N: line, please.
N:
The Ubuntu Ohio team is too awesome.
It's turning out to be a big issue, the members are too cool, and the contact is one
rad dude. You should look into making them less awesome, or we all look bad.
Much love,
Paul
.
N: Righto! So, I'm going to file this bug for you.
N: Sending now!
N:
N:
N: Alrighty! Issue filed. The LoCo Council has been
N: notified of the report. Feel free to email or talk
N: with anyone on the LoCo Council. Be sure to mention
N: that you have filed LP Bug #671256
N:
N: Thanks so much!
N:
I’ve marked this bug public, so you can see what the report looks like. Here’s the link to the bug: Bug #671256.
Patches welcome! Rock on!