| 1 | TOPICS SOUGHT FOR THE KERNEL AND MAINTAINER SUMMITS \r |
| 2 | \r |
| 3 | [Kernel] Sep 3, 2018 19:07 UTC (Mon) (corbet)\r |
| 4 | \r |
| 5 | o News link: https://lwn.net/Articles/764055\r |
| 6 | o Source link: \r |
| 7 | \r |
| 8 | \r |
| 9 | The annual Maintainer and Kernel Summits will be held in\r |
| 10 | Vancouver, BC on November 12 to 15, in conjunction with the\r |
| 11 | Linux Plumbers Conference. The program committee is looking\r |
| 12 | for topics for both summits; read on for details on how to\r |
| 13 | submit ideas and, perhaps, get an invitation to the Maintainer\r |
| 14 | Summit.\r |
| 15 | \r |
| 16 | From :\r |
| 17 | \r |
| 18 | "Theodore Y. Ts'o" <tytso-AT-mit.edu>\r |
| 19 | \r |
| 20 | To :\r |
| 21 | \r |
| 22 | linux-kernel-AT-vger.kernel.org, linux-fsdevel-AT-vger.kernel.-\r |
| 23 | org, linux-mm-AT-kvack.org, netdev-AT-vger.kernel.org,\r |
| 24 | linux-block-AT-vger.kernel.org\r |
| 25 | \r |
| 26 | Subject :\r |
| 27 | \r |
| 28 | Maintainer / Kernel Summit 2018 planning kick-off\r |
| 29 | \r |
| 30 | Date :\r |
| 31 | \r |
| 32 | Thu, 30 Aug 2018 17:35:17 -0400\r |
| 33 | \r |
| 34 | Message-ID :\r |
| 35 | \r |
| 36 | <20180830213517.GA19110@thunk.org>\r |
| 37 | \r |
| 38 | Archive-link :\r |
| 39 | \r |
| 40 | [1]Article\r |
| 41 | \r |
| 42 | [ Feel free to forward this to other Linux kernel mailing\r |
| 43 | lists as\r |
| 44 | \r |
| 45 | appropriate -- Ted ]\r |
| 46 | \r |
| 47 | This year, the Maintainer and Kernel Summit will be in\r |
| 48 | Vancouver,\r |
| 49 | \r |
| 50 | B.C., November 12th -- 15th. The Maintainer's summit will be\r |
| 51 | held on\r |
| 52 | \r |
| 53 | Monday, November 12th, in Vancouver, immediately before the\r |
| 54 | Linux\r |
| 55 | \r |
| 56 | Plumber's Conference (LPC) November 13th -- 15th.\r |
| 57 | \r |
| 58 | For the past few years, before 2017, we've scheduled mostly\r |
| 59 | management\r |
| 60 | \r |
| 61 | and development process issues on the first day. We then\r |
| 62 | opened up\r |
| 63 | \r |
| 64 | the second day of the Kernel Summit to all attendees of the\r |
| 65 | conference\r |
| 66 | \r |
| 67 | with which the Kernel Summit has been colocated, and called it\r |
| 68 | the\r |
| 69 | \r |
| 70 | "Open Technical Day". This is something that just made sense\r |
| 71 | in order\r |
| 72 | \r |
| 73 | to assure that all of the necessary people needed to discuss a\r |
| 74 | \r |
| 75 | particular technical issue could be in the room.\r |
| 76 | \r |
| 77 | Starting last year in Prague, we took the next logical step,\r |
| 78 | and split\r |
| 79 | \r |
| 80 | the Kernel Summit in two. The "Maintainer's Summit" is an\r |
| 81 | \r |
| 82 | invite-only, half-day event, where the primary focus will be\r |
| 83 | process\r |
| 84 | \r |
| 85 | issues of Linux Kernel Development. It will be limited to 30\r |
| 86 | invitees\r |
| 87 | \r |
| 88 | and a handful of sponsored attendees. This makes it smaller\r |
| 89 | than the\r |
| 90 | \r |
| 91 | first few kernel summits (which were limited to around 50\r |
| 92 | attendees).\r |
| 93 | \r |
| 94 | The "Kernel Summit" is now organized as a track which is run in\r |
| 95 | \r |
| 96 | parallel with the other tracks at the Linux Plumber's\r |
| 97 | Conference, and\r |
| 98 | \r |
| 99 | is open to all registered attendees of Plumbers. Much as how we\r |
| 100 | \r |
| 101 | organized the Kernel Summit "open technical day" in 2016 in\r |
| 102 | Santa Fe,\r |
| 103 | \r |
| 104 | the Kernel Summit schedule will be synchronized with the other\r |
| 105 | tracks\r |
| 106 | \r |
| 107 | at the Plumber's Conference, and it will be open to all\r |
| 108 | registered\r |
| 109 | \r |
| 110 | Plumber's attendees.\r |
| 111 | \r |
| 112 | Linus has suggested the following ten people as the core of\r |
| 113 | the people\r |
| 114 | \r |
| 115 | he would like invited to the Maintainer's Summit, which was\r |
| 116 | calculated\r |
| 117 | \r |
| 118 | from statistics from his git tree.\r |
| 119 | \r |
| 120 | David Miller\r |
| 121 | \r |
| 122 | Dave Airlie\r |
| 123 | \r |
| 124 | Greg KH\r |
| 125 | \r |
| 126 | Arnd Bergmann\r |
| 127 | \r |
| 128 | Ingo Molnar\r |
| 129 | \r |
| 130 | Mauro Carvalho Chehab\r |
| 131 | \r |
| 132 | Takashi Iwai\r |
| 133 | \r |
| 134 | Thomas Gleixner\r |
| 135 | \r |
| 136 | Andrew Morton\r |
| 137 | \r |
| 138 | Olof Johansson\r |
| 139 | \r |
| 140 | As we did last year, there will be a mini-program committee\r |
| 141 | that will\r |
| 142 | \r |
| 143 | be pick enough names to bring the total number of 30 for the\r |
| 144 | \r |
| 145 | Maintainer's Summit. That program committee will consist of\r |
| 146 | Arnd\r |
| 147 | \r |
| 148 | Bergmann, Thomas Gleixner, Greg KH, Paul McKenney, and Ted\r |
| 149 | Ts'o.\r |
| 150 | \r |
| 151 | We will use the rest of names on the list generated by Linus's\r |
| 152 | script\r |
| 153 | \r |
| 154 | as a starting point of people to be considered. People who\r |
| 155 | suggest\r |
| 156 | \r |
| 157 | topics that should be discussed on the Maintainer's summit\r |
| 158 | will also\r |
| 159 | \r |
| 160 | be added to the list. To make topic suggestions for the\r |
| 161 | Maintainer's\r |
| 162 | \r |
| 163 | Summit, please send e-mail to the ksummit-discuss list with a\r |
| 164 | subject\r |
| 165 | \r |
| 166 | prefix of [MAINTAINERS SUMMIT].\r |
| 167 | \r |
| 168 | The other job of the program committee will be to organize the\r |
| 169 | program\r |
| 170 | \r |
| 171 | for the Kernel Summit. The goal of the Kernel Summit track\r |
| 172 | will be to\r |
| 173 | \r |
| 174 | provide a forum to discuss specific technical issues that\r |
| 175 | would be\r |
| 176 | \r |
| 177 | easier to resolve in person than over e-mail. The program\r |
| 178 | committee\r |
| 179 | \r |
| 180 | will also consider "information sharing" topics if they are\r |
| 181 | clearly of\r |
| 182 | \r |
| 183 | interest to the wider development community (i.e., advanced\r |
| 184 | training\r |
| 185 | \r |
| 186 | in topics that would be useful to kernel developers).\r |
| 187 | \r |
| 188 | To suggest a topic for the Kernel Summit, please tag your\r |
| 189 | e-mail with\r |
| 190 | \r |
| 191 | [TECH TOPIC]. As before, please use a separate e-mail for each\r |
| 192 | topic,\r |
| 193 | \r |
| 194 | and send the topic suggestions to:\r |
| 195 | \r |
| 196 | ksummit-discuss@lists.linuxfoundation.org\r |
| 197 | \r |
| 198 | People who submit topic suggestions before September 21st and\r |
| 199 | which\r |
| 200 | \r |
| 201 | are accepted, will be given a free admission to the Linux\r |
| 202 | Plumbers\r |
| 203 | \r |
| 204 | Conference.\r |
| 205 | \r |
| 206 | We will reserving roughly half the Kernel Summit slots for\r |
| 207 | last-minute\r |
| 208 | \r |
| 209 | discussions that will be scheduled during the week of\r |
| 210 | Plumber's, in an\r |
| 211 | \r |
| 212 | "unconference style". This was extremely popular in Santa Fe\r |
| 213 | and in\r |
| 214 | \r |
| 215 | Prague, since it allowed ideas that came up in hallway\r |
| 216 | discussions,\r |
| 217 | \r |
| 218 | and in Plumber's Miniconference, to be given scheduled,\r |
| 219 | dedicated\r |
| 220 | \r |
| 221 | times for that discussion.\r |
| 222 | \r |
| 223 | If you were not subscribed on to the kernel-discuss mailing\r |
| 224 | list from\r |
| 225 | \r |
| 226 | last year (or if you had removed yourself after the kernel\r |
| 227 | summit),\r |
| 228 | \r |
| 229 | you can subscribe to the discuss list using mailman:\r |
| 230 | \r |
| 231 | https://lists.linuxfoundation.org/mailman/listinfo/ksummi...\r |
| 232 | \r |
| 233 | \r |
| 234 | \r |
| 235 | [1] https://lwn.net/ml/linux-kernel/20180830213517.GA19110@thu-\r |
| 236 | nk.org\r |
| 237 | \r |
| 238 | \r |
| 239 | \r |