Loomio
Sat 29 Dec 2012

TODO List

F
Flaburgan Public Seen by 119

Hi everyone, hope you have a great winter break.

I was thinking about how we are organized, and I find that, things aren't clear. We need a place to present explicitly what we plan to do, what energy we are putting on and if it will be available soon.

If I ask what are the feature on the launch right now, we have to scroll github, looking at thread, ask people if they still work on it... This can't be okay..

Maybe we should at least define a roadmap and choose what will be available in which version, even if we are not able to put a date on the release.

For example, the single post view which is totally buggy, everyone says that it will be strip / replace by the older version, but who is working on that ? When will it be done ?

E

Elm Sun 30 Dec 2012

I totally agree with you.

D

diasp_eu Sun 30 Dec 2012

C

Christophe Sun 30 Dec 2012

Please don't create another wishlist.

E

Elm Mon 31 Dec 2012

The github page is not clear to me. Too technical.

@christophe : I do not thinks that @flaburgan meant to make a new wishlist…

F

Flaburgan Tue 1 Jan 2013

@christophe I mean a roadmap, not a wishlist. @seantilleycommunitymanager wrote some times ago a todo list with things like "put federation on a layer", "create an official structur like a foundation" etc. My point is, we need to know who is working on what, what is the progress, where we need help...

TS

Tom Scott Thu 3 Jan 2013

We have a todo list. https://github.com/diaspora/diaspora/issues

As @diaspeu has said, we should be using Milestones to visualize which features are going to make it into each release.

@flaburgan your point about single post view needs its own thread. adding.

F

Flaburgan Thu 3 Jan 2013

Tom Scott, github is great for the code. What about make a foundation, translation, communication, things around like the official site, the wiki, a forum, a mailing list...

JL

Jon Lemmon Fri 4 Jan 2013

I'm not sure if this is a good idea for you guys, but we use Trello a lot for working on Loomio and we really like it. As an example, here's our main high-level development board for keeping track of what we're working on. I think github milestones might already solve this problem for you though.

However, for non-code stuff I think Trello could possibly work for you. It's worth checking out at least. Although, I've found that keeping track of things you'll never get to can be counter-productive. =)

TS

Tom Scott Fri 4 Jan 2013

@flaburgan we have a wiki on github. we have a "forum" here. we have a mailing list on google. github's issue tracker is good for us in a number of ways:

  1. People are expecting to post issues there. It's the first place we tell people to go when they make bugs.
  2. There are ways to categorize issues into feature requests, bugs, etc., give them importance, and attach them to a milestone
  3. Almost every other big project (including Rails and RSpec) uses Milestones to track development progress. Why don't we?

What exactly is the problem we are trying to solve here?

F

Flaburgan Fri 4 Jan 2013

As not a lot of people contribute, github can be enough. I knew trello, this is a good tool, but another tool will be too many.

DU

[deactivated account] Sat 5 Jan 2013

I see very little use of milestones in GitHub. 0.0.3 has 3 open tickets and 0.1 one.

Imo more delegation + use of milestones would solve this issue at hand.

I don't really see the point of another to-do list. The workflow could be:

suggest / discuss new ideas on loomio, merge successful proposals / good ideas into github issues. Decide on a roadmap (aka milestones), then move tickets into milestones.

Downside is: too many tickets might mess up the focus on a milestone. Maybe milestone and tags like p1-3 for priority and "beginner" (as already used) would be helpful.

+1 for the current system and let's make better use of existing platforms.

DU

[deactivated account] Sat 5 Jan 2013

Speaking of: e.g. for this beginners issue there's a volunteer. How could he be assigned? Only admins can do that? Sure we could also wait until he delivers some code, but why not assign him and have that info that this issue is assigned available in the overview?
https://github.com/diaspora/diaspora/issues/3795

EG

Erwan Guyader Sat 5 Jan 2013

