Tue 3 Jun 2014 10:03AM

Diaspora project goal is missing!

D 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 "" and rename "next-next" milestone into "" https://github.com/diaspora/diaspora/issues/milestones
  • Discuss and select one big feature for the release (currently named next-next)
  • Split the one big feature into small subtasks for the release
  • Focus on pull requests related to the release
  • Communicate to the developers about the next release with the new big feature and related subtasks

Rich Tue 3 Jun 2014 10:54AM

Are you looking for a project manager? Or for the possible next steps to be agreed upon? Sorry, I'm not completely sure what the question is :)


diasp_eu Tue 3 Jun 2014 11:49AM

First we should discuss about the current development process model. How we select new features and how we focusing on them. Imho one or more leaders should be responsible for the release planning and developer communication.


Flaburgan Tue 3 Jun 2014 1:12PM

@diaspeu it could be an approach, but it's really different than the way we currently deal with the development. I'm especially surprise by the "Only accept pull requests related to the release". Why would we want to block any contributions?

I think I get your vision here, your point is "let's focus on something specific we all agree and progress step by step". It's not a bad idea, the problem is we are all volunteer, so we just have no idea when we will have time to contribute, develop or release. So all planning is useless, it will not be respected.


diasp_eu Tue 3 Jun 2014 1:21PM

Why would we want to block any contributions? Currently 27 developers working more or less on 40 different pull requests. Let's split a new feature into 27 subtasks and focusing on them.


RAM518 Tue 3 Jun 2014 6:47PM

Basically whoever has access to the main repo is the default project manager. Diaspora has sort of stalled ever since the original dev team broke up and it became a totally FOSS community project. We still don't have chat. Youtube support is still half-broken. There are no group pages yet, no event pages. Lets just focus on the stuff that has been needing to be fixed for years.


Jason Robinson Tue 3 Jun 2014 6:50PM

While there are good ideas in to this approach - I cannot see this kind of planning work with our current developer/contributor base. We have a large project with a large code base and project high project maintenance costs - but only a small amount of developers, and even less other project maintenance people.

Personally I see the current way quite good. Important stuff is labeled as next release and everything else is merged in as it gets ready. The large items are slowly done as fast as people who are interested in working on them get them done.

All the devs who work on this project do it for fun - I don't see how restricting what they can work on will make them write more code ;)

All in all - good ideas and all, but we need more organization to have more stricter development cycles. Of course that is not to say we shouldn't improve and evaluate - that happens all the time, like the decision to go for a 1-2 week merge freeze before a release, just as one example.


Alex Talker Tue 3 Jun 2014 10:26PM

Project leader is nice, but....that man really should do what like community, else is be like slave.


Rich Wed 4 Jun 2014 3:45PM

@jasonrobinson states:

All the devs who work on this project do it for fun - I don’t see how restricting what they can work on will make them write more code

Which is a very valid point - I think we (as end users) are extremely lucky to have people working on this at all. I'd be against something which says "You there, developers, you must do this before that or else" :(

(which is how it may come across, intended or otherwise)


Flaburgan Wed 4 Jun 2014 6:09PM

@ram518 "Youtube support is still half-broken" are you on joindiaspora? If not, we're not aware of that, please open an issue.


diasp_eu Thu 5 Jun 2014 7:45AM

Don't get me wrong. The reason is focus. For example https://github.com/diaspora/diaspora/pull/4410 some nice guys worked together and the new single post view come to live. Sometimes, the issues are too big to be resolved by one man show. Split big features into small subtasks and focus on them.

Load More