-
Notifications
You must be signed in to change notification settings - Fork 0
/
what-is-monadic.html
80 lines (76 loc) · 8.04 KB
/
what-is-monadic.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
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<title>Monadic</title>
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link rel="stylesheet" type="text/css" media="screen" href="css/styles.css" />
<meta name="twitter:card" content="summary" />
<meta name="twitter:site" content="monadic.xyz" />
<meta name="twitter:title" content="What is Monadic" />
<meta name="twitter:description"
content="Monadic is a group of technologists who set out in 2017 to build the future of free and open source software collaboration." />
<meta name="twitter:image"
content="https://res.cloudinary.com/juliendonck/image/upload/v1574072407/monadic.xyz/monadic_logo_09.png" />
</head>
<body>
<div class="page">
<div class="content">
<a class="logo-link" href="/">
<div class="logo-2">Monadic</div>
</a>
<main>
<h2>On Monadic</h2>
<p>
Monadic is a group of technologists who in 2017, set out to re-imagine free and open source software collaboration with protocols, not platforms. While we're a Berlin-based software company, we are remote-first, with team members spread across six countries. We have a home base in the heart of Kreuzberg, in a sunny office with giant plants and lots of tea.
</p>
<img src="https://res.cloudinary.com/dvargvav9/image/upload/v1592410860/AfterlightImage_1_offypk.jpg" class="w3-round">
<p>
As lovers of free and open source, we think that maintaining the resilience and health of the free and open source ecosystem is more important than ever. Our reliance on centralized platforms is unsustainable and contradicts the values of free and open source that brought us all together in the first place. We conceived Radicle as an alternative — a free and open-source way to host, share, and build software together. You can read more about our vision of decentralized code collaboration <a href="https://radicle.xyz/towards-decentralized-code-collaboration.html">here</a>.
<br/><br/>
We've been lucky enough to have found an amazing group of partners that, like us, want to make decentralized code collaboration a reality.
</p>
<h2>
What we do
</h2>
<p>
In addition to contributing to the Radicle project, the Monadic team leads the development of <b>Upstream</b>, a desktop application built on Radicle. We believe that building functional, usable, and beautiful experiences for developers is essential when challenging the status quo. While we envision this application to be the main way users interact with Radicle, it will not be the only way. Upstream, as with the Radicle protocols, will be completely open-source and forkable — giving anybody the space to develop their own code collaboration experience.
<br/><br/>
While Monadic currently drives most of Radicle development, <i>we don't own Radicle</i>. Radicle is a free and open source project, made up of protocols that anyone can use, modify, and build on. We believe that to truly be a decentralized alternative for code collaboration, Radicle needs to be developed <b>by</b> a community, not just <b>for</b> one. Our goal is for the project to be maintained, governed, and owned by its community — putting it in the hands of the free and open source developers that use it. Monadic will be just one of many organizations building, maintaining, and contributing to the Radicle protocols. Our current role within the Radicle project is to <b>support and guide the progressive decentralization of the project</b> while contributing as much as we can with the resources at hand. This means:
<ul>
<li> The Radicle project will not be owned or governed by Monadic. Ownership of project repositories will be transferred to their maintainers and formal proposal improvement mechanisms will be put in place. </li>
<li> Protocol specifications, funds, trademarks & legal artefacts, and domains will be controlled by a separate, neutral, non-profit entity called the Radicle Foundation. </li>
<li> Monadic will manage the development of <a href="https://github.com/radicle-dev/radicle-upstream">Upstream</a>, a desktop client built on Radicle. All Upstream work will be public by default and licensed under GPL. </li>
</ul>
</p>
<p>
In the meantime, we'll maintain Radicle until it's ready to be off-ramped to the community and focus on building experiences (like Upstream!) that make it easier, better, and simpler to use and build on Radicle.
</p>
<h2>
We're Public by Default
</h2>
<p>
In any free and open source project, transparency and openness is key for developing an engaged and supported community. The presence of a core group of full-time contributors is great for development of a project, but can often introduce more 'closed' and 'internal' processes that can inhibit the growth of an open source community. Here's how we're introducing transparency into what we do at Monadic:
<br/><br/>
<b>With regards to contributions to the Radicle protocols</b>, we believe there must be a natural focal shift away from 'core team' development to community development. We believe this is necessary to maintain the resilience of the project outside of venture funding & investment and to develop a diverse, inclusive, and supported community of contributors and users. Therefore, all internal Monadic collaboration that influences the development & direction of Radicle project has continuously been made public, in an effort to bring transparency in our decision making process, tradeoffs and constraints and onboard more contributors to the Radicle project. Team members contributing to the Radicle protocols collaborate publicly on our community forum, <a href="https://radicle.community/">radicle.community</a> — By focusing on introducing accessibility and encouraging engagement at all steps of the process, we reduce the dependence of the project on the core team and create the space for the community to take over. Here's where you can find our collaboration.
<ul>
<li> All code collaboration will take place on Radicle, but for now is on <a href="https://github.com/radicle-dev">GitHub</a> </li>
<li> All other collaboration takes place on the community forum, <a href="https://radicle.community/">radicle.community</a> </li>
<li> A public IRC channel (<a href="irc://freenode:1/radicle">#radicle</a>) exists for real-time collaboration within the community </li>
</ul>
</p>
<p>
<b>With regards to the Monadic's development of Upstream</b>, we believe that to truly embody free and open source values we must also embody a "public by default" mode of development. Our team uses radicle.community (specifically the <a href="https://radicle.community/c/product/10">#Product</a> category) for public collaboration on Upstream development. In addition, we document our work in a public workspace on Notion. This will be the place to check out our product roadmaps, cycle objectives, project management dashboards, and other key parts of the product development process.
<br/><br/>
By developing openly, we introduce transparency into our work and create clear avenues for engagement with our community members, users, and contributors. It also drives us to continuously improve our documentation, communicate our decision-making, and create accessible and safe spaces for people to challenge our thought processes. Check out the Monadic workspace <a href="https://www.notion.so/monadic/Monadic-592f379dbcb64c78aa835a34d8b17b7b">here</a>.
</p>
<hr>
<p>
By keeping progressive decentralization and transparency at heart of our work, we hope to support the independence and resilience of the Radicle project while building beautiful peer-to-peer code collaboration experiences. If you have any questions about Monadic and how we work, throw up a post on radicle.community, drop a message in #radicle, or DM us on twitter.
</p>
</div>
</div>
</main>
</body>
</html>