433 lines
18 KiB
HTML
433 lines
18 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en-US">
|
|
<head>
|
|
<title>TiB. | Network</title>
|
|
<link rel="stylesheet" href="/assets/TiB.css">
|
|
<link rel="icon" href="/favicon.ico" type="image/x-icon" />
|
|
<meta charset="UTF-8">
|
|
<meta content="Emma Tebibyte" name="author" />
|
|
<meta content="Tebibyte Media Network directory." name="description" />
|
|
<meta content="width=device-width, initial-scale=1" name="viewport" />
|
|
<meta content="interest-cohort=()" http-equiv="Permissions-Policy" /> <!-- FUCK GOOGLE -->
|
|
</head>
|
|
<body id="network">
|
|
<header>
|
|
<img id="logo" src="/assets/img/TiB-network.png" />
|
|
</header>
|
|
<nav>
|
|
<menu>
|
|
<li class="home">
|
|
<a href="/">Home</a>
|
|
</li>
|
|
|
|
<li class="network">
|
|
<a href="/network">Network</a>
|
|
</li>
|
|
|
|
<li class="blog">
|
|
<a href="/blog">Weblog</a>
|
|
</li>
|
|
|
|
<li class="git">
|
|
<a href="https://git.tebibyte.media/">Git</a>
|
|
</li>
|
|
|
|
<li class="about">
|
|
<a href="/about">About</a>
|
|
</li>
|
|
</menu>
|
|
</nav>
|
|
<main>
|
|
<section>
|
|
<h2 id="members">
|
|
<a href="#members">Members</a>
|
|
</h2>
|
|
<dl>
|
|
<dt>
|
|
<a href="https://git.tebibyte.media/sashakoshka/arf">
|
|
ARF</a>
|
|
</dt>
|
|
<dd>
|
|
An experimental programming language with a focus on
|
|
modularization and clarity of code.
|
|
</dd>
|
|
|
|
<dt>
|
|
<a href="https://git.tebibyte.media/canary/canary">
|
|
Canary</a>
|
|
</dt>
|
|
<dd>
|
|
A post-structuralist graphical user interface (GUI)
|
|
using WebAssembly scripting for its runtime logic.
|
|
</dd>
|
|
<dt>
|
|
<a href="https://git.tebibyte.media/cyborg/cyborg">
|
|
Cyborg</a>
|
|
</dt>
|
|
<dd>
|
|
An artist-oriented realtime 3D rendering engine.
|
|
</dd>
|
|
|
|
<dt>
|
|
<a href="https://git.tebibyte.media/minecrust/hopper">Hopper
|
|
</a>
|
|
</dt>
|
|
<dd>
|
|
A Minecraft package manager, which is capable of
|
|
globally downloading and updating mods, modpacks,
|
|
plugins, and resource packs.
|
|
</dd>
|
|
<!-- <dt>
|
|
<a> href="https://ortusjournal.org">Ortus Journal</a>
|
|
</dt>
|
|
<dd>
|
|
A journal of speculative analysis
|
|
</dd> -->
|
|
</dl>
|
|
</section>
|
|
<section>
|
|
<hgroup>
|
|
<h2 id="specification">
|
|
<a href="#specification">Specification</a>
|
|
</h2>
|
|
<aside>
|
|
<small>
|
|
Read about Tebibyte Media's structure and governance
|
|
<a href="/about#structure">here</a>.
|
|
</small>
|
|
</aside>
|
|
</hgroup>
|
|
<p>
|
|
The members of the Network are split into two separate
|
|
categories: a <dfn id="project">project</dfn> in this context is
|
|
an entity whose constituents are individuals; a
|
|
<dfn id="network">network</dfn> is one whose members are
|
|
projects themselves or a mix of projects and other networks.
|
|
</p>
|
|
<p>
|
|
A Tebibyte Media project does not necessarily have to
|
|
be a free software project; it can be anything involving strong
|
|
public engagement and iterative development. For example, a
|
|
postmodernist fiction blog could count as a Tebibyte Media
|
|
project as long as the work is ongoing and the blog is shared at
|
|
no cost to its readers.
|
|
</p>
|
|
<p>
|
|
A network might be a webring, an online social hub for the
|
|
advancement of an idea or collective agenda, or an
|
|
organization which has multiple discrete components or
|
|
internal projects with distinct individuals heading them up.
|
|
A group of sites whose constituents are all blogs that focus on
|
|
physics could be an example of a Tebibyte Media network.
|
|
</p>
|
|
</section>
|
|
<section>
|
|
<h2 id="responsibilities">
|
|
<a href="#responsibilities">
|
|
Responsibilites & Assurances
|
|
</a>
|
|
</h2>
|
|
<p>
|
|
Tebibyte Media's Network is designed in a way that is meant to
|
|
prevent the Project from wielding power over members. All data
|
|
and servers relating to any given member's infrastructure and
|
|
the administrative privileges that come with it are theirs.
|
|
</p>
|
|
<p>
|
|
Every project in the Network will be represented by a single
|
|
person who will be appropriately selected by the members of
|
|
that project. For example, in the case of a free software
|
|
project run by a BDFL, the leader of that project would be
|
|
tasked with selecting the representative.
|
|
</p>
|
|
<p>
|
|
Note that we only want one representative from each project
|
|
because it will simplify communication; to have a specific
|
|
individual we know we can reach out to in discussions is
|
|
important for quick resolutions.
|
|
</p>
|
|
<p>
|
|
Member networks are given the opportunity to provide as
|
|
many representatives as there are distinct viewpoints in the
|
|
community that network represents.
|
|
</p>
|
|
<p>
|
|
Every month, on the first day of the month, the Project will
|
|
publish a blog post detailing the month in review of the
|
|
Network. Representatives of each member will be responsible for
|
|
working with the Project editors to write a short decription of
|
|
the state of the member, including what has been accomplished in
|
|
the past month and what is on the horizon. These sections will
|
|
be submitted to the blog repository using the git
|
|
version-tracking system. Knowledge of this system is not
|
|
required but is preferred. Our editors will be able to guide
|
|
representatives through the submission process and help with any
|
|
problems presented by this setup.
|
|
</p>
|
|
</section>
|
|
<section>
|
|
<h2 id="benefits">
|
|
<a href="#benefits">Member Benefits</a>
|
|
</h2>
|
|
<p>
|
|
The Project takes upon itself responsibilities for each member
|
|
of the Network. We will provide infrastructure that your project
|
|
needs to succeed. Infrastructure currently available includes:
|
|
<ul>
|
|
<li>Website hosting</li>
|
|
<ul>
|
|
<li><a href="https://jekyllrb.com/">Jekyll</a></li>
|
|
|
|
<li>
|
|
Self-hosted <a href="https://wordpress.com/">
|
|
Wordpress
|
|
</a>
|
|
</li>
|
|
|
|
<li><a href="https://getzola.org/">Zola</a></li>
|
|
</ul>
|
|
|
|
<li>
|
|
A dedicated <a href="https://matrix.org/">Matrix</a>
|
|
room
|
|
</li>
|
|
|
|
<li>An e-mail server</li>
|
|
|
|
<li>
|
|
A dedicated feed channel on <a href="/discord">our
|
|
Discord "server"</a>
|
|
</li>
|
|
</ul>
|
|
Planned infrastructure includes:
|
|
<ul>
|
|
<li><a href="https://fosscord.com/">Fosscord</a> Guilds</li>
|
|
|
|
<li>
|
|
Package maintenance (i.e.
|
|
<a href="https://mpr.makedeb.org/">
|
|
MPR
|
|
</a>/<a href="https://aur.archlinux.org/">
|
|
AUR
|
|
</a>)
|
|
</li>
|
|
|
|
<li>Documentation</li>
|
|
<ul>
|
|
<li>
|
|
<a href="https://rust-lang.github.io/mdBook/">
|
|
mdBook
|
|
</a>
|
|
</li>
|
|
</ul>
|
|
</ul>
|
|
In addition to benefits, we also offer community coordination
|
|
and the existing Tebibyte Media Network as a baseline level of
|
|
exposure.
|
|
</p>
|
|
</section>
|
|
<section>
|
|
<h2 id="application">
|
|
<a href="#application">Application</a>
|
|
</h2>
|
|
<p>
|
|
In order to apply to be a member of the Tebibyte Media
|
|
Network, please reference the below guidelines. All applications
|
|
should be sent to <a href="mailto:apply@tebibyte.media">
|
|
apply@tebibyte.media</a>.<!-- A sample application is located
|
|
<a href="sample-applications/">here</a>.-->
|
|
</p>
|
|
<p>
|
|
Please write the application in plaintext as an essay without
|
|
organizational headings.
|
|
</p>
|
|
<ol>
|
|
<li>
|
|
<p>
|
|
Include the name of the applicant and describe its
|
|
organizational makeup; specify constituents and appoint
|
|
representative(s).
|
|
<a title="More Information" href="#specification">[?]
|
|
</a>
|
|
</p>
|
|
</li>
|
|
<li>
|
|
<p>
|
|
Define the type of work it is (i.e. software,
|
|
educational resource, publisher, art project).
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Describe the programming languages, writing styles,
|
|
target platforms, or technical information regarding the
|
|
creation of its contents.
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Link technical resources which contextualize its
|
|
creation, including reference materials, any work that
|
|
is similar, or anything upon which it is based. This may
|
|
include any issues encountered by similar works that the
|
|
applicant plans to solve.
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Is this an experimental undertaking, which innovates in
|
|
its field; a refined reimplementation of a
|
|
tried-and-true solution; or something in between?
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Create a description of the vision of the applicant's
|
|
<a href="https://en.wikipedia.org/wiki/Minimum_viable_product">
|
|
minimum viable product</a>. Minimum viable products are
|
|
not complete or fully functional; they must simply
|
|
demonstrate promising work. It is important to the
|
|
success of any work that it
|
|
<a href="http://www.catb.org/%7Eesr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html">
|
|
releases early and releases often</a>.
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Explain who the target users or audience are and what
|
|
kinds of contributors the applicant would appeal to are.
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Describe the long-term goals of the applicant:
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
<p>
|
|
Estimated timespans: what will it look like in a
|
|
month? In a year? Write a road map.
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
How will it contribute to the ecosystem it
|
|
inhabits?
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Is it trying to solve a problem, occupy an
|
|
unfilled niche, or something else?
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Does anything exist that is also
|
|
attempting solve these problems? If so, how is
|
|
this endeavor different?
|
|
</p>
|
|
</li>
|
|
|
|
</ul>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Answer the following questions:
|
|
</p>
|
|
<ul>
|
|
<li>
|
|
<p>
|
|
What does it gain from joining the Network?
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
What does it bring to the table for other
|
|
Network members? For example, if the applicant
|
|
were a writing collective, it could provide
|
|
valuable editorial knowledge. If it were an art
|
|
project, it could create mixed-media projects
|
|
with other members or design graphics for their
|
|
projects.
|
|
</p>
|
|
<p>
|
|
It should be noted that the applicant need not
|
|
provide services to other Network members. For
|
|
the guidelines on what <i>is</i> required from
|
|
members, see the
|
|
<a href="#responsibilities">Responsibilities</a> section
|
|
of this page.
|
|
</p>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Does the applicant's work follow the
|
|
<a href="http://www.catb.org/esr/writings/taoup/html/ch01s06.html">
|
|
Unix Philosophy</a> (if applicable)? Explain
|
|
why or why not and how, if at all, it departs from it.
|
|
</p>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
|
|
<li>
|
|
<p>
|
|
Include licensing details—Tebibyte Media will not accept
|
|
applicants whose licensing conflicts with our goal of
|
|
furthering free software and open-access ideology. See
|
|
<a href="https://www.gnu.org/licenses/license-recommendations.html">
|
|
the Free Software Foundation's recommendations
|
|
</a> as well as
|
|
<a href="https://www.gnu.org/licenses/license-list.html">
|
|
their list of free software licenses
|
|
</a> for guidance on software licensing; for others, see
|
|
the
|
|
<a href="https://chooser-beta.creativecommons.org/">
|
|
Creative Commons license chooser</a>. Applicants whose
|
|
works are covered in part by a No-Derivatives variant of
|
|
these licenses are accepted <i>only</i> in circumstances
|
|
when that part was created by a third party.
|
|
</p>
|
|
</li>
|
|
</ol>
|
|
</section>
|
|
</main>
|
|
<footer>
|
|
<div class="copyleft">
|
|
<small>
|
|
<a href="https://copyleft.org/">Copyleft</a> 🄯 2022
|
|
Tebibyte Media
|
|
</small>
|
|
</div>
|
|
<div class="webring">
|
|
<span>
|
|
<a href="https://webring.yesterweb.org/noJS/index.php?d=rand&url=https://tebibyte.media/">
|
|
???</a>
|
|
</span>
|
|
<span>
|
|
<a href="https://webring.yesterweb.org/noJS/index.php?d=prev&url=https://tebibyte.media/"><<</a>
|
|
<a href="https://yesterweb.org/webring/">
|
|
Yesterweb</a>
|
|
<a href="https://webring.yesterweb.org/noJS/index.php?d=next&url=https://tebibyte.media/">>></a>
|
|
</span>
|
|
<span>
|
|
<a href="https://yesterweb.org/webring/members.html">..</a>
|
|
</span>
|
|
</div>
|
|
</footer>
|
|
</body>
|
|
</html>
|