-
Notifications
You must be signed in to change notification settings - Fork 3
/
governance.html
734 lines (551 loc) · 27.9 KB
/
governance.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
<!DOCTYPE html>
<html lang="en" data-content_root="./" >
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Geomstats governance and decision-making — Geomstats latest documentation</title>
<script data-cfasync="false">
document.documentElement.dataset.mode = localStorage.getItem("mode") || "";
document.documentElement.dataset.theme = localStorage.getItem("theme") || "";
</script>
<!--
this give us a css class that will be invisible only if js is disabled
-->
<noscript>
<style>
.pst-js-only { display: none !important; }
</style>
</noscript>
<!-- Loaded before other Sphinx assets -->
<link href="_static/styles/theme.css?digest=26a4bc78f4c0ddb94549" rel="stylesheet" />
<link href="_static/styles/pydata-sphinx-theme.css?digest=26a4bc78f4c0ddb94549" rel="stylesheet" />
<link rel="stylesheet" type="text/css" href="_static/pygments.css?v=a746c00c" />
<link rel="stylesheet" type="text/css" href="_static/sg_gallery.css?v=d2d258e8" />
<!-- So that users can add custom icons -->
<script src="_static/scripts/fontawesome.js?digest=26a4bc78f4c0ddb94549"></script>
<!-- Pre-loaded scripts that we'll load fully later -->
<link rel="preload" as="script" href="_static/scripts/bootstrap.js?digest=26a4bc78f4c0ddb94549" />
<link rel="preload" as="script" href="_static/scripts/pydata-sphinx-theme.js?digest=26a4bc78f4c0ddb94549" />
<script src="_static/documentation_options.js?v=c6e86fd7"></script>
<script src="_static/doctools.js?v=9bcbadda"></script>
<script src="_static/sphinx_highlight.js?v=dc90522c"></script>
<script crossorigin="anonymous" integrity="sha256-Ae2Vz/4ePdIu6ZyI/5ZGsYnb+m0JlOmKPjt6XZ9JJkA=" src="https://cdnjs.cloudflare.com/ajax/libs/require.js/2.3.4/require.min.js"></script>
<script>DOCUMENTATION_OPTIONS.pagename = 'governance';</script>
<link rel="canonical" href="geomstats.github.io/governance.html" />
<link rel="index" title="Index" href="genindex.html" />
<link rel="search" title="Search" href="search.html" />
<link rel="next" title="Google Season of Docs: Case Study" href="gsod.html" />
<link rel="prev" title="Roadmap" href="roadmap.html" />
<meta name="viewport" content="width=device-width, initial-scale=1"/>
<meta name="docsearch:language" content="en"/>
<meta name="docsearch:version" content="latest" />
<meta name="docbuild:last-update" content="Dec 5, 2024, 6:23:57 PM"/>
</head>
<body data-bs-spy="scroll" data-bs-target=".bd-toc-nav" data-offset="180" data-bs-root-margin="0px 0px -60%" data-default-mode="">
<div id="pst-skip-link" class="skip-link d-print-none"><a href="#main-content">Skip to main content</a></div>
<div id="pst-scroll-pixel-helper"></div>
<button type="button" class="btn rounded-pill" id="pst-back-to-top">
<i class="fa-solid fa-arrow-up"></i>Back to top</button>
<dialog id="pst-search-dialog">
<form class="bd-search d-flex align-items-center"
action="search.html"
method="get">
<i class="fa-solid fa-magnifying-glass"></i>
<input type="search"
class="form-control"
name="q"
placeholder="Search the docs ..."
aria-label="Search the docs ..."
autocomplete="off"
autocorrect="off"
autocapitalize="off"
spellcheck="false"/>
<span class="search-button__kbd-shortcut"><kbd class="kbd-shortcut__modifier">Ctrl</kbd>+<kbd>K</kbd></span>
</form>
</dialog>
<div class="pst-async-banner-revealer d-none">
<aside id="bd-header-version-warning" class="d-none d-print-none" aria-label="Version warning"></aside>
</div>
<header class="bd-header navbar navbar-expand-lg bd-navbar d-print-none">
<div class="bd-header__inner bd-page-width">
<button class="pst-navbar-icon sidebar-toggle primary-toggle" aria-label="Site navigation">
<span class="fa-solid fa-bars"></span>
</button>
<div class="col-lg-3 navbar-header-items__start">
<div class="navbar-item">
<a class="navbar-brand logo" href="index.html">
<p class="title logo__title">Geomstats latest documentation</p>
</a></div>
</div>
<div class="col-lg-9 navbar-header-items">
<div class="me-auto navbar-header-items__center">
<div class="navbar-item">
<nav>
<ul class="bd-navbar-elements navbar-nav">
<li class="nav-item ">
<a class="nav-link nav-internal" href="getting_started/index.html">
Getting Started
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="explanation/index.html">
Explanation
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="tutorials/index.html">
Tutorials
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="contributing/index.html">
Contributing Guide
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="api/index.html">
API Reference
</a>
</li>
<li class="nav-item dropdown">
<button class="btn dropdown-toggle nav-item" type="button" data-bs-toggle="dropdown" aria-expanded="false" aria-controls="pst-nav-more-links">
More
</button>
<ul id="pst-nav-more-links" class="dropdown-menu">
<li class=" ">
<a class="nav-link dropdown-item nav-internal" href="roadmap.html">
Roadmap
</a>
</li>
<li class=" current active">
<a class="nav-link dropdown-item nav-internal" href="#">
Governance
</a>
</li>
<li class=" ">
<a class="nav-link dropdown-item nav-internal" href="gsod.html">
Google Season of Docs
</a>
</li>
<li class=" ">
<a class="nav-link dropdown-item nav-internal" href="hackathons.html">
Hackathons
</a>
</li>
</ul>
</li>
</ul>
</nav></div>
</div>
<div class="navbar-header-items__end">
<div class="navbar-item navbar-persistent--container">
<button class="btn search-button-field search-button__button pst-js-only" title="Search" aria-label="Search" data-bs-placement="bottom" data-bs-toggle="tooltip">
<i class="fa-solid fa-magnifying-glass"></i>
<span class="search-button__default-text">Search</span>
<span class="search-button__kbd-shortcut"><kbd class="kbd-shortcut__modifier">Ctrl</kbd>+<kbd class="kbd-shortcut__modifier">K</kbd></span>
</button>
</div>
<div class="navbar-item">
<button class="btn btn-sm nav-link pst-navbar-icon theme-switch-button pst-js-only" aria-label="Color mode" data-bs-title="Color mode" data-bs-placement="bottom" data-bs-toggle="tooltip">
<i class="theme-switch fa-solid fa-sun fa-lg" data-mode="light" title="Light"></i>
<i class="theme-switch fa-solid fa-moon fa-lg" data-mode="dark" title="Dark"></i>
<i class="theme-switch fa-solid fa-circle-half-stroke fa-lg" data-mode="auto" title="System Settings"></i>
</button></div>
</div>
</div>
<div class="navbar-persistent--mobile">
<button class="btn search-button-field search-button__button pst-js-only" title="Search" aria-label="Search" data-bs-placement="bottom" data-bs-toggle="tooltip">
<i class="fa-solid fa-magnifying-glass"></i>
<span class="search-button__default-text">Search</span>
<span class="search-button__kbd-shortcut"><kbd class="kbd-shortcut__modifier">Ctrl</kbd>+<kbd class="kbd-shortcut__modifier">K</kbd></span>
</button>
</div>
<button class="pst-navbar-icon sidebar-toggle secondary-toggle" aria-label="On this page">
<span class="fa-solid fa-outdent"></span>
</button>
</div>
</header>
<div class="bd-container">
<div class="bd-container__inner bd-page-width">
<dialog id="pst-primary-sidebar-modal"></dialog>
<div id="pst-primary-sidebar" class="bd-sidebar-primary bd-sidebar">
<div class="sidebar-header-items sidebar-primary__section">
<div class="sidebar-header-items__center">
<div class="navbar-item">
<nav>
<ul class="bd-navbar-elements navbar-nav">
<li class="nav-item ">
<a class="nav-link nav-internal" href="getting_started/index.html">
Getting Started
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="explanation/index.html">
Explanation
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="tutorials/index.html">
Tutorials
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="contributing/index.html">
Contributing Guide
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="api/index.html">
API Reference
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="roadmap.html">
Roadmap
</a>
</li>
<li class="nav-item current active">
<a class="nav-link nav-internal" href="#">
Governance
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="gsod.html">
Google Season of Docs
</a>
</li>
<li class="nav-item ">
<a class="nav-link nav-internal" href="hackathons.html">
Hackathons
</a>
</li>
</ul>
</nav></div>
</div>
<div class="sidebar-header-items__end">
<div class="navbar-item">
<button class="btn btn-sm nav-link pst-navbar-icon theme-switch-button pst-js-only" aria-label="Color mode" data-bs-title="Color mode" data-bs-placement="bottom" data-bs-toggle="tooltip">
<i class="theme-switch fa-solid fa-sun fa-lg" data-mode="light" title="Light"></i>
<i class="theme-switch fa-solid fa-moon fa-lg" data-mode="dark" title="Dark"></i>
<i class="theme-switch fa-solid fa-circle-half-stroke fa-lg" data-mode="auto" title="System Settings"></i>
</button></div>
</div>
</div>
<div class="sidebar-primary-items__start sidebar-primary__section">
<div class="sidebar-primary-item">
<nav class="bd-docs-nav bd-links"
aria-label="Section Navigation">
<p class="bd-links__title" role="heading" aria-level="1">Section Navigation</p>
<div class="bd-toc-item navbar-nav"></div>
</nav></div>
</div>
<div class="sidebar-primary-items__end sidebar-primary__section">
</div>
<div id="rtd-footer-container"></div>
</div>
<main id="main-content" class="bd-main" role="main">
<div class="bd-content">
<div class="bd-article-container">
<div class="bd-header-article d-print-none">
<div class="header-article-items header-article__inner">
<div class="header-article-items__start">
<div class="header-article-item">
<nav aria-label="Breadcrumb" class="d-print-none">
<ul class="bd-breadcrumbs">
<li class="breadcrumb-item breadcrumb-home">
<a href="index.html" class="nav-link" aria-label="Home">
<i class="fa-solid fa-home"></i>
</a>
</li>
<li class="breadcrumb-item active" aria-current="page"><span class="ellipsis">Geomstats governance and decision-making</span></li>
</ul>
</nav>
</div>
</div>
</div>
</div>
<div id="searchbox"></div>
<article class="bd-article">
<section id="geomstats-governance-and-decision-making">
<span id="governance"></span><h1>Geomstats governance and decision-making<a class="headerlink" href="#geomstats-governance-and-decision-making" title="Link to this heading">#</a></h1>
<p>This document formalizes the governance process used by the
geomstats project, to clarify how decisions are made and how
elements of our community interact.</p>
<p>This document establishes a decision-making structure that takes into account
feedback from all members of the community and strives to find consensus, while
avoiding any deadlocks.</p>
<p>Geomstats is a meritocratic, consensus-based community project. Anyone with an
interest in the project can join the community, contribute to the project
design and participate in the decision making process. This document describes
how that participation takes place and how to earn merit within
the project community.</p>
<p>This document is inspired by Scikit-Learn’s and Pandas’ governance documents.</p>
<section id="roles-and-responsibilities">
<h2>Roles And Responsibilities<a class="headerlink" href="#roles-and-responsibilities" title="Link to this heading">#</a></h2>
<section id="contributors">
<h3>Contributors<a class="headerlink" href="#contributors" title="Link to this heading">#</a></h3>
<p>Contributors are community members who contribute in concrete ways to the
project. Anyone can become a contributor, and contributions can take many forms
- not only code - as detailed in the <a class="reference external" href="https://geomstats.github.io/contributing/index.html#contributing">contributors guide</a>.</p>
</section>
<section id="contributor-experience-team">
<h3>Contributor Experience Team<a class="headerlink" href="#contributor-experience-team" title="Link to this heading">#</a></h3>
<p>The contributor experience team is composed of community members who have permission on
github to label and close issues. Their work is
crucial to improve the communication in the project and limit the crowding
of the issue tracker.</p>
<p>Similarly to what has been decided in the <a class="reference external" href="https://devguide.python.org/triaging/#becoming-a-member-of-the-python-triage-team">python project</a>,
any contributor may become a member of the geomstats contributor experience team,
after showing some continuity in participating to geomstats
development (with pull requests, reviews and help on issues).
Any core developer or member of the contributor experience team is welcome to propose a
geomstats contributor to join the contributor experience team. Other core developers
are then consulted: while it is expected that most acceptances will be
unanimous, a two-thirds majority is enough.
Every new member of the contributor experience team will be announced in Geomstats GoogleGroups mailing
list. Members of the team are welcome to participate in <a class="reference external" href="https://github.com/geomstats/admin/blob/main/meeting_notes.md">monthly core developer meetings</a>.</p>
<p>The contributor experience team is currently constituted of:</p>
<blockquote>
<div><ul class="simple">
<li><p>Luis Pereira,</p></li>
<li><p>Nina Miolane.</p></li>
</ul>
</div></blockquote>
</section>
<section id="communication-team">
<span id="id1"></span><h3>Communication team<a class="headerlink" href="#communication-team" title="Link to this heading">#</a></h3>
<p>Members of the communication team help with outreach and communication
for Geomstats. The goal of the team is to develop public awareness of
Geomstats, of its features and usage, as well as branding.</p>
<p>For this, they can operate the Geomstats accounts on various social
networks and produce materials.</p>
<p>Every new communicator will be announced in Geomstats GoogleGroups mailing list.
Communicators are welcome to participate in <a class="reference external" href="https://github.com/geomstats/admin/blob/main/meeting_notes.md">monthly core developer meetings</a>.</p>
<p>The communication team is currently constituted of:</p>
<blockquote>
<div><ul class="simple">
<li><p>Nina Miolane.</p></li>
</ul>
</div></blockquote>
</section>
<section id="core-developers">
<h3>Core developers<a class="headerlink" href="#core-developers" title="Link to this heading">#</a></h3>
<p>Core developers are community members who have shown that they are dedicated to
the continued development of the project through ongoing engagement with the
community. They have shown they can be trusted to maintain Geomstats with
care. Being a core developer allows contributors to more easily carry on
with their project related activities by giving them direct access to the
project’s repository.</p>
<p>Core developers are expected to review code
contributions, can merge approved pull requests, can cast votes for and against
merging a pull-request, and can be involved in deciding major changes to the
API.</p>
<p>New core developers can be nominated by any existing core developers. Once they
have been nominated, there will be a vote by the current core developers.
Voting on new core developers is one of the few activities that takes place on
the project’s private management list. While it is expected that most votes
will be unanimous, a two-thirds majority of the cast votes is enough. The vote
needs to be open for at least 1 week.</p>
<p>Core developers that have not contributed to the project (commits or GitHub
comments) in the past 12 months will be asked if they want to become emeritus
core developers and recant their commit and voting rights until they become
active again. The list of core developers, active and emeritus (with dates at
which they became active) will be public on the Geomstats website.</p>
<p>The core developers are currently:</p>
<blockquote>
<div><ul class="simple">
<li><p>Luis Pereira,</p></li>
<li><p>Nicolas Guigui,</p></li>
<li><p>Alice Le Brigant,</p></li>
<li><p>Jules Deschamps,</p></li>
<li><p>Saiteja Utpala,</p></li>
<li><p>Adele Myers,</p></li>
<li><p>Anna Calissano,</p></li>
<li><p>Yann Thanwerdas,</p></li>
<li><p>Elodie Maignant,</p></li>
<li><p>Tom Szwagier,</p></li>
<li><p>Nina Miolane.</p></li>
</ul>
</div></blockquote>
</section>
<section id="technical-committee">
<h3>Technical Committee<a class="headerlink" href="#technical-committee" title="Link to this heading">#</a></h3>
<p>The Technical Committee (TC) members are core developers who have additional
responsibilities to ensure the smooth running of the project. TC members are expected to
participate in strategic planning, and approve changes to the governance model.
The purpose of the TC is to ensure a smooth progress from the big-picture
perspective. Indeed changes that impact the full project require a synthetic
analysis and a consensus that is both explicit and informed. In cases that the
core developer community (which includes the TC members) fails to reach such a
consensus in the required time frame, the TC is the entity to resolve the
issue.
Membership of the TC is by nomination by a core developer. A nomination will
result in discussion which cannot take more than a month and then a vote by
the core developers which will stay open for a week. TC membership votes are
subject to a two-third majority of all cast votes as well as a simple majority
approval of all the current TC members. TC members who do not actively engage
with the TC duties are expected to resign.</p>
<p>The Technical Committee of Geomstats currently consists of:</p>
<blockquote>
<div><ul class="simple">
<li><p>Nina Miolane,</p></li>
<li><p>Alice Le Brigant,</p></li>
<li><p>Xavier Pennec.</p></li>
</ul>
</div></blockquote>
</section>
</section>
<section id="decision-making-process">
<h2>Decision Making Process<a class="headerlink" href="#decision-making-process" title="Link to this heading">#</a></h2>
<p>Decisions about the future of the project are made through discussion with all
members of the community. All non-sensitive project management discussion takes
place at the project’s monthly meetings and follow-up emails,
and the <a class="reference external" href="https://github.com/geomstats/geomstats/issues">issue tracker</a>.
Occasionally, sensitive discussion occurs on a private list.</p>
<p>Geomstats uses a “consensus seeking” process for making decisions. The group
tries to find a resolution that has no open objections among core developers.
At any point during the discussion, any core-developer can call for a vote, which will
conclude one month from the call for the vote. If no option can gather two thirds of the votes cast, the
decision is escalated to the TC, which in turn will use consensus seeking with
the fallback option of a simple majority vote if no consensus can be found
within a month. This is what we hereafter may refer to as “the decision making
process”.</p>
<p>Decisions (in addition to adding core developers and TC membership as above)
are made according to the following rules:</p>
<ul class="simple">
<li><p><strong>Minor Documentation changes</strong>, such as typo fixes, or addition / correction of a
sentence, but no change of the geomstats.ai landing page or the “about”
page: Requires +1 by a core developer, no -1 by a core developer (lazy
consensus), happens on the issue or pull request page. Core developers are
expected to give “reasonable time” to others to give their opinion on the pull
request if they are not confident others would agree.</p></li>
<li><p><strong>Code changes and major documentation changes</strong>
require +1 by one core developer, no -1 by a core developer (lazy
consensus), happens on the issue of pull-request page.</p></li>
<li><p><strong>Changes to the API principles and changes to dependencies or supported
versions</strong> follow the decision-making process outlined above.</p></li>
<li><p><strong>Changes to the governance model</strong> use the same decision process outlined above.</p></li>
</ul>
<p>If a veto -1 vote is cast on a lazy consensus, the proposer can appeal to the
community and core developers and the change can be approved or rejected using
the decision making procedure outlined above.</p>
</section>
<section id="conflict-of-interest">
<h2>Conflict of Interest<a class="headerlink" href="#conflict-of-interest" title="Link to this heading">#</a></h2>
<p>It is expected that Geomstats Team Members will be employed at a wide range of companies,
universities and non-profit organizations. Because of this, it is possible that Members will have
conflict of interests. Such conflict of interests include, but are not limited to:</p>
<blockquote>
<div><ul class="simple">
<li><p>Financial interests, such as investments, employment or contracting work, outside of Geomstats that may influence their contributions.</p></li>
<li><p>Access to proprietary information of their employer that could potentially leak into their work with Geomstats.</p></li>
</ul>
</div></blockquote>
<p>All members of Geomstats shall disclose to the Technical Committee any conflict of interest they may have.</p>
<p>Members with a conflict of interest in a particular issue may participate in discussions on that issue, but must recuse themselves from voting on the issue.</p>
</section>
<section id="breach">
<h2>Breach<a class="headerlink" href="#breach" title="Link to this heading">#</a></h2>
<p>Non-compliance with the terms of the governance documents shall be reported to the Technical Committee either through public or private channels as deemed appropriate.</p>
</section>
<section id="changing-the-governance-documents">
<h2>Changing the Governance Documents<a class="headerlink" href="#changing-the-governance-documents" title="Link to this heading">#</a></h2>
<p>Changes to the governance documents are submitted via a GitHub pull request targeting <a class="reference external" href="https://github.com/geomstats/geomstats/blob/main/docs/governance.rst">Geomstats governance documents</a>.
The pull request is then refined in response to public comment and review, with the goal being consensus in the community.
After this open period, a member of the Technical Committee proposes to the core developers that the changes be ratified and the pull request merged (accepting the proposed changes)
or proposes that the pull request be closed without merging (rejecting the proposed changes). The Technical Committee member should state the final commit hash in the pull request being proposed
for acceptance or rejection and briefly summarize the pull request. A minimum of 60% of the core developers must vote and at least 2/3 of the votes must be positive to carry out the proposed action
(fractions of a vote rounded up to the nearest integer).</p>
</section>
</section>
</article>
<footer class="prev-next-footer d-print-none">
<div class="prev-next-area">
<a class="left-prev"
href="roadmap.html"
title="previous page">
<i class="fa-solid fa-angle-left"></i>
<div class="prev-next-info">
<p class="prev-next-subtitle">previous</p>
<p class="prev-next-title">Roadmap</p>
</div>
</a>
<a class="right-next"
href="gsod.html"
title="next page">
<div class="prev-next-info">
<p class="prev-next-subtitle">next</p>
<p class="prev-next-title">Google Season of Docs: Case Study</p>
</div>
<i class="fa-solid fa-angle-right"></i>
</a>
</div>
</footer>
</div>
<dialog id="pst-secondary-sidebar-modal"></dialog>
<div id="pst-secondary-sidebar" class="bd-sidebar-secondary bd-toc"><div class="sidebar-secondary-items sidebar-secondary__inner">
<div class="sidebar-secondary-item">
<div
id="pst-page-navigation-heading-2"
class="page-toc tocsection onthispage">
<i class="fa-solid fa-list"></i> On this page
</div>
<nav class="bd-toc-nav page-toc" aria-labelledby="pst-page-navigation-heading-2">
<ul class="visible nav section-nav flex-column">
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#roles-and-responsibilities">Roles And Responsibilities</a><ul class="nav section-nav flex-column">
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#contributors">Contributors</a></li>
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#contributor-experience-team">Contributor Experience Team</a></li>
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#communication-team">Communication team</a></li>
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#core-developers">Core developers</a></li>
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#technical-committee">Technical Committee</a></li>
</ul>
</li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#decision-making-process">Decision Making Process</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#conflict-of-interest">Conflict of Interest</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#breach">Breach</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#changing-the-governance-documents">Changing the Governance Documents</a></li>
</ul>
</nav></div>
<div class="sidebar-secondary-item">
<div class="tocsection sourcelink">
<a href="_sources/governance.rst.txt">
<i class="fa-solid fa-file-lines"></i> Show Source
</a>
</div>
</div>
</div></div>
</div>
<footer class="bd-footer-content">
</footer>
</main>
</div>
</div>
<!-- Scripts loaded after <body> so the DOM is not blocked -->
<script defer src="_static/scripts/bootstrap.js?digest=26a4bc78f4c0ddb94549"></script>
<script defer src="_static/scripts/pydata-sphinx-theme.js?digest=26a4bc78f4c0ddb94549"></script>
<footer class="bd-footer">
<div class="bd-footer__inner bd-page-width">
<div class="footer-items__start">
<div class="footer-item">
<p class="copyright">
© Copyright 2022-2023, Geomstats, Inc..
<br/>
</p>
</div>
<div class="footer-item">
<p class="sphinx-version">
Created using <a href="https://www.sphinx-doc.org/">Sphinx</a> 8.1.3.
<br/>
</p>
</div>
</div>
<div class="footer-items__end">
<div class="footer-item">
<p class="theme-version">
Built with the <a href="https://pydata-sphinx-theme.readthedocs.io/en/stable/index.html">PyData Sphinx Theme</a> 0.16.0.
</p></div>
</div>
</div>
</footer>
</body>
</html>