1Getting Involved 2================ 3 4LLVM welcomes contributions of all kinds. To get started, please review the following topics: 5 6.. contents:: 7 :local: 8 9.. toctree:: 10 :hidden: 11 12 Contributing 13 DeveloperPolicy 14 CodeReview 15 SupportPolicy 16 SphinxQuickstartTemplate 17 Phabricator 18 HowToSubmitABug 19 BugLifeCycle 20 CodingStandards 21 GitHub 22 GitBisecting 23 GitRepositoryPolicy 24 25:doc:`Contributing` 26 An overview on how to contribute to LLVM. 27 28:doc:`DeveloperPolicy` 29 The LLVM project's policy towards developers and their contributions. 30 31:doc:`CodeReview` 32 The LLVM project's code-review process. 33 34:doc:`SupportPolicy` 35 The LLVM support policy for core and non-core components. 36 37:doc:`SphinxQuickstartTemplate` 38 A template + tutorial for writing new Sphinx documentation. It is meant 39 to be read in source form. 40 41:doc:`Phabricator` 42 Describes how to use the Phabricator code review tool hosted on 43 http://reviews.llvm.org/ and its command line interface, Arcanist. 44 45:doc:`HowToSubmitABug` 46 Instructions for properly submitting information about any bugs you run into 47 in the LLVM system. 48 49:doc:`BugLifeCycle` 50 Describes how bugs are reported, triaged and closed. 51 52:doc:`CodingStandards` 53 Details the LLVM coding standards and provides useful information on writing 54 efficient C++ code. 55 56:doc:`GitHub` 57 Describes how to use the llvm-project repository on GitHub. 58 59:doc:`GitBisecting` 60 Describes how to use ``git bisect`` on LLVM's repository. 61 62:doc:`GitRepositoryPolicy` 63 Collection of policies around the git repositories. 64 65.. _development-process: 66 67Development Process 68------------------- 69 70Information about LLVM's development process. 71 72.. toctree:: 73 :hidden: 74 75 Projects 76 HowToReleaseLLVM 77 Packaging 78 ReleaseProcess 79 HowToAddABuilder 80 ReleaseNotes 81 82:doc:`Projects` 83 How-to guide and templates for new projects that *use* the LLVM 84 infrastructure. The templates (directory organization, Makefiles, and test 85 tree) allow the project code to be located outside (or inside) the ``llvm/`` 86 tree, while using LLVM header files and libraries. 87 88:doc:`HowToReleaseLLVM` 89 This is a guide to preparing LLVM releases. Most developers can ignore it. 90 91:doc:`ReleaseProcess` 92 This is a guide to validate a new release, during the release process. Most developers can ignore it. 93 94:doc:`HowToAddABuilder` 95 Instructions for adding new builder to LLVM buildbot master. 96 97:doc:`Packaging` 98 Advice on packaging LLVM into a distribution. 99 100:doc:`Release notes for the current release <ReleaseNotes>` 101 This describes new features, known bugs, and other limitations. 102 103.. _lists-forums: 104 105Forums & Mailing Lists 106---------------------- 107 108If you can't find what you need in these docs, try consulting the 109Discourse forums. There are also commit mailing lists for all commits to the LLVM Project. 110The :doc:`CodeOfConduct` applies to all these forums and mailing lists. 111 112`LLVM Discourse`__ 113 The forums for all things LLVM and related sub-projects. There are categories and subcategories for a wide variety of areas within LLVM. You can also view tags or search for a specific topic. 114 115 .. __: https://discourse.llvm.org/ 116 117`Commits Archive (llvm-commits)`__ 118 This list contains all commit messages that are made when LLVM developers 119 commit code changes to the repository. It also serves as a forum for 120 patch review (i.e. send patches here). It is useful for those who want to 121 stay on the bleeding edge of LLVM development. This list is very high 122 volume. 123 124 .. __: http://lists.llvm.org/pipermail/llvm-commits/ 125 126`Bugs & Patches Archive (llvm-bugs)`__ 127 This list gets emailed every time a bug is opened and closed. It is 128 higher volume than the LLVM-dev list. 129 130 .. __: http://lists.llvm.org/pipermail/llvm-bugs/ 131 132`LLVM Announcements`__ 133 If you just want project wide announcements such as releases, developers meetings, or blog posts, then you should check out the Announcement category on LLVM Discourse. 134 135 .. __: https://discourse.llvm.org/c/announce/46 136 137.. _online-sync-ups: 138 139Online Sync-Ups 140--------------- 141 142A number of regular calls are organized on specific topics. It should be 143expected that the range of topics will change over time. At the time of 144writing, the following sync-ups are organized. 145The :doc:`CodeOfConduct` applies to all online sync-ups. 146 147If you'd like to organize a new sync-up, please add the info in the table 148below. Please also create a calendar event for it and invite calendar@llvm.org 149to the event, so that it'll show up on the :ref:`llvm-community-calendar`. 150Please see :ref:`llvm-community-calendar-host-guidance` for more guidance on 151what to add to your calendar invite. 152 153.. list-table:: LLVM regular sync-up calls 154 :widths: 25 25 25 25 155 :header-rows: 1 156 157 * - Topic 158 - Frequency 159 - Calendar link 160 - Minutes/docs link 161 * - Loop Optimization Working Group 162 - Every 2 weeks on Wednesday 163 - `ics <./_static/LoopOptWG_invite.ics>`__ 164 - `Minutes/docs <https://docs.google.com/document/d/1sdzoyB11s0ccTZ3fobqctDpgJmRoFcz0sviKxqczs4g/edit>`__ 165 * - RISC-V 166 - Every 2 weeks on Thursday 167 - `ics <https://calendar.google.com/calendar/ical/lowrisc.org_0n5pkesfjcnp0bh5hps1p0bd80%40group.calendar.google.com/public/basic.ics>`__ 168 `gcal <https://calendar.google.com/calendar/b/1?cid=bG93cmlzYy5vcmdfMG41cGtlc2ZqY25wMGJoNWhwczFwMGJkODBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ>`__ 169 - 170 * - Scalable Vectors and Arm SVE 171 - Monthly, every 3rd Tuesday 172 - `ics <https://calendar.google.com/calendar/ical/bjms39pe6k6bo5egtsp7don414%40group.calendar.google.com/public/basic.ics>`__ 173 `gcal <https://calendar.google.com/calendar/u/0/embed?src=bjms39pe6k6bo5egtsp7don414@group.calendar.google.com>`__ 174 - `Minutes/docs <https://docs.google.com/document/d/1UPH2Hzou5RgGT8XfO39OmVXKEibWPfdYLELSaHr3xzo/edit>`__ 175 * - ML Guided Compiler Optimizations 176 - Monthly 177 - 178 - `Minutes/docs <https://docs.google.com/document/d/1JecbplF09l3swTjze-UVeLh4L48svJxGVy4mz_e9Rhs/edit?usp=gmail#heading=h.ts9cmcjbir1j>`__ 179 * - `LLVM security group <https://llvm.org/docs/Security.html>`__ 180 - Monthly, every 3rd Tuesday 181 - `ics <https://calendar.google.com/calendar/ical/eoh3m9k1l6vqbd1fkp94fv5q74%40group.calendar.google.com/public/basic.ics>`__ 182 `gcal <https://calendar.google.com/calendar/embed?src=eoh3m9k1l6vqbd1fkp94fv5q74%40group.calendar.google.com>`__ 183 - `Minutes/docs <https://discourse.llvm.org/t/llvm-security-group-public-sync-ups/62735>`__ 184 * - `CIRCT <https://github.com/llvm/circt>`__ 185 - Weekly, on Wednesday 186 - 187 - `Minutes/docs <https://docs.google.com/document/d/1fOSRdyZR2w75D87yU2Ma9h2-_lEPL4NxvhJGJd-s5pk/edit#heading=h.mulvhjtr8dk9>`__ 188 * - `MLIR <https://mlir.llvm.org>`__ design meetings 189 - Weekly, on Thursdays 190 - 191 - `Minutes/docs <https://docs.google.com/document/d/1y_9f1AbfgcoVdJh4_aM6-BaSHvrHl8zuA5G4jv_94K8/edit#heading=h.cite1kolful9>`__ 192 * - flang 193 - Multiple meeting series, `documented here <https://github.com/llvm/llvm-project/blob/main/flang/docs/GettingInvolved.md#calls>`__ 194 - 195 - 196 * - OpenMP 197 - Multiple meeting series, `documented here <https://openmp.llvm.org/docs/SupportAndFAQ.html>`__ 198 - 199 - 200 * - LLVM Alias Analysis 201 - Every 4 weeks on Tuesdays 202 - `ics <http://lists.llvm.org/pipermail/llvm-dev/attachments/20201103/a3499a67/attachment-0001.ics>`__ 203 - `Minutes/docs <https://docs.google.com/document/d/17U-WvX8qyKc3S36YUKr3xfF-GHunWyYowXbxEdpHscw>`__ 204 * - Vector Predication 205 - Every 2 weeks on Tuesdays, 3pm UTC 206 - 207 - `Minutes/docs <https://docs.google.com/document/d/1q26ToudQjnqN5x31zk8zgq_s0lem1-BF8pQmciLa4k8/edit?usp=sharing>`__ 208 * - LLVM Pointer Authentication 209 - Every month on Mondays 210 - `ics <https://calendar.google.com/calendar/ical/fr1qtmrmt2s9odufjvurkb6j70%40group.calendar.google.com/public/basic.ics>`__ 211 - `Minutes/docs <https://discourse.llvm.org/t/llvm-pointer-authentication-sync-ups/62661>`__ 212 * - MemorySSA in LLVM 213 - Every 8 weeks on Mondays 214 - `ics <https://calendar.google.com/calendar/ical/c_1mincouiltpa24ac14of14lhi4%40group.calendar.google.com/public/basic.ics>`__ 215 `gcal <https://calendar.google.com/calendar/embed?src=c_1mincouiltpa24ac14of14lhi4%40group.calendar.google.com>`__ 216 - `Minutes/docs <https://docs.google.com/document/d/1-uEEZfmRdPThZlctOq9eXlmUaSSAAi8oKxhrPY_lpjk/edit#>`__ 217 * - LLVM Embedded Toolchains 218 - Every 4 weeks on Thursdays 219 - `ics <https://drive.google.com/file/d/1uNa-PFYkhAfT83kR2Nc4Fi706TAQFBEL/view?usp=sharing>`__ 220 `gcal <https://calendar.google.com/calendar/u/0?cid=ZDQyc3ZlajJmbjIzNG1jaTUybjFsdjA2dWNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ>`__ 221 - `Minutes/docs <https://docs.google.com/document/d/1GahxppHJ7o1O_fn1Mbidu1DHEg7V2aOr92LXCtNV1_o/edit?usp=sharing>`__ 222 * - Clang C and C++ Language Working Group 223 - 1st and 3rd Wednesday of the month 224 - `gcal <https://calendar.google.com/calendar/u/0?cid=cW1lZGg0ZXNpMnIyZDN2aTVydGVrdWF1YzRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ>`__ 225 - `Minutes/docs <https://docs.google.com/document/d/1x5-RbOC6-jnI_NcJ9Dp4pSmGhhNe7lUevuWUIB46TeM/edit?usp=sharing>`__ 226 * - LLVM SPIR-V Backend Working Group 227 - Every week on Thursday 228 - 229 - `Meeting details/agenda <https://docs.google.com/document/d/1UjX-LAwPjJ75Nmb8a5jz-Qrm-pPtKtQw0k1S1Lop9jU/edit?usp=sharing>`__ 230 * - SYCL Upstream Working Group 231 - Every 2 weeks on Mondays 232 - `gcal <https://calendar.google.com/calendar/u/0?cid=c3ljbC5sbHZtLndnQGdtYWlsLmNvbQ>`__ 233 - `Meeting details/agenda <https://docs.google.com/document/d/1ivYDSn_5ChTeiZ7TiO64WC_jYJnGwAUiT9Ngi9cAdFU/edit?usp=sharing>`__ 234 235.. _office-hours: 236 237Office hours 238------------ 239 240A number of experienced LLVM contributors make themselves available for a chat 241on a regular schedule, to anyone who is looking for some guidance. Please find 242the list of who is available when, through which medium, and what their area of 243expertise is. Don't be too shy to dial in! 244 245The :doc:`CodeOfConduct` applies to all office hours. 246 247Of course, people take time off from time to time, so if you dial in and you 248don't find anyone present, chances are they happen to be off that day. 249 250.. list-table:: LLVM office hours 251 :widths: 15 40 15 15 15 252 :header-rows: 1 253 254 * - Name 255 - In-scope topics 256 - When? 257 - Where? 258 - Languages 259 * - Kristof Beyls 260 - General questions on how to contribute to LLVM; organizing meetups; 261 submitting talks; and other general LLVM-related topics. Arm/AArch64 262 codegen. LLVM security group. LLVM Office Hours. 263 - Every 2nd and 4th Wednesday of the month at 9.30am CET, for 30 minutes. 264 `ics <https://calendar.google.com/calendar/ical/co0h4ndpvtfe64opn7eraiq3ac%40group.calendar.google.com/public/basic.ics>`__ 265 - `Jitsi <https://meet.jit.si/KristofBeylsLLVMOfficeHour>`__ 266 - English, Flemish, Dutch 267 * - Alina Sbirlea 268 - General questions on how to contribute to LLVM; women in compilers; 269 MemorySSA, BatchAA, various loop passes, new pass manager. 270 - Monthly, 2nd Tuesdays, 10.00am PT/7:00pm CET, for 30 minutes. 271 `ics <https://calendar.google.com/calendar/ical/c_pm6e7160iq7n5fcm1s6m3rjhh4%40group.calendar.google.com/public/basic.ics>`__ 272 `gcal <https://calendar.google.com/calendar/embed?src=c_pm6e7160iq7n5fcm1s6m3rjhh4%40group.calendar.google.com>`__ 273 - `GoogleMeet <https://meet.google.com/hhk-xpdj-gvx>`__ 274 - English, Romanian 275 * - Aaron Ballman (he/him) 276 - Clang internals; frontend attributes; clang-tidy; clang-query; AST matchers 277 - Monthly, 2nd Monday of the month at 10:00am Eastern and again at 2:00pm Eastern, for 30 minutes (will run longer as needed). 278 `ics <https://calendar.google.com/calendar/ical/npgke5dug0uliud0qapptmps58%40group.calendar.google.com/public/basic.ics>`__ 279 `gcal <https://calendar.google.com/calendar/embed?src=npgke5dug0uliud0qapptmps58%40group.calendar.google.com>`__ 280 - `GoogleMeet <https://meet.google.com/xok-iqne-gmi>`__ 281 - English, Norwegian (not fluently) 282 * - Johannes Doerfert (he/him) 283 - OpenMP, LLVM-IR, interprocedural optimizations, Attributor, workshops, research, ... 284 - Every week, Wednesdays 9:30am (Pacific Time), for 1 hour. 285 `ics <https://drive.google.com/file/d/1E_QkRvirmdJzlXf2EKBUX-v8Xj7-eW3v/view?usp=sharing>`__ 286 - `MS Teams <https://teams.microsoft.com/l/meetup-join/19%3ameeting_MTMxNzU4MWYtYzViNS00OTM2LWJmNWQtMjg5ZWFhNGVjNzgw%40thread.v2/0?context=%7b%22Tid%22%3a%22a722dec9-ae4e-4ae3-9d75-fd66e2680a63%22%2c%22Oid%22%3a%22885bda30-ce8e-46db-aa7e-15de0474831a%22%7d>`__ 287 - English, German 288 * - Tobias Grosser 289 - General questions on how to contribute to LLVM/MLIR, Polly, Loop Optimization, FPL, Research in LLVM, PhD in CS, Summer of Code. 290 - Monthly, last Monday of the month at 18:00 London time (typically 9am PT), for 30 minutes. 291 - `Video Call <https://meet.grosser.science/LLVMOfficeHours>`__ 292 - English, German, Spanish, French 293 * - Anastasia Stulova 294 - Clang internals for C/C++ language extensions and dialects, OpenCL, GPU, SPIR-V, how to contribute, women in compilers. 295 - Monthly, 2nd Thursday of the month at 17:00 BST - London time (9:00am PT except for 2 weeks in spring), 1 hour slot. 296 - `GoogleMeet <https://meet.google.com/kdy-fdbv-nuk>`__ 297 - English, Russian, German (not fluently) 298 * - Alexey Bader 299 - SYCL compiler, offload tools, OpenCL and SPIR-V, how to contribute. 300 - Monthly, 2nd Monday of the month at 9:30am PT, for 30 minutes. 301 - `GoogleMeet <https://meet.google.com/pdz-xhns-uus>`__ 302 - English, Russian 303 * - Maksim Panchenko 304 - BOLT internals, IR, new passes, proposals, etc. 305 - Monthly, 2nd Wednesday of the month at 11:00am PT, for 30 minutes. 306 - `Zoom <https://fb.zoom.us/j/97065697120?pwd=NTFaUWJjZW9uVkJuaVlPTE9qclE3dz09>`__ 307 - English, Russian 308 * - Michal Paszkowski 309 - SPIR-V backend, IGC, OpenCL, and IR transformations 310 - Monthly, 3rd Thursday of the month at 21:00 Warsaw/Poland time, 1 hour slot. 311 - `MS Teams <https://teams.microsoft.com/l/meetup-join/19%3ameeting_ODRmN2UwYTgtODdiOS00N2VkLTgxZjgtNDUxYjI3YmNkM2Ri%40thread.v2/0?context=%7b%22Tid%22%3a%2246c98d88-e344-4ed4-8496-4ed7712e255d%22%2c%22Oid%22%3a%220c2b140d-8412-4963-a118-0f7534426b65%22%7d>`__ 312 - English, Polish 313 * - Quentin Colombet (he/him) 314 - LLVM/MLIR; Codegen (Instruction selection (GlobalISel/SDISel), Machine IR, 315 Register allocation, etc.); Optimizations; MCA 316 - Monthly, 1st Wednesday of the month at 8.00am PT, for 30 minutes. 317 `ics <https://calendar.google.com/calendar/ical/48c4ad60290a4df218e51e1ceec1106fe317b0ebc76938d9273592053f38204e%40group.calendar.google.com/public/basic.ics>`__ 318 `gcal <https://calendar.google.com/calendar/embed?src=48c4ad60290a4df218e51e1ceec1106fe317b0ebc76938d9273592053f38204e%40group.calendar.google.com>`__ 319 - `Google meet <https://meet.google.com/cbz-grrp-obs>`__ 320 - English, French 321 * - Paulo Matos (he/him) 322 - WebAssembly backend; LLVM IR; 323 - Monthly, 1st Monday of the month at 11:00am Europe/Berlin, for 30 minutes. 324 - `Igalia Jitsi <https://meetings.igalia.com/PauloMatosLLVMOfficeHour>`__ 325 - English, Portuguese, German 326 * - Phoebe Wang (she/her) 327 - X86 backend, General questions to X86, women in compilers. 328 - Monthly, 3rd Wednesday of the month at 8:30am Beijing time, for 30 minutes. 329 - `MS Teams <https://teams.microsoft.com/l/meetup-join/19%3ameeting_NWQ0MjU0NjYtZjUyMi00YTU3LThmM2EtY2Y2YTE4NGM3NmFi%40thread.v2/0?context=%7b%22Tid%22%3a%2246c98d88-e344-4ed4-8496-4ed7712e255d%22%2c%22Oid%22%3a%227b309d9c-a9bb-44c8-a940-ab97eef42d4d%22%7d>`__ 330 - English, Chinese 331 332 333Guidance for office hours hosts 334^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 335 336* If you're interested in becoming an office hours host, please add your 337 information to the list above. Please create a calendar event for it and 338 invite calendar@llvm.org to the event so that it'll show up on the 339 :ref:`llvm-community-calendar`. 340 Please see :ref:`llvm-community-calendar-host-guidance` for more guidance on 341 what to add to your calendar invite. 342* When starting an office hours session, consider typing something like "*Hi, 343 I'm available for chats in the next half hour at* video chat URL. *I'm 344 looking forward to having conversations on the video chat or here.*" on the 345 LLVM chat channels that you are already on. These could include: 346 347 * the `#office-hours Discord channel 348 <https://discord.com/channels/636084430946959380/976196303681896538>`__. 349 * :ref:`IRC` 350 351 Doing this can help: 352 * overcome potential anxiety to call in for a first time, 353 * people who prefer to first exchange a few messages through text chat 354 before dialing in, and 355 * remind the wider community that office hours do exist. 356* If you decide to no longer host office hours, please do remove your entry 357 from the list above. 358 359 360.. _IRC: 361 362IRC 363--- 364 365Users and developers of the LLVM project (including subprojects such as Clang) 366can be found in #llvm on `irc.oftc.net <irc://irc.oftc.net/llvm>`_. The channel 367is actively moderated. 368 369The #llvm-build channel has a bot for 370`LLVM buildbot <http://lab.llvm.org/buildbot/#/console>`_ status changes. The 371bot will post a message with a link to a build bot and a blamelist when a build 372goes from passing to failing and again (without the blamelist) when the build 373goes from failing back to passing. It is a good channel for actively monitoring 374build statuses, but it is a noisy channel due to the automated messages. The 375channel is not actively moderated. 376 377In addition to the traditional IRC there is a 378`Discord <https://discord.com/channels/636084430946959380/636725486533345280>`_ 379chat server available. To sign up, please use this 380`invitation link <https://discord.com/invite/xS7Z362>`_. 381 382 383.. _meetups-social-events: 384 385Meetups and social events 386------------------------- 387 388.. toctree:: 389 :hidden: 390 391 MeetupGuidelines 392 393Besides developer `meetings and conferences <https://llvm.org/devmtg/>`_, 394there are several user groups called 395`LLVM Socials <https://www.meetup.com/pro/llvm/>`_. We greatly encourage you to 396join one in your city. Or start a new one if there is none: 397 398:doc:`MeetupGuidelines` 399 400.. _community-proposals: 401 402Community wide proposals 403------------------------ 404 405Proposals for massive changes in how the community behaves and how the work flow 406can be better. 407 408.. toctree:: 409 :hidden: 410 411 Proposals/GitHubMove 412 BugpointRedesign 413 Proposals/TestSuite 414 Proposals/VariableNames 415 Proposals/VectorizationPlan 416 Proposals/VectorPredication 417 418:doc:`Proposals/GitHubMove` 419 Proposal to move from SVN/Git to GitHub. 420 421:doc:`BugpointRedesign` 422 Design doc for a redesign of the Bugpoint tool. 423 424:doc:`Proposals/TestSuite` 425 Proposals for additional benchmarks/programs for llvm's test-suite. 426 427:doc:`Proposals/VariableNames` 428 Proposal to change the variable names coding standard. 429 430:doc:`Proposals/VectorizationPlan` 431 Proposal to model the process and upgrade the infrastructure of LLVM's Loop Vectorizer. 432 433:doc:`Proposals/VectorPredication` 434 Proposal for predicated vector instructions in LLVM. 435 436.. _llvm-community-calendar: 437 438LLVM community calendar 439----------------------- 440 441We aim to maintain a public calendar view of all events happening in the LLVM 442community such as :ref:`online-sync-ups` and :ref:`office-hours`. The calendar 443can be found at 444https://calendar.google.com/calendar/u/0/embed?src=calendar@llvm.org and can 445also be seen inline below: 446 447.. raw:: html 448 449 <iframe src="https://calendar.google.com/calendar/embed?height=600&wkst=1&bgcolor=%23ffffff&ctz=UTC&showCalendars=0&showDate=1&showNav=1&src=Y2FsZW5kYXJAbGx2bS5vcmc&color=%23039BE5" style="border:solid 1px #777" width="800" height="600" frameborder="0" scrolling="no"></iframe> 450 451.. _llvm-community-calendar-host-guidance: 452 453Guidance on what to put into LLVM community calendar invites 454^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 455 456To add your event, create a calendar event for it and invite calendar@llvm.org 457on it. Your event should then show up on the community calendar. 458 459Please put the following pieces of information in your calendar invite: 460 461* Write a single paragraph describing what the event is about. Include things 462 such as who the event is for and what sort of topics are discussed. 463* State explicitly that the :doc:`CodeOfConduct` applies to this event. 464* Make it clear who: 465 466 * the organizer is. 467 468 * the person to contact is in case of any code-of-conduct issues. Typically, 469 this would be the organizer. 470 471* If you have meeting minutes for your event, add a pointer to where those live. 472 A good place for meeting minutes could be as a post on LLVM Discourse. 473 474An example invite looks as follows 475 476.. code-block:: none 477 478 This event is a meetup for all developers of LLDB. Meeting agendas are posted 479 on discourse before the event. 480 481 Attendees are required to adhere to the LLVM Code of Conduct 482 (https://llvm.org/docs/CodeOfConduct.html). For any Code of Conduct reports, 483 please contact the organizers, and also email conduct@llvm.org. 484 485 Agenda/Meeting Minutes: Link to minutes 486 487 Organizer(s): First Surname (name@email.com) 488 489