09:01:45 #startmeeting blazar 09:01:46 Meeting started Tue Jan 9 09:01:45 2018 UTC and is due to finish in 60 minutes. The chair is masahito. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:01:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:49 The meeting name has been set to 'blazar' 09:02:06 #topic RollCall 09:02:18 o/ 09:02:25 o/ 09:02:28 o/ 09:02:48 priteau, hiro-kobayashi, bertys: hi, Happy New Year! 09:03:00 Today's agenda is 09:03:03 Happy New Year! 09:03:11 1. project mascot 09:03:14 2. status update 09:03:17 3. AOB 09:03:18 Happy New Year everyone 09:03:22 anything else? 09:04:18 Bonne Annee! Happy New Year! 09:04:55 #topic project mascot 09:05:33 The foundation staff sent me a project mascot this morning. 09:05:51 https://drive.google.com/open?id=0BwsSjc7Nvglja2IwSkF1V1VwWTZ1NmhlbkRxSkRhQUtlcjRZ 09:06:12 It's cute 09:06:14 It's a house mouse as we voted. 09:06:22 Yes, it's so cute! 09:06:36 yes. it's cute. 09:07:27 If there isn't a problem, I replay ok to them. 09:07:52 +1 09:08:00 Gerald isn't here today, so I'll send the mascot to him, too. 09:08:13 I was going to say the same thing 09:08:30 He proposed the house mouse, so he should check if it looks like what he had in mind 09:08:58 right 09:11:13 I don't remember if we said that the mouse would be sitting on cheese or something like that. Anyway, I think it looks great as it is 09:13:12 IIRC, we didn't mention that. 09:13:17 masahito: Just shared this info with Gerald. He will come back to u. Thanks 09:14:14 bertys: thanks 09:14:35 okay, let's move on to next 09:14:41 #topic status update 09:15:21 we skipped last 2 meeting. So if someone has updates, please share it. 09:15:47 I have some updates. 09:15:53 1. API reference 09:16:10 I pushed patches of a new API reference 09:16:17 https://review.openstack.org/#/c/530054/ 09:16:29 https://review.openstack.org/#/c/530065/ 09:16:49 And for testing them, I added a build-openstack-api-ref job. 09:17:04 the result is: http://logs.openstack.org/65/530065/4/check/build-openstack-api-ref/6fc74b2/html/v1/index.html 09:17:46 It looks great, thanks a lot for doing this Hiro! 09:18:01 hiro-kobayashi: Great work! 09:18:03 After merging them, I'll apply api reference publish jobs to publish the reference on developer.openstack.org/api-ref 09:18:16 my pleasure 09:19:04 So please review them ;-) 09:19:36 2. version 0.x.0 09:20:26 You know, there was a mail about versioning: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125843.html 09:20:37 I was going to mention it in AOB 09:21:17 When will we use 1.0? 09:21:59 IMO, Queens release is a good chance to use 1.0.0. 09:22:37 +1 09:23:05 Blazar became an official project, will support resource monitoring and got its mascot :-) 09:23:20 And perhaps we should describe the instance reservation is beta until we solve the affinity filter problem 09:23:25 Should we use 1.0.0 only when we reach OpenStack-wide goals though? 09:24:22 Support queens wide goals? 09:24:37 Queens and previous releases 09:24:46 I haven't been able to make much progress on Python 3 support 09:26:08 Lots of project don't support all wide goal but started to use x.0.0. 09:26:08 No strong opinion, Queens or Rocky both fine with me 09:27:09 masahito: true 09:27:13 Sean's mail would mention both feature side and project marketing side. 09:28:26 like ready to deploy in production or ready to say "The project has real codes that work well.". 09:28:36 Not strong but I prefer Queens because Blazar itself works well. It can promote use of blazar. 09:31:07 We can move to 1.0.0 as long as it is clearly documented that there are still shortcomings compared to more advanced projects 09:33:19 you mean shortcoming in features? 09:34:32 or do you mean to have "known issues" section in Blazar release notes https://docs.openstack.org/releasenotes/blazar/unreleased.html? 09:35:02 Things like online upgrades, HA, etc. which are supported by the core OpenStack projects 09:35:11 bertys: Sounds good! 09:36:32 The list is like maturity in project navigator. 09:37:01 IIRC, none of project has all features listed in maturity. 09:38:21 hi. sorry for being late. bertys just pointed me to the proposed mascot. l like it. 09:39:05 GeraldK: hi happy new year! 09:39:13 happy new year to all of you. 09:40:28 Based on the all's opinion, how about we decide feature list to release 1.0.0 for Blazar? 09:41:45 Sounds good 09:43:00 And shall we add notes of important missing features in release notes or docs? 09:43:44 Sorry, missing features compared to what? 09:45:19 Sorru but I don't have a clear definition. If any active contributor says it's important, then it's important. 09:45:39 IMHO can be any missing features that we are aware of 09:45:46 I would say in docs, since release notes are per-release, and we may not have things like HA or online upgrades until much later 09:46:45 I think it's a role of project navigator. Of course, docs is fine for each projects. 09:46:59 Are we in the project navigator? 09:47:34 It doesn't even show the Pike release 09:48:01 https://www.openstack.org/software/project-navigator/ 09:48:05 not yet. 09:48:14 There is not Queens in the project navigator. 09:48:21 we need to add Blazar to it. 09:49:22 I see the project navigator seems to be based on tags: https://governance.openstack.org/tc/reference/tags/ 09:49:28 I'll ask infra team? or someone who is in charge of the page.. 09:49:52 So, if the tags for Blazar are correct, we could do without adding the same information in the docs 09:51:42 maybe 09:52:19 Anyway, I'll ask how we list Blazar in the navigator. 09:53:18 thanks! 09:53:27 and once we've added tags or written docs we'll be ready to release 1.0.0. 09:53:31 right? 09:54:01 +1 09:54:05 OK 09:55:12 last 5 mins. 09:55:25 anything to share? 09:55:39 I don't have other updates. 09:56:58 okay, then let's end early. 09:57:36 thanks all! 09:57:58 Thanks! see you! 09:58:01 bye 09:58:07 bye 09:58:13 #endmeeting