-
Notifications
You must be signed in to change notification settings - Fork 28
/
process.html
153 lines (133 loc) · 5.86 KB
/
process.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
---
layout: page
---
<!-- Header -->
<header>
<div class="container">
<br/><br/><br/>
<div class="row">
<div class="col-lg-12 text-center">
<h2 class="page-heading">The AI•ON process & FAQ</h2>
</div>
</div>
<br/><br/>
</div>
</header>
<section id="" class="bg-light-gray">
<div class="container">
<br>
<div class="row">
<div class="col-md-1">
</div>
<div class="col-md-10">
<div class="text-item">
<h3>Team formation</h3>
<p>
Researchers and students interested in tackling a specific problem
should sign up to the mailing list (Google Group) associated with the problem or get in touch through.
The link can be found next to the problem description. We also have a AI•ON gitter chat.
Anyone is free to join. Teams are meant to be self-organized and self-supervised,
with only occasional lightweight mentorship from senior researchers.
</p>
</div>
</div>
<div class="col-md-1">
</div>
</div>
<hr>
<div class="row">
<div class="col-md-1">
</div>
<div class="col-md-10">
<div class="text-item">
<h3>Problem solving</h3>
<p>
The entire research process takes place in the open,
with communications happening via either a Google group or a Gitter channel.
Code is exchanged via public git repositories on GitHub or Gitlab.
The repositories are created and managed by team members.
</p>
</div>
</div>
<div class="col-md-1">
</div>
</div>
<hr>
<div class="row">
<div class="col-md-1">
</div>
<div class="col-md-10">
<div class="text-item">
<h3>Publication</h3>
<p>
The research process takes place in the open,
which is already a form of publication and result-sharing.
However some results may be organized into research papers
to be submitted to Arxiv and research conferences.
Authors lists and credit attribution is expected to be handled by team members,
with conflicts escalated to third-party arbiters.
Every person who made a contribution, internal or external to the team,
should be getting appropriate and commensurate recognition for the value they provided.
In particular, senior researchers who submitted the problem that is
the topic of the publication and who provided mentorship throughout
the research process should have a reasonable expectation of co-authorship.
AI•ON itself should also be acknowledged in some form in all publications
(e.g. under the "acknowledgments" section).
</p>
</div>
</div>
<div class="col-md-1">
</div>
</div>
<hr>
<div class="row">
<div class="col-md-1">
</div>
<div class="col-md-10">
<div class="text-item">
<h3>Conflict resolution authority</h3>
<p>
Openness is our core value, and an organization can only be open if power within it is transparently distributed to many individuals.
However, having access to a third-party authority is still necessary to quickly resolve any conflict that may arise.
AI•ON maintains a list of arbiters that may be contacted in case of issue.
The list is as follow (note that it will grow as AI•ON matures):
<br>
<ul>
<li>Francois Chollet - [email protected]</li>
<li>Gabriel Pereyra - [email protected]</li>
<li>Hugo Larochelle - [email protected]</li>
</ul>
</p>
</div>
</div>
<div class="col-md-1">
</div>
</div>
<hr>
<div class="row">
<div class="col-md-1">
</div>
<div class="col-md-10">
<div class="text-item">
<h3>On the fear of "scooping"</h3>
<p>
The fact that the research process of every AI•ON project gets publicly documented, from ideation to open-source code deliverables, may raise concerns about having ideas or code taken from AI•ON by unscrupulous parties and published as their own. This is both inevitable and utterly unimportant. Inevitable because such events always occur no matter where results come from and how they get published. Unimportant because it has ultimately no long-term consequences. The fact that the research process of AI•ON is fully public and continuously timestamped by neutral third-parties (Google, GitHub, etc.) makes it possible to easily prove where specific results originated.
</p>
</div>
</div>
<div class="col-md-1">
</div>
</div>
<br><br>
</div>
</section>