All,
Serge and I met this morning and I thought I'd pass along the minutes for those that are interested and interested in hacking a little python, more people are welcome.
Background: Alan Bennett earlier in the year had written a tool in python to take advantage of the Jira python interface to auto generate a portion of the monthly engineering report.
Tom Gall got involved to use for LMG efforts, and inherited the tool from Alan when he left. The codebase has been used as inspiration to automate a number of useful Jira related activities. Since google docs, Jira, plotting/graphics tools and other things that have good and powerful python interfaces, there's lots of opportunity to do useful things.
Now that we're over to projects.linaro.org that's motivating tool development involving the new system and new needs.
Serge has driven ahead with a more full function version that takes into account Core Engineering and how reporting occurs there.
Discussed: -------------- Current status of the tool Tom is maintaining Current status and design of Serge's codebase Needs going forward, and observation that lead project oriented reporting instead of reporting by team might be a future reporting need.
Actions: - Tom to examine and pull in Serge's advanced functionality - Serge will look at the older code base - Tom examining a tool called "did" that compiles developer status from git - better output through output directly into google docs instead of HTML
Tom / Serge,
Good stuff. Please keep me informed.
Mark
On Wed, Sep 30, 2015 at 9:44 AM, Tom Gall tom.gall@linaro.org wrote:
All,
Serge and I met this morning and I thought I'd pass along the minutes for those that are interested and interested in hacking a little python, more people are welcome.
Background: Alan Bennett earlier in the year had written a tool in python to take advantage of the Jira python interface to auto generate a portion of the monthly engineering report.
Tom Gall got involved to use for LMG efforts, and inherited the tool from Alan when he left. The codebase has been used as inspiration to automate a number of useful Jira related activities. Since google docs, Jira, plotting/graphics tools and other things that have good and powerful python interfaces, there's lots of opportunity to do useful things.
Now that we're over to projects.linaro.org that's motivating tool development involving the new system and new needs.
Serge has driven ahead with a more full function version that takes into account Core Engineering and how reporting occurs there.
Discussed:
Current status of the tool Tom is maintaining Current status and design of Serge's codebase Needs going forward, and observation that lead project oriented reporting instead of reporting by team might be a future reporting need.
Actions:
- Tom to examine and pull in Serge's advanced functionality
- Serge will look at the older code base
- Tom examining a tool called "did" that compiles developer status from git
- better output through output directly into google docs instead of HTML
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Director, Linaro Mobile Group Tech Lead, Graphics, GPGPU Linaro.org │ Open source software for ARM SoCs irc: tgall_foo | skype : tom_gall _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Tom/Serge
Thanks for the great initiative! I am onboard as we agreed before Connect! I will sync with you for updates real-time on IRC.
Cheers, Amro
*Amro Hassaan* Tools Analyst amro.hassaan@linaro.org Phone: 613-454-1462 Cell : 613-413-2993 http://www.linaro.org
On 30 September 2015 at 12:44, Tom Gall tom.gall@linaro.org wrote:
All,
Serge and I met this morning and I thought I'd pass along the minutes for those that are interested and interested in hacking a little python, more people are welcome.
Background: Alan Bennett earlier in the year had written a tool in python to take advantage of the Jira python interface to auto generate a portion of the monthly engineering report.
Tom Gall got involved to use for LMG efforts, and inherited the tool from Alan when he left. The codebase has been used as inspiration to automate a number of useful Jira related activities. Since google docs, Jira, plotting/graphics tools and other things that have good and powerful python interfaces, there's lots of opportunity to do useful things.
Now that we're over to projects.linaro.org that's motivating tool development involving the new system and new needs.
Serge has driven ahead with a more full function version that takes into account Core Engineering and how reporting occurs there.
Discussed:
Current status of the tool Tom is maintaining Current status and design of Serge's codebase Needs going forward, and observation that lead project oriented reporting instead of reporting by team might be a future reporting need.
Actions:
- Tom to examine and pull in Serge's advanced functionality
- Serge will look at the older code base
- Tom examining a tool called "did" that compiles developer status from git
- better output through output directly into google docs instead of HTML
-- Regards, Tom
"Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Director, Linaro Mobile Group Tech Lead, Graphics, GPGPU Linaro.org │ Open source software for ARM SoCs irc: tgall_foo | skype : tom_gall _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
-
Amro Hassaan -
Mark Orvek -
Tom Gall