[OpenStack-Infra] [StoryBoard] StoryBoard Bug Squash 22nd-23rd June
Hi everyone! For one week only*, the StoryBoard bug squash is coming to an OpenStack community near you! That's right; from 11:00 UTC 22nd June, to 11:00 UTC 23rd June THIS week, the StoryBoard team will be making a critically-acclaimed appearance in #openstack-sprint. We'll be setting time aside to help new contributors and to smoosh as many pesky little bugs as possible. So come one, come all, and let's squash some bugs! As always, you can also catch us in #storyboard. You can also help with the effort by tagging smaller tasks as low-hanging-fruit in storyboard.openstack.org. We have a worklist-in-progress listing all such StoryBoard stories here: https://storyboard.openstack.org/#!/worklist/76 Feel free to ask any questions in #storyboard, and we hope to see you there! Best Wishes, Zara *every week, really, we just don't use #openstack-sprint most weeks. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [StoryBoard] Thanks for the bugsquash, plus a new-things roundup
Hi all, A big thank you to everyone who came and helped out in the spectacular* StoryBoard bug squash! We look forward to the next. :) Here are some hilights from the last couple of weeks: * BEAUTIFUL NEW COMMENTS AND EVENTS TIMELINE It's so beautiful, it requires all-caps. SotK has transformed the barebones events timeline into an elegant swan. Well, that's a weird mixed metaphor, but it *is* lovely! Furthermore, this magnificent gentleman has removed pagination so that comments are no longer lost on the second page of the results, and has made it possible to link comments directly. Extra thanks to ttx for fixing some of the css during the bugsquash! :) Here's an example: https://storyboard.openstack.org/#!/story/2000464#comment-7029 There is a WIP patch in review for editing one's own comments, for anyone interested in trying it out and giving feedback: https://review.openstack.org/#/c/333418/ * Email threading The kindly pedroalvarez has worked some magic on the emails StoryBoard sends, so that they are threaded according to story. It should now be easier to see what an email refers to at a glance. * API Docs example commands anteaya has made it easier for people to interact with StoryBoard via the API with these examples. This should be good news for anyone who wants to use scripts with StoryBoard. You can see them here: http://docs.openstack.org/infra/storyboard/webapi/v1.html#stories * Gerrit integration for storyboard-dev Review-dev can now post comments on storyboard-dev (our test instance)! Thanks so much, zaro! You can see an example patch here: https://review-dev.openstack.org/#/c/5454/ * Tags search upgraded Tags search now suggests existing tags! This should making searching-by-tag much easier. I hope to build on this to change task-statuses in the next couple of weeks. It's been a pretty busy time... which is why I'm over a week late with this email \o/. Anyway, yes, thanks again to everyone who helped out. If you'd like to get involved in the project, we're always available in #storyboard on freenode; the project is a mix of python and angularjs. We have a worklist of stories that contain easy tasks here: https://storyboard.openstack.org/#!/worklist/76 , so you can see if anything takes your interest, then it's best to ask in the channel for the specifics. :) Hope to see you there! If I've missed anything, please let me know. Best Wishes, Zara *I haven't personally written any interesting patches of late, so I am allowed to call it 'spectacular'. :) ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [openstack-dev][StoryBoard] Gerrit-StoryBoard integration is live, and other updates
Hi, all! A few exciting StoryBoard updates incoming. 1. StoryBoard is now integrated with Gerrit (thanks, zaro)! --- This is the big one! And I am as happy as a clam.:) To use this incredible new power, in StoryBoard, find the task id to the left of the task you're about to send a patch for. Then put: Task: $task_id into the commit message. When the patch is sent, this will update the status of the relevant task in StoryBoard, and post a comment linking to the gerrit change. Stories also have unique ids, found to the left of each story in the list of stories, so if you include: Story: $story_id you can easily browse from gerrit to the related StoryBoard story. There is an example of the syntax here: https://review.openstack.org/#/c/355079/ If you'd like to try it out yourself but don't have any pressing patches to send, you can make a story over at our test instance, https://storyboard-dev.openstack.org , and then send a nonsense patch to a project in review-dev (https://review-dev.openstack.org/), citing the relevant task and/or story. zaro has done the vast majority of the work on this, so thank you, zaro (again)!!! And thanks to everyone in the infra team who helped with reviews to config and switching things on. :) 2. Worklists and boards are more discoverable - Now logged-out users can easily find the lists of worklists and boards, and users can filter them by title, or by tasks or stories they contain. You'll find them on the main sidebar, just below the 'dashboard' option. A worklist lets you order a custom todo list (eg: to convey priority), or provide a handy filter of tasks/stories (eg: 'show all 'todo' tasks in story foo). A board allows you to create several lists side-by-side, so that you can track the movement of tasks. This means you can, say, create a board with 'todo', 'review', and 'merged' lanes, filtered by project, and the contents of these will update as people send patches to gerrit. Here's an example: https://storyboard.openstack.org/#!/board/14 3. More usable developer docs - Matthew Bodkin has updated our developer docs so that they can be used to launch a StoryBoard instance. They should be functional now (we aim for the stars). Thanks, Matthew! He's also helped with multiple misc ui fixes recently, so thanks again. On the horizon... - There is a TC Ocata goal to remove incubated oslo code, which affects two StoryBoard projects (the api and the python client). I've made a story for it over here: https://storyboard.openstack.org/#!/story/2000707 ; if other affected projects are using StoryBoard, it makes sense to list tasks there so they're easier to find. This is exactly the sort of cross-project work that StoryBoard is designed for, so let's give it a workout! I could do with some guidance or examples on removing and replacing the incubated oslo code (especially for the python client, which uses the old apiclient module). If people are interested in running scripts against StoryBoard and doing more specific browses and filters on results, our python client is the answer, so I'm interested in a) tidying it up and b)finding out people's workflow and how they would expect to interact with the python client from the commandline. That's all for now (sorry this was so long!). The StoryBoard meeting is at 15:00 UTC today (and every Wednesday) in #openstack-meeting. We are also always available in #storyboard, for chatter (and occasionally development). Happy task-tracking! :) Best Wishes, Zara ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [StoryBoard] StoryBoard can now represent complex priority
Hi, all,
We're excited to announce that it's now possible to represent complex
priority in StoryBoard!
What does this mean?
It's possible for different people to say 'this is a priority for us',
so that a task can have different priorities, tailored to different
audiences.
So, why is this useful?
Previously, StoryBoard allowed users to assign one priority to each task
('high', 'medium' or 'low'). The implementation meant that anyone could
change a task's priority, and this would be seen by everyone viewing the
task. There was no way to say 'you can only change this priority if you
have discussed this on irc and it has been agreed among the project
team', etc. This meant that people with no context could alter global
priority of tasks. Also, two different groups might prioritize tasks
differently, and this could result in long prioritization sessions,
where the real question was 'whose priorities matter most?' (and often
the answer was 'it depends on who the audience is', so these arguments
would result in a stalemate)
So, StoryBoard now has a way to say 'this task matters to *me*'. We use
worklists to express priority: if you manually add tasks to a worklist,
you can drag and drop them in order of priority. This has the side
effect that you can see how prioritizing one task affects the priority
of other tasks; you can only have one item at the top, and putting
anything high on the list will push other things down. It is now
possible for others to subscribe to the worklists of those individuals
or teams whose priorities they care about; then, whenever they browse to
a story, they will see if any of the tasks are on those lists, and what
position the tasks are on the list.
Lists have permissions, so it is possible to set up a project team list
on which items can only be moved by contributors selected by core
reviewers, etc. This stops everyone changing the priority of tasks
without discussion.
This is very new, and we're excited to see how people use it. We've lost
some ease in *assigning* priority in favour of finer grained
*representation* of priority. In the past, StoryBoard did show lots of
different people's priorities, it just didn't offer any way of tracking
whose priorities were whose. So this makes things more open and
explicit. We hope to tailor the implementation based on user feedback,
and these are the first steps! :)
Example workflow for a project team:
* Make a worklist, subscribe to it and add tasks you care about from
existing stories, select users who are allowed to move things on the
worklist
* Drag and drop tasks in order of priority
* Create a story with a task you care about (or browse to an existing
story); click the arrow next to the task, then the 'add to worklist'
button, and add to the team priorities worklist
* On a story, tasks that feature in subscribed worklists will appear on
the top-right, along with their position in the worklist
* Link the worklist on irc or on the mailing list, etc, wherever it's
most visible, and invite people to subscribe!
It is possible to subscribe to email notifications for worklists, so
that you can be kept up to date on changes in priority. These
notifications can be toggled in the profile preferences (person icon on
navbar, near the bottom) and are separate from the main email
notifications, to avoid things getting spammy. :)
We have a summit session on Thursday afternoon; feel free to come along
if you're interested! The details are here:
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16985/infrastructure-status-update-and-plans-for-task-tracking
and we have a (very drafty) etherpad at:
https://etherpad.openstack.org/p/ocata-infra-community-task-tracking )
Have fun, and happy task-tracking!
Best Wishes,
Zara
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Boston 2017 Summit dinner
On 28/04/17 01:47, Paul Belanger wrote: Greetings! Its that time where we all try to figure out when and where to meet up for some dinner and drinks in Boston. While I haven't figure out a place to eat (suggestion most welcome), maybe we can decide which night to go out. Hi! Thanks for organizing this. :) Please take a moment to reply, and which day may be better for you. Sunday: Yes Monday: Yes Tuesday: Yes (though also prefer not to clash with StackCity) Wednesday: No Thursday: Yes ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Boston 2017 Summit dinner
On 09/05/17 15:16, Paul Belanger wrote: Thanks to everybody who turned out last night. Apologies we had to split off the some people from the main table. Hopefully everybody still had an awesome time! -PB Thank you for organizing it! :) ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] StoryBoard Midcycle Meetup
Hi, all, The StoryBoard[1] team is excited[2] to announce that we're hosting a meetup on the 17th of February, 2016, in Manchester, UK[3]! It's free to attend, and there will be cake. Wiki Page: https://wiki.openstack.org/wiki/StoryBoard/Midcycle_Meetup Etherpad: https://etherpad.openstack.org/p/StoryBoard_Mitaka_Midcycle This is just after the ops meetup [4], in the same city, so it should be convenient for anyone going there. Alternatively, why not come out on a spontaneous trip to Manchester? Actually, don't answer that. Anyway, please add yourself to the etherpad if interested, and/or specify a cake! :) And thanks to Codethink for sponsoring us. We're happy to answer any questions in this thread or in #storyboard on freenode. Best Wishes, Zara [1] https://storyboard.openstack.org/#!/page/about [2] We're even more excited to have finally gotten round to writing this email [3] Exact location: https://www.google.co.uk/maps/place/Ducie+House,+37+Ducie+St,+Manchester+M1+2JW/@53.4805451,-2.2308359,17z/data=!3m1!4b1!4m2!3m1!1s0x487bb1bc54a57815:0x5a08e799278b60b [4] https://etherpad.openstack.org/p/MAN-ops-meetup ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] right way to report odd infrastructure issues?
Hi! On 12/02/16 11:41, Sean Dague wrote: I hit another oddball infrastructure issue this morning where setup workspace took > 1 hr (giving 34 minutes for tempest job which then failed with a timeout) - http://logs.openstack.org/27/279227/2/check/gate-tempest-dsvm-full-ceph/35c90b3/console.html The current model is mostly to take these to IRC, but things get lost there, especially as I tend to find many of these during light coverage windows there. What bug / issue tracker should I be using so that we can build up profiles of things like this? I know story board isn't a thing atm. Infra people do use it for tracking bugs and tasks, so I think your information may be out of date (there are plans to move away, but in the meantime, StoryBoard is much more usable these days). If you haven't used StoryBoard in some months, it's worth trying again. Obviously I am biased on this. :) The openstack-gate project in launchpad I don't think gets looked at (we mostly use it as a dumping ground for ER signatures that don't have a clear home). Would love to have a better model for writing down what we see that can get looked at when folks are around to poke at the issues. -Sean If this refers to the devstack-gate project, people track at least soome issues using StoryBoard. https://storyboard.openstack.org/#!/project/712 . Best Wishes, Zara ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [StoryBoard] A few new things StoryBoard does these days
Hi, all, We've been working on StoryBoard (https://storyboard.openstack.org/#!/dashboard/stories) for a while, but haven't really updated the list; here's a roundup. New things in storyboard over the last few months: Notification: * storyboard.openstack.org sends email notifications! Finally! If you are subscribed to a project, project-group, or story, and it changes, you'll get an email. At the moment these are pretty basic, and off by default. To turn them on, log in (in the header), click 'profile' toward the bottom of the sidebar, and you should see a checkbox on the bottom left below 'preferences'. This is just an on-off switch; you will receive emails for all changes to a subscribed resource, or none. We plan to refine it further; feedback welcome for what changes people would like to see most! Thanks so much to everyone for helping to get this show on the road. :) Dashboard: * column for 'stories assigned to me' Useful as a shortcut to see your planned work * column for 'stories created by me' Useful as a shortcut to see issue reports you've filed. * subscriptions Now you can see the list of things you're subscribed to, all in one place. These are accessible from the star-shaped button on the dashboard submenu on the sidebar (click 'dashboard' and the submenu should fold out) Boards and Automatic Worklists: *Manual worklists These allow you to order tasks, by dragging cards up and down in the worklist. They allow for more finely grained personal priorities than the global 'priority' button. To make one, click 'create new...' in the header. Once created, you can edit to make it public or private, and choose who is able to move/delete items (or the worklist itself) by setting owners and users. Best to play around. To see your current worklists, click 'dashboard' in the sidebar, and the second icon in the dashboard submenu (it looks like some horizontal lines, and is not great; patches welcome!) *Boards These are a display of several worklists on a page, which can visualise the progress of tasks. You can create due dates which can be shared across boards, and then apply them to items in a worklist in a board. it's all hard to explain in words, so here's a board: https://storyboard.openstack.org/#!/board/1 Things in a board you have permissions for can be moved, deleted, reordered, etc. Boards are created and accessed from the same places as worklists.At the moment they only show manual worklists, and you can't import an existing worklist into a board. * AUTOMATIC WORKLISTS You can now also have an automatically updating worklist filtered by, say "all tasks in the project 'StoryBoard', that are in review" and so on. I suggest trying it out and seeing what's around (when creating a worklist, there's a checkbox for 'automatic'; check it and see what happens). These worklists cannot be reordered. We want to make all boards and worklists more discoverable in the future; they're a bit tucked away at the moment. We're also working toward automatic worklists in boards... * Task Notes Now you can add notes to a task. This lets you say 'patch in review here', etc, a bit more easily than putting a long list of urls in the story description. There's a funny-looking button next to the task title on the story detail page; clicking it should allow you to add notes. It's white if there are no notes and black-on-red if there are some. That was a very long email, sorry. We tend to be around in #storyboard on freenode, though it's a holiday weekend over here in the UK, so... I picked a bad time to send this! :D New contributors and patches always welcome; the codebase is a mix of python, angularjs, and html/css. Most of this is SotK's work, and I just yell about it so he gets the credit he deserves; he has done an amazing job; thanks, SotK! And thanks again to everyone who has been involved so far, you're the best! If I've missed anything, please say. :) Best Wishes and Happy Task-Tracking, Zara ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Openstack Infra's puppet manifests and Puppet style guide.
On 25/03/16 05:23, Elizabeth K. Joseph wrote: On Thu, Mar 24, 2016 at 7:11 AM, Paul Belanger wrote: I cannot thing of something, besides linting, to better understand our modules and sub projects. And interested to here what others think. I'm certainly glad we have someone who is interested in helping out, I never meant to imply otherwise. Thanks for diving in Andrey :) My fear in a case like this with so many patches from a single new contributor, that it's turned less into a learning exercise and more into a lot of repetition. This quickly becomes much less valuable for getting familiar with things, I'm sure it's very boring, and it is filling up our review queue. I'm also conscious of the fact that not all reordering in Puppet has no impact on functionality, so it does take diligence on the part of the reviewer to make sure we don't break anything in the "harmless" effort to improve style. As for ideas for newcomers, back when we used Launchpad for bug and task tracking we had a low-hanging-fruit tag. This helped me get my first changes in that spanned across a broad number of areas of our infra. These were much more interesting than lint fixes! My hope was that we could somehow continue this in Storyboard. Perhaps even working to take some of the things that established contributors, by reflex, just fix immediately but don't strictly need immediate fixes and tag to give those tasks to newcomers to get their feet wet. I think a separate newcomer thread is in order. Thanks for laying this out; this matches my view. This has also reminded me that I missed something in the 'new things StoryBoard does' email: Tags can be applied and searched in StoryBoard these days. You can search them from the sidebar search, or from the search bar at the top of the list of stories, *not* the header search (yup, search needs some improvements) :) Anyway, this means it's possible to tag things as 'low-hanging-fruit', and for someone else to see all things tagged that way, so the same workflow *can* be used, but it depends on people remembering to tag things. (In theory it's possible to make an automatic worklist from that tag, though in practice those are a bit buggy-- they don't return all the stories they should-- and we're still investigating it. Automatic worklists seem fine for everything *but* tags, for added amusement.) ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [StoryBoard] Meetings (and meetup) info
Hi all! At the summit, a few people asked us about StoryBoard meetings (and the next StoryBoard meetup). So here are the details: IRC Meetings (text shamelessly copied from wiki): - StoryBoard holds public weekly meetings in #openstack-meeting, Wednesdays at 1500 UTC. Everyone who is interested in development and use of StoryBoard is encouraged to attend. In-Person Meetup: - https://wiki.openstack.org/wiki/StoryBoard/Milestone_1_Meetup (date= May 16th; this was voted on in the StoryBoard meeting shortly after the last meetup) Feel free to update the etherpad. :) Hope to see you there! We're also always available in #storyboard on freenode. Best Wishes, Zara ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Tools for tracking the Scientific WG
Hi! Some notes on the interface (hopefully we should have a nice tutorial eventually): On 10/05/16 09:02, Stig Telfer wrote: On 10 May 2016, at 01:00, Blair Bethwaite wrote: Hi Jeremy, On 10 May 2016 at 03:25, Jeremy Stanley wrote: Worth noting, Storyboard does have kanban functionality similar to that. It calls them "worklists" (simple) or "boards" (customizable multi-lane) but they're the same sort of card organizing system. I thought so as I quickly found the list functionality... But tbh I find the interface somewhat confusing and could not, after another 5 minutes just now, figure out how to add items to a list... they seem to have to exist as "tasks" or "stories" already, but I can't figure out how to create a "task" (or perhaps what the difference between a "task and a "story" is?), and "stories" seem to have to be part of a project, but I can't create a project...? Yeah, tasks can only be added to a board after being created as part of a story. (stories can be created from the board view-- 'create story' on the left when you click 'add a card'. That page doesn't yet allow users to add tasks to an existing story, but that is on the list of things to fix in the future.) In the meantime, one can create a task via the 'add task' button on a story detail view (eg: https://storyboard.openstack.org/#!/story/2000476) or the 'add another task' button when creating a new story. On tasks vs stories, from the about page: 'A story is a bug report or proposed feature. Stories are then further split into tasks, which affect a given project and branch' So roughly, a story is the goal a team is working toward. A task is a specific item of work the team is doing to meet that goal. As I understand it, StoryBoard mandates that tasks are tied to stories so that it's clearer a) why people are doing things and b) so that tasks are trackable. Each task within a story can be tied to a different project, to allow for cross-project work to be recorded. It's not possible to create a task in isolation from its goal or the project it affects. (In general, unusual things about the StoryBoard interface are due to it being designed for cross-project work on the scale of OpenStack. Whether or not a team benefits from the quirks probably depends on how much that team plans to coordinate with other teams.) I had a go on the sandbox instance and (perhaps because I authenticated) could see the options for creating new stories, worklists and boards, but couldn’t see a way of creating a new project to put them all in. Is that something that requires greater admin privileges? Yes, that's right, currently only logged in users can create stories, tasks, boards and worklists, and only admin users can create projects (and project groups). Best wishes, Stig ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] A tool for slurping gerrit changes in to bug updates
On 25/05/16 18:44, Anita Kuno wrote: On 05/25/2016 01:13 PM, Jeremy Stanley wrote: On 2016-05-25 11:43:39 -0500 (-0500), Gregory Haynes wrote: [...] We are considering making a small project to connect to and read from the Gerrit event stream and then update our bug tracker. [...] If we implemented this, would this be something the -infra project would like to have live upstream? It seems easy enough to make this generally useful to others with similar requirements. Any other thoughts/comments that might help :). Please collaborate with the storyboard team on this. I believe the Gerrit integration plan there has always been to have an independent service which consumes the Gerrit event stream and then performs arbitrary callouts (likely over localhost on the storyboard server) to a task tracker API. Your goals seem closely aligned. I believe this is the patch that is in progress: https://review.openstack.org/#/c/302912/ I think Zara would welcome help on it if you want to talk to her in #storyboard. Thanks, Anita. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra Hi, I'd add to this that I found getting gerrit changes pretty trivial using gerritlib (well, my control flow in that WIP is dodgy, but that's more a combination of my inexperience and my lack of time). Updating the bug/task-tracker from those changes, however, would be different for each tracker, so you wouldn't be able to do that part in a generic way. Plus, while analyzing the data from the stream could theoretically be the same, in practice different data might matter for each tracker, and one might be looking for a different regex in the commit message, etc. So I think the only part that can be generic will be getting the changes from gerrit, and from other comments on this thread, it sounds as though people have already covered that. Best Wishes, Zara ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] A tool for slurping gerrit changes in to bug updates
On 26/05/16 14:06, Jeremy Stanley wrote: On 2016-05-26 11:37:18 +0100 (+0100), Zara Zaimeche wrote: [...] Updating the bug/task-tracker from those changes, however, would be different for each tracker, so you wouldn't be able to do that part in a generic way. Plus, while analyzing the data from the stream could theoretically be the same, in practice different data might matter for each tracker, and one might be looking for a different regex in the commit message, etc. So I think the only part that can be generic will be getting the changes from gerrit, and from other comments on this thread, it sounds as though people have already covered that. I'd imagine things like regular expression matches and API methods could be extracted into configuration (as long as we make assumptions like the task tracker APIs are all RESTish and don't require fancy branching business logic). So a rules engine which can be configured to tokenize parts of specified Gerrit events and then expand corresponding variables in configured API calls would presumably fit the bill. I agree regexps should definitely be extractable. I'm less sure about API methods; some general things I've noticed in discussion of task trackers are: * The APIs seem to often be a muddy spot (I hear complaints about how they're not as RESTful as desired) * Trackers designed to work on a small scale have a very different architecture from those designed to span multiple repos So the first point there makes me wonder how safe we are in assuming tracker APIs are all RESTish. The second makes me wonder how far a generic implementation can go, or whether it'd be better to have different implementations for cross-project bug/task-trackers vs single project bug/task-trackers. (eg: the contrast between StoryBoard and Github issues) The latter tend not to, say, distinguish between stories and tasks, which makes sense when the tracker doesn't have to worry about coordinating cross-project work. But if someone writes middleware that assumes stories and tasks are the same thing in a tracker, it requires some fiddling to make it work for StoryBoard, possibly to the point where it's easier to implement a custom thing from scratch. From my perspective, there's a good chance that something designed initially for Github Enterprise won't have much I can use-- which is still fine; we were just asked if we'd find it useful. :) StoryBoard is the unusual one here, and I think a lot of teams with smaller trackers will find their architecture similar enough for it to work for them. And maybe it's possible not to make those assumptions, but I figure if I flag it up, it's easier for people to know what assumptions they're making, and choose an approach from the start. Best Wishes, Zara ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [StoryBoard] StoryBoard Bug Squash!
Hi all! We're running a bugsquash for bugs in StoryBoard and the StoryBoard webclient, on the 22nd and 23rd of June. It'll start and finish around 11:00 UTC-- though of course every day is a StoryBoard bugsquash day *really*, so that's just the timeframe where StoryBoard people will sometimes be active in #openstack-sprint on freenode. We'll also be around in #storyboard, which is where we live the rest of the time. If you're interested in helping out with the bugs, then it's a good time to start! We're going to try to be more vigilant actually tagging low-hanging-fruit as low-hanging-fruit in the next couple of weeks, so that it's easy for people to see what needs work. :) Feel free to join #storyboard if you want to squash some bugs. Or if you have questions. Or if you just want to keep us company. Best Wishes, Zara (and SotK probably also wishes you all well, but he hasn't seen this email, so I won't put his name on it, except in parentheses like these) ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
