#openstack-meeting log

23:06:10 <reed> #startmeeting openstack-community
23:06:11 <openstack> Meeting started Wed Dec  4 23:06:10 2013 UTC and is due to finish in 60 minutes.  The chair is reed. Information about MeetBot at http://wiki.debian.org/MeetBot.
23:06:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
23:06:14 <openstack> The meeting name has been set to 'openstack_community'
23:06:59 <sarob> so what do you think about https://blueprints.launchpad.net/openstack-community/+spec/foundation-participation-table
23:07:10 <reed> #link  https://blueprints.launchpad.net/openstack-community/+spec/foundation-participation-table
23:07:33 * reed opening
23:07:57 <reed> right, I saw the wiki page too
23:08:15 <sarob> reed: something good here?
23:08:24 <reed> #topic tools to help newcomers understand the Foundation at a glance
23:08:41 <reed> sarob, indeed, lots of good stuff there
23:08:47 <sarob> reed: cool
23:09:06 <reed> the wiki page is not fully readable on my system though
23:09:16 <reed> looks like a part of it is cut
23:09:19 <sarob> i'd like to expand/include what board director responsibilities are
23:09:32 <sarob> hmm, its big for sure
23:09:42 <sarob> im not a UI guy
23:09:46 <reed> :)
23:09:50 * sarob just the facts
23:09:59 <reed> and tables in the wiki are just hard
23:10:16 <reed> anyway, one thing I'd like to understand better is the scope of the project
23:10:22 <sarob> right, i gamed it through a gsheet
23:10:35 <reed> where did the need come from?
23:10:53 <sarob> reed: as long as the info gets to eyeballs
23:11:13 <sarob> reed: i will plant the flag of success in victory
23:11:39 <sarob> reed: we know this stuff cause we have been living the dream
23:12:02 <sarob> reed: many do not know details like this and have no idea where to find them
23:12:43 <reed> sarob, I'm wondering whether it would make sense to create a page for each of the entity you describe in the table and group those pages into one master page
23:12:54 <reed> nah, it would not be readable
23:13:06 <sarob> maybe mouse over
23:13:18 <reed> I'm afraid of the maintainability of a huge table
23:13:22 <reed> on a wiki
23:13:24 <sarob> me too
23:13:34 <sarob> its just a starting place i think
23:13:45 <reed> btw, https://docs.google.com/spreadsheet/ccc?key=0AgwM400_8SNZdE9GVlZkOVdnWU5hTjJuWXk4NzN2dlE#gid=0 needs permission
23:13:58 <reed> i agree with you, it's a starting point
23:14:20 <reed> maybe from there we can go and improve the pages of each item?
23:14:41 <reed> for example, something I have noticed is that the individual program pages are not consistent
23:14:43 <sarob> reed: your openstack.org account?
23:15:02 <reed> sarob, stefano@openstack.org
23:15:07 <reed> or just make it public
23:15:19 <reed> since you link it from the public wiki anyway
23:15:36 <sarob> hmm, its on my yahoo-inc account, i can move it to my private
23:15:43 <sarob> task for me
23:16:04 <reed> see for example: https://wiki.openstack.org/wiki/Nova and https://wiki.openstack.org/wiki/Horizon have different information
23:16:18 <reed> not sure if the wiki pages can be 'templatized'
23:16:59 <reed> #idea can wiki pages carry templates? how can we make the individual program pages more coherent, carry the same sort of information?
23:17:00 <sarob> reed: hmm, not sure, but is that this problem?
23:17:17 <reed> sarob, in a way I think it is
23:17:33 <sarob> reed: we need someone like marketing to own communicating the table info
23:17:51 <reed> sarob, if I understand the problem you're addressing is the lack of 'at a glance' useful information in lots of our pieces
23:18:13 <sarob> reed: well, a bit of it
23:18:28 <reed> sarob, expand then, I'm interested
23:18:41 <sarob> reed: for instance when a new corporation wants to join 'openstack'
23:18:52 <sarob> reed: what are their options
23:19:02 <sarob> reed: i can tell them, which i have been doing
23:19:29 <sarob> reed: but we need a one stop digital place to start a new 'person' off at
23:19:52 <sarob> reed: participation table is a rough example
23:20:12 <reed> got it... have you talked with Heidi about i?
23:20:27 <sarob> reed: at the summit yup
23:20:42 <sarob> circling back to her and lauren this week
23:21:30 <reed> nice, I'm sure they may have more thoughts too
23:22:15 <sarob> #link https://docs.google.com/spreadsheet/ccc?key=0Ahy1qS0O_cnldFdEcHNVdEJEN2tnTWNnZV9ZeThhZmc&usp=sharing
23:22:22 <sarob> public now
23:23:04 <reed> cool
23:23:57 <sarob> reed: wiki updated
23:24:35 <sarob> reed: so lets call this 'blueprint' done and hand off to heidi
23:24:42 <sarob> reed: we help as they need?
23:24:43 <reed> sounds good to me
23:24:49 <sarob> reed: cool
23:25:09 <sarob> reed: okay, my other burning thought
23:25:13 <reed> she can pull from the wiki page and make a nicer looking html page on the site if needed
23:25:27 <sarob> reed: certainly
23:25:46 <sarob> reed: and i can help expand on some more thoughts when she is ready
23:26:25 <sarob> reed: so the community training
23:26:34 <reed> #topic community training
23:26:42 <sarob> reed: sweet
23:27:03 <sarob> reed: the first book is ready for a havana branch publish
23:27:15 <sarob> reed: its a rough draft, but ready enuf
23:27:35 <reed> I saw a message about that somewhere, cool
23:28:13 <reed> #info  the first book is ready for a havana branch publish
23:28:17 <sarob> #link http://docs.openstack.org/trunk/training-guides/content/bk001-associate-training-guide.html
23:28:52 <reed> sweet
23:28:58 <sarob> reed: do you have any thoughts on next steps?
23:29:18 <sarob> reed: im thinking publish link to training.openstack.org
23:29:49 <sarob> reed: plus aptira will be using most of the associate guide for their training classes
23:30:13 <sarob> reed: anything else you think we should do?
23:30:17 <reed> that might work, I think Heidi and Mark own that page
23:30:32 <reed> blog post?
23:30:44 <sarob> reed: hmm like
23:30:53 <reed> i love blog posts :) they're my cheap way to do press releases
23:31:16 <reed> we may also want to ask teachers to look at it and let us know
23:31:40 <sarob> reed: hmm, right that reminds me
23:31:54 <reed> my friend prof. Verma at SF State will be interested
23:32:01 <reed> did I put you in touch with him already?
23:32:02 <sarob> reed: im really bad at collecting names and getting back to them, timely
23:32:26 <sarob> reed: you did, i havent circled back with details yet
23:32:42 <reed> ok, this may be an excuse
23:32:55 <sarob> reed: of?
23:33:16 <reed> so, I think we should push a blog post out with it and I'll ping Sameer Verma right after, putting you in CC
23:33:27 <sarob> reed: /me has he figured out that i dont know what i am doing?
23:33:39 * sarob has he figured out that i dont know what i am doing?
23:33:48 <reed> we're all good at faking to know what we're doing :)
23:33:59 <sarob> reed: hmm, yes
23:34:19 <reed> what do you think should be in the blog post?
23:34:37 <reed> anything you want to highlight?
23:34:40 <sarob> reed: for training, its would be about
23:35:02 <sarob> reed: community training purpose, history, next steps
23:35:56 <reed> are the quiz supposed to be in the manual?
23:36:03 <sarob> reed: we should share a gsheet of universities that are openstack community interested
23:36:25 <sarob> reed: perhaps along with their interest and status
23:36:36 <reed> sarob, wiki page, better so we don't loose it
23:37:10 <reed> we used to have an openstack academia group, we may want to revive it
23:37:15 <sarob> reed: well, i would want our new friends getting spammed is all
23:37:42 <sarob> reed: ohh, openstack academia , sarob like much
23:37:45 <reed> https://wiki.openstack.org/wiki/AcademicInitiative
23:38:47 <sarob> reed: okay, righto
23:39:26 <reed> that effort kinda died down after an initial burst
23:39:35 <sarob> reed: 87 members
23:39:51 <reed> there was one guy getting his phd who was active at the beginning and then it got lost
23:40:02 <reed> maybe the scope was too broad? too shallow? not sure
23:40:20 <sarob> reed: i think so
23:40:41 <reed> things have changed though, we may have more luck now if we want to reboot it
23:40:53 <sarob> reed: a list of interested people, their interest, and status
23:41:05 <sarob> reed: maybe add events
23:41:25 <sarob> reed: other than that, the rest should be just openstack projects
23:41:42 <sarob> reed: like regular people ;)
23:42:01 <reed> we go back to the lack of visibility of people and members, activities
23:42:08 <reed> events, etc
23:42:14 <sarob> reed: hmm, right
23:42:42 <sarob> reed: launchpad sucks as a community tool
23:42:45 <reed> and to the user groups portal ... which is lagging behind the openid project
23:42:47 <sarob> reed: communication tool
23:43:18 <reed> ok, before I get depressed thinking about it, let's think about what we can do with what we have today
23:43:19 <sarob> reed: well, we can steer students to user groups easy enough
23:43:31 <sarob> reed: right you are
23:44:24 <reed> the blog post could link to the wiki page
23:44:42 <sarob> reed: we need a list of names, email, university, interest, status
23:44:54 <reed> since we moved all our lists off of launchpad, is it worth trying to create an openstack-academia list on lists.o.o?
23:44:59 <sarob> reed: for unversity angle
23:45:20 <reed> university as in 'teaching openstack' or cloudy topics, right?
23:45:36 <reed> not 'researching cloud stuff'
23:45:37 <sarob> reed: sure, buuuut, we need to add those important attributes
23:45:53 <sarob> reed: right, like teaching openstack
23:46:36 <reed> ok, we know of a few universities that teach cloud using openstack
23:46:47 <sarob> reed: the blog post can certainly request unversity prof, grads to reach out
23:47:12 <sarob> reed: other focus is user group education
23:47:16 <reed> shall we ask them to subscribe to a mlist and introduce themselves?
23:47:49 <reed> or setup a google form?
23:48:11 <sarob> reed: if we could add the unversity, interest, status attributes to foundation members
23:48:18 <reed> to ask them to answer a few questions?
23:48:22 <sarob> reed: is that possible today?
23:48:55 <sarob> reed: google form could def work
23:48:59 <reed> not without a massive investment on my or Tom's side to convince the website developers to do things
23:49:19 <sarob> reed: okay np, google form is a good start
23:49:37 <reed> so we could ask them there:
23:49:40 <sarob> reed: it will dump into a gsheet, so that would be very useful
23:50:16 <reed> university/affiliation, interest... what else?
23:50:44 <sarob> reed: status of work with openstack
23:50:48 <reed> a Y/N flag like 'Would you like to be contacted by members of the community with additional questions'?
23:50:59 <reed> email ...
23:51:02 <sarob> reed: thats good
23:51:22 <reed> that should be a good way to get started
23:51:24 <sarob> reed: some info about the community channel and mailling list
23:51:32 <reed> what do you mean?
23:52:40 <sarob> reed: provide a bit of openstack community info on the form in case it gets shared separate from the blog post
23:53:04 <reed> gotcha
23:53:29 <sarob> reed: /me i feel productive
23:53:47 <reed> #action write a blog post to announce the first release of training material
23:53:58 <sarob> reed: my thoughts betray me
23:54:48 <reed> #action prepare a google form with intro to community and questions for teachers/profs about  university/affiliation, interest, status of work with openstack, email, a Y/N flag like 'Would you like to be contacted by members of the community with additional questions'
23:55:17 <sarob> reed: if you can approve the blueprint so others understand we agree
23:56:19 <reed> #action reed to send a draft of the blog post to the community list
23:56:32 <reed> sarob, which bp exactly?
23:56:35 <sarob> reed: id like to update the https://launchpad.net/~openstack-academia and http://wiki.openstack.org/AcademicInitiative pages as well
23:57:04 <reed> sarob, yeah... I think we should deprecate the launchpad team
23:57:14 <sarob> reed: the https://blueprints.launchpad.net/openstack-community/+spec/foundation-participation-table
23:57:27 <reed> either create a new mlist or use the community list (low enough traffic, I think)
23:57:38 <sarob> reed: new mlist def
23:58:05 <reed> we could treat the academia circle as a Special Interest Group under the user groups umbrella
23:58:29 <sarob> reed: i like that
23:58:46 <reed> it's a conversation to have with fifieldt too
23:58:59 <sarob> reed: cause im on a mission to create one new user group per quarter
23:59:04 <sarob> reed: at universities
23:59:13 <fifieldt> hi
23:59:40 <sarob> fifieldt and there you are
00:00:10 <fifieldt> hi, yes
00:00:11 <fifieldt> hi
00:00:11 <fifieldt> :)
00:00:18 <sarob> fifieldt whatchu think about our discussion above?
00:00:44 <fifieldt> it's a good idea, needs careful phrasing
00:01:02 <fifieldt> lecturers can be a bit tetchy about sharing content
00:01:22 <fifieldt> but if you come to them with something they can use
00:01:25 <fifieldt> they'll love it
00:01:37 <sarob> fifieldt roger that
00:02:10 <reed> anything else to discuss?
00:02:16 <fifieldt> so it's good to do sooner rather than later
00:02:22 <fifieldt> while noone has gone to the effort of making slides
00:03:01 <fifieldt> not so much
00:03:03 <sarob> fifieldt reed a slide generation and archival tool for training guides is in the near future
00:03:08 <fifieldt> :)
00:03:19 <reed> neat :)
00:03:20 <sarob> for trainers/prof
00:03:20 <fifieldt> we could chat about the travel support software, reed
00:03:45 <sarob> im chatted out, so next topic
00:04:12 <fifieldt> well, so just to give sarob an update
00:04:28 <fifieldt> SUSE has some software for running their travel support program
00:04:32 <fifieldt> reed discovered it :)
00:04:42 <reed> #topic travel support software
00:04:47 <fifieldt> and we were thinking to see if we could use it for the summit travel
00:04:51 <sarob> interesting
00:04:52 <fifieldt> and/or the ambassador funding program
00:04:58 <sarob> cool
00:05:22 <fifieldt> unfortunately, it seems like it's not directly usable - we'd need to do some mods
00:05:59 <fifieldt> and given it's in ruby, and fairly basic to begin with, DIYing one in something more maintainable for our community (python/django) is an option as well
00:06:12 <sarob> cool
00:06:28 <fifieldt> the idea of a tool is to provide process/tracking through the applications
00:06:31 <fifieldt> and also some reporting
00:06:44 <fifieldt> in order to replace that google spreadsheet we used for summit travel
00:06:51 <fifieldt> and also the eventual voting process that turned out
00:07:18 <reed> we need to have forms to enter data and a workflow to keep things in order... eventually also for reporting
00:07:25 <fifieldt> aye
00:07:43 <fifieldt> and ideally, something that integrates with the magical SSO system reed is building
00:07:58 <sarob> magic, aye
00:08:07 <reed> after the voting process there are notifications to be sent, final acceptance by the candidates, and the whole shebang dealing with the fine details of who goes from where and when
00:08:31 <fifieldt> such as travel agents
00:09:11 <sarob> getting unversities more invovled probably will make this tool even more important
00:09:22 <reed> I was looking at a workflow engine in django, seems quite powerful but I'd rather not code :)
00:09:33 <fifieldt> :D
00:09:34 <reed> sarob, yeah, and for Ambassadors too :)
00:09:42 <sarob> yup
00:09:52 <sarob> i have to take my boy to a bb game
00:10:11 <fifieldt> sounds fun
00:10:13 <sarob> gotta bail on you two
00:10:33 <fifieldt> enjoy
00:10:39 <sarob> good progress all around
00:10:45 <sarob> talk soon
00:10:51 <reed> bye sarob
00:11:14 <reed> we may want to close the meeting too
00:11:18 <fifieldt> sure
00:11:29 <reed> #endmeeting