Diaspora project goal is missing!
diasp_eu
Public
Seen by 124
Two years ago Max and Daniel left the project as core contributors. Since that time the diaspora development goes on (thanks) but without a specific goal. A project without a goal is a project without success. For example 10 month ago: https://www.loomio.org/d/VMg5HlpZ/diaspora-the-next-12-months
How to tackle this issue?
We should change the process model. Someone should be responsible for planning the next release and communicating about it. We know the wish list is long enough to pick one feature for the next release. Let's focus on one feature for the next release and work together on it. I believe we can make more progress towards our goals (to be defined).
Next steps?
- Rename "next" milestone into "0.4.0.0" and rename "next-next" milestone into "0.5.0.0" https://github.com/diaspora/diaspora/issues/milestones
- Discuss and select one big feature for the 0.5.0.0 release (currently named next-next)
- Split the one big feature into small subtasks for the 0.5.0.0 release
- Focus on pull requests related to the 0.5.0.0 release
- Communicate to the developers about the next 0.5.0.0 release with the new big feature and related subtasks
diasp_eu Thu 5 Jun 2014 9:41AM
@flaburgan I like the hack together idea at same time. But because of timezone the work packages should be selected, described and prepared for the next release.
Steffen van Bergerem Thu 5 Jun 2014 1:38PM
@diaspeu Working together on the new SPV was a nice example how working on diaspora* could look like. There was no real plan to do it. We all talked about changing the SPV but there was one dev who started working on that and did a lot of nice work. Then others came across and helped. The same thing could happen for chat or groups. We "just" need someone to start working on that issue and spend some time to get the basic stuff done.
diasp_eu Sun 15 Jun 2014 1:18PM
@steffenvanbergerem Why something happens like https://github.com/diaspora/diaspora/pull/4554
goob Sun 15 Jun 2014 4:48PM
@diaspeu That's because of a lack of people qualified to review that code rather than a lack of a goal. Everyone on the project thinks of an API as a priority goal, so it's not been left because no one cares. We need more developers!
Flaburgan Mon 16 Jun 2014 7:54AM
We need more developers!
I think every discussion about the project will finally arrive to that point. So let's focus on communication and make the project innovative and sexy again.
Flaburgan Mon 16 Jun 2014 8:18AM
At the moment this is the kind of message we can post, even if only one person start contribute after reading it, it's already a victory.
In the future, I think a good idea would be to write an official blogpost to definitely kill all false idea about the project (founders went in vacation with the money, etc...) (yeah, I heard this one more than once). Something like "the real history of the diaspora* project", explaining everything the founders never talked about when they probably should. Once this will be done, we can start again on solid foundation.
Jason Robinson Mon 16 Jun 2014 8:22AM
Well put @flaburgan
Share and talk to the world - everybody! :)
Sean Tilley Mon 16 Jun 2014 2:45PM
@flaburgan Incidentally, I am working on a personal post that talks about everything that the project went through, from being a startup to pivoting to a community-run organization, and everything that happened between those periods.
I plan on posting it as soon as it gets finished; it's kind of a long story, but I'd like to think that it's a really good one. :)
Flaburgan Mon 16 Jun 2014 3:22PM
Nice Sean :)
Looks like some people already heard my message: https://diaspora-fr.org/posts/439692 :)
Flaburgan · Thu 5 Jun 2014 9:30AM
@diaspeu the work "all together" on the new SPV was awesome, and we all want to see that happen again. In my opinion, the best way to do that is to coordinate ourselves like "let's all block next thursday to work on diaspora*, meet on #diaspora-dev and hack all the evening together". If we success to plan something like that, then it makes sense to prepare the work to do by choosing a task, splitting it in subtask and affect them to a volunteer, etc. But to prepare the work without having a work time planned is useless imo.