-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
38 lines (33 loc) · 2.92 KB
/
index.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
<!DOCTYPE html>
<html>
<head>
<title>Expo Community</title>
<link rel="stylesheet" type="text/css" href="build/base.css" />
</head>
<body>
<nav class="flex items-center justify-between flex-wrap bg-expo-blue p-6">
<div class="flex items-center flex-shrink-0 text-white mr-6">
<span class="font-semibold text-xl">Expo Community</span>
</div>
<div class="w-auto block flex-grow flex items-center">
<div class="text-sm flex-grow"></div>
<div>
<a href="https://github.com/expo-community/" class="inline-block text-sm px-4 py-2 leading-none rounded text-white hover:underline">GitHub</a>
</div>
</div>
</nav>
<main class="container mx-auto px-8">
<h1 class="font-bold text-xl mt-4">expo-community</h1>
<p class="mt-2">The expo-community GitHub organization is a collection of repositories for Expo projects. We're currently getting it set up and starting with a few repos. The types of repos we have in mind include project-management tools, CI integrations, components, integrations with proprietary services, and so on.</p>
<h2 class="font-bold text-l mt-4">Org Management</h2>
<p class="mt-2">Each repo maintainer administers the repos for which they're responsible. There are also a small number of expo-community stewards who have admin access to all repos if they need to act as moderators. Some members of the Expo team are org owners and are responsible for accepting repos into or transferring them out of this org and moderation.</p>
<h2 class="font-bold text-l mt-4">Public Repos</h2>
<p class="mt-2">All of the repos under this org are public. It is under GitHub's free plan.</p>
<h2 class="font-bold text-l mt-4">Maintainer Expectations</h2>
<p class="mt-2">The repos in this organization generally need to be maintained. We find that repos are often best maintained when their maintainers are using the library in production. When a maintainer's priorities change or they aren't using the library in production anymore, we ask they transfer ownership of the repo to a new maintainer who is using the library in production or transfer the repo out of the expo-community org. If someone steps up to maintain a repo and cares about it working well in production, that's a good signal it still belongs in this org.</p>
<p class="mt-2">We also would like to see sustained maintenance and health of a repo before accepting it into the expo-community org. A maintainer's track record also helps too. Holistically speaking, we want the repos in this org to be durably healthy.</p>
<h2 class="font-bold text-l mt-4">Code of Conduct</h2>
<p class="mt-2">The <a href="https://expo.io/guidelines" class="text-expo-blue hover:underline">Expo community guidelines</a> apply here to everyone, including participants on GitHub issues. We expect maintainers especially to set positive examples.</p>
</main>
</body>
</html>