Why galaxy-beep-frame
=====================

Origin story
------------

One day, I discovered the `BEEP protocol`_, and I felt like it was great !
But work on BEEP protocol seems to have "stopped" or at least significatively
slow down. Of course, this is due to the fact that it is not very used, to say
the least.

There is some very important and great software still alive and going well, like
`Vortex`_, which has python binding. But the only native python implementation I
found, `BEEPy`_, was not updated since 12 years.

So this is a new take on making a python library for the `BEEP protocol`_,
because the more the merrier (and there isn't much on this subject anyway).
This first software only focus on frames and is a brick for future project.

Like `galaxy-graph`_, this library is:

#. **FLOSS, not FOSS:** licensing is a political issue. I want to live in a world where everyone contributes to the commons.
#. **Typed:** because I love static typing in dynamic language \\o/.
#. **Simple:** there is a frame, a parser, and that's it. For now, this is not totally exact, but work is being done in this direction.

Why galaxy
----------

(this part is common to every "galaxy" project)

I have started a long-standing project called *modularity* in PHP. The
goal is to have very flexible pieces that can be put together to form
a modular framework.

With this project, I am starting something similar in Python, so I
needed a prefix for the project name to ensure consistency if I continue
with more Python project with the same principle.

I love space, so I chose the prefix "galaxy". Other *galaxy* projects are
available on the `galaxy homepage`_.

.. _BEEP protocol: https://datatracker.ietf.org/doc/html/rfc3080
.. _Vortex: https://www.aspl.es/vortex/
.. _BEEPy: https://sourceforge.net/projects/beepy/
.. _galaxy homepage: https://galaxy.linarphy.net
.. _galaxy-graph: https://graph.galaxy.linarphy.net