12:59:55 #startmeeting evoque 12:59:55 Meeting started Wed Nov 18 12:59:55 2015 UTC and is due to finish in 60 minutes. The chair is Liuqing. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:59:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:59:59 hi 13:00:00 The meeting name has been set to 'evoque' 13:00:14 \o 13:00:30 if you're here, please say hi 13:00:37 hi 13:01:04 let's know who're here :-) 13:01:27 #topic dummy workflow engine 13:01:50 why not start with anouncement? 13:02:13 as we talked offline in shanghai , we'll have a dummy workflow engine. 13:02:19 ok 13:02:21 do we have any anouncement? 13:03:07 devstack plugin, test framework 13:03:10 ... 13:03:20 we will use stevedore to load dummy workflow engine driver 13:04:38 we should add devstack plugin in this week? 13:05:10 I think, sooner is better than later. 13:05:26 let's others can play with the system. 13:05:47 i thought that we could add devstack plugin in version 0.0.1 release cycle. 13:06:08 well, we could write a plugin 13:06:18 and guide 13:06:34 EinstCrazy, +1 13:06:40 we should think more about the engine,but not the devstack plugin. 13:06:44 EinstCrazy, do u have time for it. 13:06:47 ? 13:07:17 why not let someone do what they want to do? 13:07:37 now we haven't one complete demo for evoque。 13:07:37 if EinstCrazy wants to set the devstack up, he can do. 13:07:39 well, I could do it. But may someone help me with how to install it? 13:07:46 EinstCray can help is good 13:07:49 It's my opinion. 13:07:58 Do what you want 13:08:22 #action EinstCray will help the evoque devstack plugin 13:09:13 sorry, let's back to topic dummy workflow engine 13:09:25 OK 13:09:39 who will take the work ? 13:09:46 sin_ 13:10:05 we have one initial devstack patch posted by zhurong: https://review.openstack.org/#/c/241923/ 13:10:23 EinstCrazy, that may help 13:11:03 the dummy workflow will have following abstract methods 13:11:13 1. workflow-list 13:11:16 2. workflow-show 13:11:24 devstack plugin i will improve it, EinstCrazy 13:11:37 3. worflow-get-status 13:11:58 4. worflow-start-instance 13:12:12 OK, zhurong can improve it 13:12:36 #action zhurong will help the evoque devstack plugin 13:13:15 #info https://github.com/knipknap/SpiffWorkflow/wiki 13:13:32 Liuqing, do we have BP for workflow? 13:13:33 #info workflow pattens http://www.workflowpatterns.com/ 13:13:41 not now 13:13:59 I think we should first put it into a BP, and review, and then work on codes. 13:14:02 gongysh, we should register it in launchpad 13:14:43 so who take the dummy workflow engine? 13:15:49 if nobody take the work, i will 13:16:13 #action liuqing could help the dummy workflow engine 13:16:29 move to the next topic 13:16:35 #topic evoque dev mail list 13:16:55 now we haven't any mail list in openstack dev ML 13:17:16 any thoughts guys ? 13:17:16 don't we just use [openstack-dev][eqvoque] in subject? 13:17:34 in general, it is 13:17:45 do other openstack projects have their own mail list? 13:17:50 I don't think so. 13:18:39 #info http://stackalytics.com/?project_type=all&module=evoque&metric=emails 13:18:48 ML about evoque in stacjalytics. 13:19:58 Contribution Summary is useful 13:20:19 Draft Blueprints: 1 13:20:20 Completed Blueprints: 0 13:20:21 Filed Bugs: 0 13:20:23 Resolved Bugs: 0 13:20:23 Emails: 0 13:20:33 yes 13:20:54 those items is not very well, maybe bad. 13:22:51 so in the next development, we should pay attention to our bad items. 13:24:37 any thoughts? guys? 13:24:49 currently, we have no bugs report? 13:25:10 may we invite someone to test and use for it? 13:25:24 any patchs should be under a bug or bp, I think. 13:25:51 agree 13:26:11 The core reviewers should have some rules, or 底线。 13:27:22 and had better two core reviewers agree. 13:27:55 gongysh__, it really 13:28:02 register some BPs, for example:devstack plugin,:) 13:28:31 zhangjn, welcome 13:29:36 how to register BP? 13:30:42 on launchpad, register a BP, and, if it is not too a big feature, just descript it in launchpad BP. 13:31:18 otherwise we can have it under evoque/doc/specs 13:31:39 and use the normal review process. 13:31:48 the wifi broken just now.. 13:32:47 i thought it depends, we need move forward faster.. 13:33:18 evoque/doc/specs better than launchpad 13:33:57 I said if the feature is obvious, we can just register it only on launchpad, describe it there. 13:34:33 If the feature is big, besides the launchpad, we need put it under evoque/doc/specs and go through normal review process. 13:34:45 Liuqing_, agree? 13:34:59 This is rule, :) 13:35:17 do we have other topics? 13:35:44 It seems Liuqing_ is gone with wind again. 13:36:41 Liuqing_ I thought you should write some introduction article about the project, and then we promote it. 13:36:43 in this stage, maybe feature implement is the most import, 13:38:34 register a bp may not take much time, i think 13:38:52 quick start guide maybe good start. 13:39:35 some introduction article for general user or develop? 13:41:04 write some in wiki.openstack.org 13:41:38 so we should improve the evoque wiki? gongysh__? 13:42:09 wiki, or in evoque doc 13:42:16 we can put it in evoque doc. 13:42:22 i think evoque doc 13:43:29 wiki/doc 13:43:30 wiki and doc 13:43:40 i think we can show the doc in https://readthedocs.org/ 13:43:56 wiki/doc 13:44:10 yep,zhurong 13:44:20 something url like http://evoque.readthedocs.org/ 13:45:00 wiki will have some introduction for user 13:45:00 just like other project's wiki 13:45:25 doc should contain details of evoque 13:45:41 zhurong, could you take the doc work? 13:46:31 project's wiki is good window for user. 13:46:50 we can build the doc skeleton firstly. 13:47:09 Agree 13:47:14 Next Sprint 13:47:17 :) 13:47:29 :--) 13:48:40 but who take the doc work? 13:49:28 EinstCrazy? 13:49:39 the devstack is taken by zhurong 13:50:05 i vote EinstCrazy:) 13:50:06 EinstCrazy, what about the doc? 13:50:41 I don't know rst format 13:50:41 you can put the doc in evoque/doc, that is the same as we write codes. 13:51:22 I known. But I have not write any rst doc before. 13:51:29 It is easy. Just learn from other project and google 13:51:37 EinstCrazy, we can refer to other project , it's easy for you :) 13:51:49 EinstCrazy, you can do it. 13:52:17 and we will help to review. 13:52:33 and even co-author to help 13:52:58 OK, I do it. 13:53:16 and it is *1, not *0.8. 13:53:16 great. 13:53:26 thanks EinstCrazy 13:54:16 LOL 13:54:25 #action EinstCrazy to start the doc job. 13:54:57 I will write a quick start first 13:55:09 Liuqing_, I am trying to help 13:55:13 great 13:55:36 great 13:56:43 OK,so we end the meeting? 13:56:57 sure 13:57:10 sure 13:58:00 if we have other topic we can talk in channel #openstack-evoque , i will end meeting 13:58:06 #endmeeting 13:59:04 #endmeeting 14:00:17 #endmeeting