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