<div dir="ltr"><a href="https://github.com/spacedirectory/directory">https://github.com/spacedirectory/directory</a> is that supposed to be empty?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 20, 2017 at 3:02 PM, Danilo <span dir="ltr"><<a href="mailto:mail@dbrgn.ch" target="_blank">mail@dbrgn.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all<br>
<br>
Those of you that have been involved with the SpaceAPI[1] in the last<br>
2-3 years probably took notice that any related development has<br>
essentially stalled. I personally did multiple attempts at improving the<br>
situation and was in contact with the main developer, but with no<br>
tangible results. The directory[2] was frequently offline, inconsistent<br>
or incomplete (at the time of this writing the response returns with<br>
HTTP 200 but closes prematurely without any content). Pull requests with<br>
updates to the data about hackerspaces were not merged for months or<br>
even years. Same thing with pull requests regarding website content.<br>
Some of them were even merged but never deployed.<br>
<br>
There were a few attempts at improving the situation, e.g. Fixme[3]<br>
hosts their own fork[4] of the directory used by the MyHackerspace<br>
app[5] which is actually reliable in contrast to the official one. But<br>
it's not a good long-term solution, since many pull requests are still<br>
directed against the official directory. We also contacted the original<br>
author multiple times, trying to get more maintainers onboard, but that<br>
didn't work out either.<br>
<br>
At the Chaos Communication Congress last December, we (some people from<br>
Coredump[6] and Fixme[3]) met and discussed a full friendly-fork of the<br>
SpaceAPI. After some discussions we ended up with this:<br>
<br>
<a href="https://spacedirectory.org/" rel="noreferrer" target="_blank">https://spacedirectory.org/</a><br>
<br>
The Space Directory has the same goals as the SpaceAPI: Providing an API<br>
specification for sharing data across hackerspaces, fablabs, chaostreffs<br>
and makerspaces across the world. We try to enable easy integration into<br>
opening status systems, door locks, webcams, sensors, and so on. It<br>
should provide a unified interface to get contact information for<br>
hackerspaces. And the project should also showcase interesting<br>
implementations / integrations.<br>
<br>
Our current project status:<br>
<br>
- We created a Github organization: <a href="https://github.com/spacedirectory" rel="noreferrer" target="_blank">https://github.com/<wbr>spacedirectory</a><br>
- We published a website: <a href="https://spacedirectory.org/" rel="noreferrer" target="_blank">https://spacedirectory.org/</a><br>
- We host the directory on a reliable server: <a href="https://spaceapi.fixme.ch/" rel="noreferrer" target="_blank">https://spaceapi.fixme.ch/</a><br>
(will probably also be hosted on <a href="http://spacedirectory.org" rel="noreferrer" target="_blank">spacedirectory.org</a> in the future)<br>
- We maintain a fork of the API specification, ported to the current<br>
JSON Schema version (IETF draft 4):<br>
<a href="https://github.com/spacedirectory/schema" rel="noreferrer" target="_blank">https://github.com/<wbr>spacedirectory/schema</a><br>
- We provide API documentation automatically generated from the schema<br>
files: <a href="https://spacedirectory.org/pages/docs.html" rel="noreferrer" target="_blank">https://spacedirectory.org/<wbr>pages/docs.html</a><br>
- We started porting over the "apps" page:<br>
<a href="https://spacedirectory.org/pages/apps.html" rel="noreferrer" target="_blank">https://spacedirectory.org/<wbr>pages/apps.html</a> It's not complete yet, but<br>
we'll get there.<br>
- We started writing a new schema validator:<br>
<a href="https://github.com/spacedirectory/validator" rel="noreferrer" target="_blank">https://github.com/<wbr>spacedirectory/validator</a><br>
<br>
The Github organization currently has 4 members, so the bus factor is<br>
already up by 300%. But we're still looking for contributors! If you<br>
would like to push the SpaceAPI ecosystem ahead, feel free to take a<br>
look at the projects in our Github organization. For general discussion,<br>
open an issue in the Meta-Project[7]. If you want to become part of the<br>
Github organization, contact me or open an issue in the Meta-Project[7].<br>
<br>
Last but not least, we'd like to thank Slopjong for the countless hours<br>
he has put into the original SpaceAPI project. It's great what he<br>
achieved and we'll continue his efforts! Thank you :)<br>
<br>
We're happy about any feedback or ideas related to the project, be it<br>
here or on Github :)<br>
<br>
Danilo (Coredump Hackerspace, Switzerland)<br>
<br>
[1] <a href="http://spaceapi.net/" rel="noreferrer" target="_blank">http://spaceapi.net/</a><br>
[2] <a href="http://spaceapi.net/directory.json" rel="noreferrer" target="_blank">http://spaceapi.net/directory.<wbr>json</a><br>
[3] <a href="https://fixme.ch/" rel="noreferrer" target="_blank">https://fixme.ch/</a><br>
[4]<br>
<a href="http://lists.hackerspaces.org/pipermail/spaceapi-devel/2016-April/000157.html" rel="noreferrer" target="_blank">http://lists.hackerspaces.org/<wbr>pipermail/spaceapi-devel/2016-<wbr>April/000157.html</a><br>
[5] <a href="https://github.com/fixme-lausanne/MyHackerspace" rel="noreferrer" target="_blank">https://github.com/fixme-<wbr>lausanne/MyHackerspace</a><br>
[6] <a href="https://www.coredump.ch/" rel="noreferrer" target="_blank">https://www.coredump.ch/</a><br>
[7] <a href="https://github.com/spacedirectory/meta/issues" rel="noreferrer" target="_blank">https://github.com/<wbr>spacedirectory/meta/issues</a><br>
______________________________<wbr>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.hackerspaces.org">Discuss@lists.hackerspaces.org</a><br>
<a href="http://lists.hackerspaces.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.hackerspaces.org/<wbr>mailman/listinfo/discuss</a><br>
</blockquote></div><br></div>