This President's Day holiday I'm firing up my #ruby and #kotline dev VM for the first time since July, patching, and updating sources to get my #diaspora API based blog comments code running now that that code is running (in beta) on
Ohai there, friends! Sorry for the bit of silence in the last couple of months, we don't like that either, so we figured it's time to make some noise! A few moments ago, we merged the API branch into develop, which means that starting now, all pods
... show more
This is awesome news! Can’t wait to fire up my blog comments system and to integrate into a desktop social media app I am writing.
Ohai there, friends! Sorry for the bit of silence in the last couple of months, we don't like that either, so we figured it's time to make some noise! A few moments ago, we merged the API branch into develop, which means that starting now, all pods on the develop branch support the new, fancy API!
Note that this is not a stable release yet. Until diaspora* 0.8.0.0 is officially released, this API is not considered stable, and we might change things at any time without notice to improve usability and stability. We plan on reaching a stable point once we push 0.8.0.0 into release, but we will communicate as soon as we consider the API stable. Consider it experimental until then. :)
Please do check out the API documentation if you want to know what you can do with the API, and how to use it. We're looking forward to your ideas, and we're curious what you will build with it.
If you had plans for an application using the API, now is a great time to start working on that. We know that we said the API is not stable yet, and that's true, but your feedback will help to improve the API and polishing it for a stable release. If you do find bugs where diaspora* does not behave like you'd expect from reading the API documentation, please file a bug on diaspora* so we can iron that out. If you have an idea for an improvement or you think we should change something within the API, please open a bug on the API documentation. For all other kinds of questions and input regarding the API, we created a new category on Discourse, so please join us there! :)
I woke from a dream where the #diaspora API was being deployed (which I think may actually be happening soon, right #diaspora-dev ?) so I revived my website comments system based on the API, polished up the #kotlin implementation, and then also wrote a #dotnet version so I could make an #fediverse app in #AvaloniaUI . Yeah I'm in a coding mood :).
Dove into some #diaspora code for the first time in forever to help someone figure out how to do something. I do enjoy that code base immensely even if I haven't worked in it for many months #programming #ruby
Are you willing to contribute some money to help diaspora\*s development?
Hey awesome diaspora* community! Today I'm asking you a very special question. At the moment, the development speed of the diaspora* project is quite slow. It looks like this is not only because not many people are interested in contributing to diaspora*, but also because the volunteers who compose the core team don't have enough time to do the review work needed, adding more delays to everything.
The core team is doing all lot of background work. They maintain all the official services: the website, the HQ pod, our Discourse and the wiki. They do the sysadmin job of installing and keeping those services up to date, but they also are the moderators who fight spam. They answer many questions and help developers, podmins, and users. They do the release management and push out new versions of diaspora*. But most important of all, they are the ones doing the final reviews, the very important task of checking the code submitted by other contributors, helping them improve the code, and then integrate it inside diaspora* for everyone.
This is a lot of work, and even if it is less visible than new features, this work is critical because if it is not done, the project is stuck.
We unfortunately reached a point where the limited time of the core team as volunteers slows down the diaspora* development. Two very important features, the accounts migration and the API, are waiting for a review for several weeks while the core team currently is busy with all the tasks listed above, as well as other tasks like the creation of a new official website. To go forward, the diaspora* project needs someone from the core team to be dedicating more time to these diaspora* background jobs at least a couple of hours per month more.
So, to the important question...
If a diaspora* core team member would set up a Patreon or something similar that allows them to fund more time to do the maintenance and review work, would you contribute to that fund?
A big warning here: This is not about paying someone to be able to decide what they will be working on. There is BountySource if you want to support the development of specific features with money. This is about allowing someone to have some dedicated time to work on the maintenance tasks of the diaspora* project, mainly reviews. This core developer will be the one who will choose how they will spend their time, most of the time. But as the core team members are the ones who are the most aware of what's going on with the project, I think we can trust them to do the best choices to improve diaspora* development speed.
So, would you give a few bucks monthly? I would totally do!