*** harlowja has quit IRC | 00:24 | |
*** diablo_rojo has quit IRC | 00:58 | |
*** kumarmn has joined #openstack-tc | 02:58 | |
*** alex_xu has quit IRC | 03:11 | |
*** alex_xu has joined #openstack-tc | 03:14 | |
*** zhipeng has joined #openstack-tc | 03:51 | |
*** kumarmn has quit IRC | 04:04 | |
*** kumarmn has joined #openstack-tc | 04:04 | |
*** kumarmn has quit IRC | 04:09 | |
*** kumarmn has joined #openstack-tc | 05:07 | |
*** kumarmn has quit IRC | 05:12 | |
*** zhipeng has quit IRC | 06:37 | |
*** kumarmn has joined #openstack-tc | 08:10 | |
*** kumarmn has quit IRC | 08:14 | |
*** kumarmn has joined #openstack-tc | 08:41 | |
*** kumarmn has quit IRC | 08:45 | |
*** kumarmn has joined #openstack-tc | 09:05 | |
*** kumarmn has quit IRC | 09:10 | |
*** kumarmn has joined #openstack-tc | 09:11 | |
*** kumarmn has quit IRC | 09:16 | |
*** kumarmn has joined #openstack-tc | 09:45 | |
*** kumarmn has quit IRC | 09:50 | |
*** kumarmn has joined #openstack-tc | 10:20 | |
*** kumarmn has quit IRC | 10:25 | |
*** kumarmn has joined #openstack-tc | 10:53 | |
*** kumarmn has quit IRC | 10:58 | |
*** alex_xu has quit IRC | 11:08 | |
*** alex_xu has joined #openstack-tc | 11:09 | |
*** kumarmn has joined #openstack-tc | 11:39 | |
*** kumarmn has quit IRC | 11:44 | |
*** kumarmn has joined #openstack-tc | 12:04 | |
*** kumarmn has quit IRC | 12:10 | |
*** kumarmn has joined #openstack-tc | 13:04 | |
*** kumarmn has quit IRC | 13:09 | |
*** kumarmn has joined #openstack-tc | 13:10 | |
*** kumarmn has quit IRC | 13:15 | |
dhellmann | I've been thinking about the "communicating important ML threads" issue. What if we had a community "newspaper" and every team could contribute 1 article to it each week? Sort of like what thingee was doing with summarizing the ML, but with the work distributed. The work that some teams are already doing to provide weekly summaries would make a natural set of content. | 13:41 |
---|---|---|
*** kumarmn has joined #openstack-tc | 13:46 | |
*** kumarmn has quit IRC | 13:51 | |
*** kumarmn has joined #openstack-tc | 13:56 | |
*** alex_xu has quit IRC | 15:10 | |
*** alex_xu has joined #openstack-tc | 15:17 | |
*** kumarmn has quit IRC | 17:51 | |
*** kumarmn has joined #openstack-tc | 17:51 | |
*** kumarmn has quit IRC | 17:56 | |
*** notmyname has quit IRC | 18:03 | |
*** notmyname has joined #openstack-tc | 18:07 | |
fungi | well, the work on summarizing the ml was also supposed to be distributed, but few people actually submitted any entries on the crowdsourcing etherpad for it | 18:44 |
*** kumarmn has joined #openstack-tc | 19:10 | |
*** kumarmn has quit IRC | 19:17 | |
*** kumarmn has joined #openstack-tc | 19:19 | |
*** kumarmn has quit IRC | 19:25 | |
*** kumarmn has joined #openstack-tc | 20:15 | |
*** kumarmn has quit IRC | 20:20 | |
dhellmann | yes, I wonder if the TC more formally asks teams to do this, based on the popularity of the work being done by some of the other teams or subteams, if we would have better results. And then if we have a few folks willing to take those emails to the -dev list and either republish them to a blog or just post the links (maybe an RSS feed that works based on the ML archives?) if we could publish the results in some way that | 20:26 |
dhellmann | is easier for people to follow than trying to follow the full list | 20:26 |
dhellmann | alternatively we could just set up the mechanism to republish the work that is already being done and announce *that* and see if it encourages anyone else to start sending updates | 20:27 |
dhellmann | I wonder if just having a second mailing list like we did with the release announcements, where folks can subscribe as a digest, would do it | 20:42 |
dhellmann | we could then ask people sending these updates to cross-post to both lists | 20:42 |
*** kumarmn has joined #openstack-tc | 21:35 | |
*** kumarmn has quit IRC | 21:39 | |
*** kumarmn has joined #openstack-tc | 22:05 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!