15:02:58 #startmeeting StoryBoard 15:02:59 Meeting started Mon Jun 9 15:02:58 2014 UTC and is due to finish in 60 minutes. The chair is NikitaKonovalov. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:03 The meeting name has been set to 'storyboard' 15:03:37 Agenda as always is here https://wiki.openstack.org/wiki/StoryBoard 15:04:33 #topic Roadmap(ttx) 15:04:38 hey 15:04:58 So we had a high-level roadmap on the etherpad from the juno design summit session 15:05:08 I turned it into a wikipage for a bit more... permanence 15:05:17 #link https://wiki.openstack.org/wiki/StoryBoard/Roadmap 15:05:43 First task is to the items we have completed 15:06:16 NikitaKonovalov: do you see anything that should be marked as completed? 15:06:28 I think "UI to find tasks assigned to you" is already implemented by krotscheck's commit 15:06:52 NikitaKonovalov: thought so too, but the prod instance is not showing it? 15:08:11 Second thing to note, I split what was MVP 1.2 on the etherpad into two slightly separate steps (1.2 and 1.2.1) 15:08:21 following a suggestion from mordred 15:08:43 that integrated projects could switch to using storyboard for blueprints sooner that they switch to using storyboard for bugs 15:09:04 (which makes sense, since launchpad blueprints are so horrible, while bugs are pretty decent) 15:09:15 sounds resonable to me 15:09:18 so that lets us having a slightly shorter list at 1.2 15:09:27 and prioritize in a useful way 15:09:47 for example we don't need secret features or backport tasks for blueprints 15:10:44 OK, that's all I had on this topic 15:11:05 I've noticed LP import before using for blueprints 15:11:13 what sohuld we import? 15:12:52 NikitaKonovalov: it's a bit unclear 15:13:17 NikitaKonovalov: basically I'm not 100% certain there is so much value to import from LP until we hit 1.2.1 15:13:23 (integrated projects bugs) 15:13:52 ok, let's get back to that later 15:13:55 existing infra bugs and integrated projects blueprints may not have that much value to import 15:14:01 It's a discussion with those stakeholders 15:14:19 It's something we'll need to support for sure 15:14:51 just not entirely clear how critical it is for the various groups, so in which milestone it should land 15:15:14 hence the "?" on that line :) 15:15:58 agree, we need to practice importing stuff at some point before big projects decide to move to SB 15:16:24 ok, next topic is specs 15:16:29 #topic Specs 15:16:40 OK, let's try to find those in infra-specs 15:17:02 I'll add them to the agenda 15:17:39 OK, same list 15:18:13 refreshed agenda page 15:18:42 i didn't get any review on the tags spec 15:19:15 I need to review the search spec 15:19:29 ttx: I've looked through the tags spec 15:20:34 I think we should also have tags for projects, so that a User could mark a project 15:20:57 NikitaKonovalov: could you give an example of what you would use that for ? 15:21:13 I'd rather have "project groups" to do random project grouping 15:22:23 because i can't think of a project "tag" that wouldn't actually make sense as a project group instead 15:22:24 Let's say a User wants to tag all python-whateverclient project with a "client" tag 15:22:48 and then subscribe to all stories that affect client libraries 15:22:58 NikitaKonovalov: I think we should have a "client libraries" project group then 15:23:12 It makes sense to be centrally administered 15:23:51 I fear if we allow random tagging of projects, they will end up with a long list of them 15:24:09 we should rather identify the needs for grouping and provide them as project groups 15:24:26 "client" is a valid project group 15:24:31 as would be "infra" 15:24:38 or "all-storyboard" 15:24:56 that makes sense 15:25:11 NikitaKonovalov: I guess we could implement projectgroups as project tags though, if we restrict tagging to admins 15:25:27 but I'd rather not overload the meaning of "tags" 15:25:46 agree let's keep tags for Stories only 15:26:09 a given project (code repo) will just be a part of a number of project groups. And if one group is missing, we should just create it 15:26:25 havign them centrally administered will let us be coherent 15:26:37 (if we had a new client project somwhere, we'll add it to the clients projectgroup) 15:26:41 add* 15:26:53 anyway, I digress :) 15:27:09 at least we can create groups based on project prefix like openstack-infra/nodepool is definitlly going under openstack-infa group 15:27:55 NikitaKonovalov: let's see if anything else on MVP1.1 needs a spec 15:28:21 NikitaKonovalov: project groups maybe? 15:28:44 looks so 15:28:48 I seem to remember there were some bits of it already landed, though ? 15:29:16 * ttx adds spec links to the roadmap 15:29:30 There is an API that allows all necessary operations for project groups and projects inside those 15:30:27 may be the load_projects script needs an update to create groups in a smarter way 15:30:34 and there is no UI at all 15:30:41 NikitaKonovalov: ok, so probably not needing a spec if it's half-implmeented already 15:31:20 I think a Story should be enough to describe that 15:31:40 ack 15:31:53 #action NikitaKonovalov create a Story for Project Groups 15:32:01 updated https://wiki.openstack.org/wiki/StoryBoard/Roadmap with links to specs 15:32:22 great 15:32:23 I guess we could add links to stories there too 15:33:02 so the next spec is for Search 15:33:28 I've got some comments from krotscheck 15:33:55 i'll review it soon 15:34:03 the main thing missing there is "What should the query strings look like?" 15:34:55 ok, will keep an eye on that 15:34:55 We can postpone that until we have a quorum for a discussion 15:35:16 morning 15:35:21 o/ 15:36:57 so we have a spec for subscriptions 15:37:38 I like it 15:37:46 and it looks like the most complex 15:41:08 I guess we should wait for some reviews before implementing that 15:42:20 Looks like that's all for the specs 15:42:32 #topic Ongoing work 15:42:59 NikitaKonovalov: you go first 15:43:18 I'm working on name fields validation 15:44:23 The name fields of projects and project groups should be url friendly 15:45:05 So there is a bunch of changes to introduce that validation 15:45:10 and some testing for it 15:46:19 That's pretty much all from my side because I was a bit busy last week with my University graduation work 15:47:11 And I guess I'll be for this week too 15:47:20 NikitaKonovalov: heh 15:47:43 OK, on my side, I worked on the roadmap and need to work on spec review 15:47:51 I try to keep up with reviews 15:48:13 I might work on more documentation around the project, to clarify the intent and goals 15:48:22 and status 15:48:33 as there seems to be a bit of misunderstanding on that side 15:49:03 EOF 15:49:38 time for an open discussion 15:49:45 #topic Open discussion 15:51:16 NikitaKonovalov: nothing to add 15:51:24 Thanks for running the meeting! 15:51:45 we have holidays on Thursday and Friday in Russia this week 15:52:11 I have a holiday today here. (don't ask) 15:52:22 ok 15:52:26 #endmeeting