As @flaburgan said, Github issues and milestones are good for development but they're not suited for other stuff like Translation, Communication, Legal issues, ...
A wiki page might enough but we need something to list everything we have to do, who's working on it, what's been done, ...

E

Elm Sun 6 Jan 2013

This info should be easily accessed from the http://diaspora-project.org/ web page.

A bit like this page : http://libertreeproject.org/roadmap/

but with some more info such as a simple progress bar (with indication of time).

That would be a good communication arguments to tell that D* is not dead if people can see the progress this way because not many things have changed since one year for D* (at least from the user perspective) : same bugs, same lack of features…

FS

Florian Staudacher Tue 8 Jan 2013

from the dev-perspective the github milestones are enough. (yes, there simply isn't any more going on, than you see in the current milestones - apart from open pull requests).
Apart from that, I'd rather not start using another tool, until we really need it.

F

Flaburgan Fri 25 Jan 2013

Okay so I simply created a page on the wiki. @seantilleycommunitymanager I could be a good place to keep trace and progress about what is done :)

F

Flaburgan Tue 12 Mar 2013

Here are some bugs which need to be fixed because really annoying. It's these bugs which keep this impression of non stable in Diaspora.

  1. Send profile update (the profile of a person is not the same from different pods : one did not receive an update) #3976

  2. Pictures are not always federated with posts Loomio discussion #3940

  3. The stream does not contain every posts of every aspects #3786

  4. Refactoring the single post view Discussion on loomio, #3942

I think we should focus on these bugs and if we correctly deal with all of them, Diaspora can be announced as v0.1.0.0

L

L3MNcakes Tue 19 Mar 2013

I'm happy to help squash those bugs. C= Could somebody link me to somewhere I could read up on the federation protocol?

F

Flaburgan Tue 19 Mar 2013

you can find a lot of useful info on wiki.diaspora-project.org

DU

[deactivated account] Sun 31 Mar 2013

I would look at Pivotal Tracker http://www.pivotaltracker.com/ or the open source clone: Fulcrum http://wholemeal.co.nz/projects/fulcrum.html
I really like the idea of piles of things (Icebox for anything, Backlog for things that are ready to be worked on, and Current for things that are in progress).

F

Flaburgan Tue 2 Apr 2013

We already brainstorm about that and we agreed that having too many platforms is not good for new members integration. So github + loomio + diaspora itself should be enough.

N

Nick Sat 15 Jun 2013

Hey, I would agree that a roadmap is quite important, to convince members that diaspora is actively in development.

I've attempted to check out the pivotal tracker on a few occasions with no success?

Why not have a roadmap page on the wiki?

F

Flaburgan Thu 18 Jul 2013

I updated the todo list page on the wiki, it could be great to maintain it.

ST

Sean Tilley Thu 18 Jul 2013

The problem with Pivotal Tracker is that it doesn't scale very well to community development. It's really better designed for small teams of people that are all working together in the same room.

I wouldn't be against using something like Trello for task tracking, but as fla pointed out, we don't want to have too many platforms all at the same time.

DU

[deactivated account] Sun 21 Jul 2013

Is this really an open issue? I think current structure with GItHub, revamped https://diasporafoundation.org/, Wiki and Loomio is sufficient. Can we close this?

G

goob Sun 21 Jul 2013

Wilhelm, a 'to do' list or road map is different from Github issue tracker, the project site, or Loomio discussions. It's a tool for strategic planning ahead rather than reactively, making and maintaining a list of the items that are considered crucial to the project's success so that they can be planned, worked on and implemented.

DU

[deactivated account] Sun 21 Jul 2013

Goob: Understood. But we do have a wiki. Why not use that?

G

goob Sun 21 Jul 2013

The to-do list is on the wiki!

But a wiki is no good for discussion or proposals, which is what Loomio is good for. Each platform has its own benefits and drawbacks, and we should use each for the things which they are best at.

F

Flaburgan Mon 22 Jul 2013

@wilhelm my message was only to point that I updated the todo list and I encourage devs to add / modify the topics which should be treated in priority.