255 lines
14 KiB
HTML
255 lines
14 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<title>TiB. | Network</title>
|
|
<link rel="stylesheet" href="/assets/TiB.css">
|
|
<link rel="icon" href="/favicon.ico" type="image/x-icon" />
|
|
<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" width=25% style="vertical-align:top" /></header>
|
|
<nav><h4 style="text-align: right"><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="about"><a href="/about">About</a></li></h4></nav>
|
|
<p>
|
|
Tebibyte Media's <i>raison d'être</i> is its Network. Our goal as a
|
|
Project is to foster the creation of that Network by extending
|
|
connections of solidarity between project who share the values we
|
|
believe are important in the new digital age.
|
|
</p>
|
|
|
|
<h2 id="specification"><a href="#specification">Specification</a></h2>
|
|
<p>
|
|
Tebibyte Media is composed of two distinct parts: the Network and
|
|
the Project. The latter is made up of myself, the individuals I
|
|
have recruited into the Project, and the infrastructure which supports
|
|
it; the former, the constituent projects and networks which are
|
|
associated with the Project. This distinction exists in order to
|
|
maintain an appropriate separation between the interests of these
|
|
entities to preserve the heterogeneity of these communities.
|
|
</p>
|
|
<p>
|
|
Like the components defined above, the members of the Network are
|
|
split into two separate categories:
|
|
</p>
|
|
<p>
|
|
A "project" in this context is an entity whose constituents are
|
|
individuals; a "network" 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
|
|
post-modernist fiction-writing blog can 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 "project" could be an open writing publication requiring
|
|
attention or third-party reviewing, a free software project
|
|
looking for a userbase and pool of talented developers, or an art
|
|
project looking for exposure and contributors.
|
|
</p>
|
|
<p>
|
|
A "network" might be a webring, an online social hub for the
|
|
advancement of some idea or combined agenda, or an organization
|
|
which has multiple distinct components or internal projects but
|
|
which still works toward one main goal. A webring whose
|
|
constituents are all blogs that focus on physics would be an
|
|
example.
|
|
</p>
|
|
<p>
|
|
In the case of members creating new networks internal to Tebibyte
|
|
Media's influence, we take it upon ourselves to mediate and foster
|
|
that connection; we see these novel networks as partially our
|
|
responsibility.
|
|
</p>
|
|
|
|
<h2 id="responsibilities"><a href="#responsibilities">Responsibilites &
|
|
Assurances</a></h2>
|
|
<p>
|
|
Joining the Network is not a binding agreement. We would obviously
|
|
<i>prefer</i> it if members would adhere to the responsibilities we
|
|
ask them to adhere to, but we obviously cannot force them to, and
|
|
they are under no formal obligation to. In the same way, the Network
|
|
is set up in a way that prevents Tebibyte Media (the Project) from
|
|
using its power to harm members. All data and servers relating to
|
|
any given member's infrastructure are theirs, with administrator
|
|
privileges attached to those resources.
|
|
</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 that Representative or could
|
|
select someone else to represent it. Any 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 put out
|
|
a blog post detailing the month in review of the Network.
|
|
Representatives of each member entity will be responsible for
|
|
working with the Project Editors in order to write a short two- or
|
|
three-paragraph decription of the state of their member entity,
|
|
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>
|
|
|
|
<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>Self-hosted <a
|
|
href="https://wordpress.com/">Wordpress</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>Website hosting alternatives
|
|
<ul>
|
|
<li><a href="https://getzola.org/">Zola</a></li>
|
|
<li><a href="https://jekyllrb.com/">Jekyll</a></li>
|
|
</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 benefit of the existing Tebibyte Media Network as a base-level of exposure.
|
|
</p>
|
|
|
|
<h2 id="members"><a href="#members">Members</a></h2>
|
|
<!-- <p><a href="https://farside.link/https://instagram.com/_remind_me_tomorrow">_remind_me_tomorrow</a>,
|
|
a platform dependent essay, hosted on Instagram, which deals with
|
|
the ways that The Digital has been made precarious over the past
|
|
several decades. Created by
|
|
<a href="https://embeddedscript.net/">Richard Williams</a>
|
|
<a title="Unlicensed JavaScript" href="https://www.gnu.org/philosophy/javascript-trap.html">[!]</a>.
|
|
Linked here using a free software frontend for Instagram.</p> -->
|
|
<p><a href="https://git.tebibyte.media/sashakoshka/arf">ARF</a>, an
|
|
experimental programming language.</p>
|
|
<!-- <p><a href="https://git.tebibyte.media/canary/canary">Canary</a> -->
|
|
<p><a href="https://git.tebibyte.media/nexus/nexus">Nexus, a
|
|
federated, free software, hackable VR social platform and
|
|
protocol.</a></p>
|
|
<!-- <p><a href="https://ortusjournal.org">Ortus Journal, a journal
|
|
of speculative analysis</a>
|
|
<a title="nonfree plugins" href="https://gschoppe.com/wordpress/plugins-and-themes-open-source/">[!]</a></p> -->
|
|
|
|
<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/nexus.txt">here</a>.</p>
|
|
<p>Please write the application in plaintext as an essay without
|
|
organizational headers.</p>
|
|
<ol>
|
|
<li>Name of project or network and describe organizational makeup
|
|
<ul>
|
|
<li>List member projects of applicant networks</li>
|
|
<li>List team members of applicant projects and their roles</li>
|
|
<li>Designate of the Representative(s)</li>
|
|
</ul>
|
|
</li>
|
|
<li>A short written section describing the project or network
|
|
<ul>
|
|
<li>Include the type of project or network (i.e. software,
|
|
educational resource, publisher, art project)</li>
|
|
<li>Also include any programming languages, writing styles,
|
|
target platforms or technical information regarding the creation
|
|
of content</li>
|
|
<li>Link technical resources which contextualize its creation,
|
|
including:
|
|
<ul>
|
|
<li>Referenced materials used throughout the process of its
|
|
creation</li>
|
|
<li>Similar work or work upon which it is based</li>
|
|
<li>References to issues with a similar entity which it
|
|
addresses</li>
|
|
</ul>
|
|
</li>
|
|
<li>Describe the userbase and contributors attempting to be
|
|
appealed to</li>
|
|
<li>Describe long-term goals for the endeavor:
|
|
<ol>
|
|
<li>What will it look like in a year?</li>
|
|
<li>What does it gain from joining the Network?</li>
|
|
<li>What does it bring to the table for other Network
|
|
members?
|
|
<ul>
|
|
<li>If the proposed member is a writing collective, it
|
|
could provide valuable editorial experience and
|
|
knowledge</li>
|
|
<li>Art projects could work with editorial and
|
|
software entities to create combined works or to design
|
|
graphics, typefaces, or logotypes</li>
|
|
</ul>
|
|
</li>
|
|
</li>
|
|
<li>Prompt questions to answer as a conclusion could include
|
|
the following:
|
|
<ul>
|
|
<li>How does this endeavor contribute to the ecosystem it
|
|
integrates?</li>
|
|
<li>What specific problems is this new endeavor solving?</li>
|
|
<li>Do any existing projects solve these problems already?
|
|
If so, how is this endeavor different?</li>
|
|
<li>Is this a highly experimental endeavor that innovates
|
|
its field, a refined reimplementation of a tried-and-true
|
|
solution, or something in between?</li>
|
|
</ul>
|
|
</li>
|
|
<li>Feel free to include any extra information deemed important
|
|
to specify; the application cannot account for everything</li>
|
|
</ul>
|
|
</li>
|
|
<li>(If not already existing) a clear description of the vision of
|
|
the project or network's
|
|
<a href="https://en.wikipedia.org/wiki/Minimum_viable_product">minimum
|
|
viable product</a>
|
|
<ul>
|
|
<li>Remember to
|
|
<a href="http://www.catb.org/%7Eesr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html">Release Early, Release Often</a></li>
|
|
<li>Minimum viable products are not complete or fully
|
|
functional; they must simply demonstrate promising work</li>
|
|
</ul>
|
|
</li>
|
|
<li>Estimated timespans for the project or network (i.e. one month,
|
|
a few months, a year, continuous) and a roadmap for the completed
|
|
project</li>
|
|
<li>Project licensing details
|
|
<ul>
|
|
<li>Tebibyte Media will not accept projects whose licensing
|
|
conflicts with our goal of furthering free software and
|
|
open-access projects. For guidance on this topic, 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></li>
|
|
</ul>
|
|
</li>
|
|
</ol>
|
|
</body>
|
|
</html> |