Task managment tool - which one should we use?

B2G OS
#1

Hi B2Geeks ! :slight_smile:

Following a discussion on the telegram group, I’m opening a topic here - it will be more easy to follow the conversation :slightly_smiling:

The goal is to choose a system to keep track of task to do / ongoing / done. Having an overview of those task can help people to see the project progress, to have an overview of the status, to avoid forgetting who does what and what remains to do, and so on.

It could be great to have a comparison like for the governance topic, with pros/cons for each software, and how they can fit to our needs.

For instance one option could be to use github issues as a task management software. Which has the default of being non-free, not being more powerful than git, and having a quite bad UI/UX.
If we still want to stay based on git, gitlab can be useful. The issue system is a bit more powerful (but it’s mostly code), and it’s a free software, self-hostable if needed.
I’m also thinking about Kanboard (a Trello alternative) which is quite powerful but the UI is a bit complex and not as pretty as Trello. It has no git bridge as far as I know.

Exploring those options (and the other that you can )

A question here is also if we should/could/need to use Mozilla current system.

Please share your toughs/proposals :slightly_smiling:

#2

Why not use Bugzilla to track issues and tasks? That has been the default at Mozilla for a long time and works pretty decently.

#3

But we saw more user friendly tools ^^
But we have to keep it in mind for the comparison.

Well, in yesterday communication meeting (it’s internal communication) we decided that for the moment we need something to setup in a short time, the final feature is more important than the tool, that we could change for instance in 2 weeks (end of the transition) without taking too much time / loosing much data.
So we’ll took the basic default option, a github repo.

This discussion can still continue, as it will be useful quite soon.

#4

FWIW for the code transition project we’ve been using Pivotal Tracker to create a backlog of Bugzilla bugs https://www.pivotaltracker.com/n/projects/1568715

The Bugzilla integration isn’t great so it’s quite a manual process but a useful tool nonetheless.

Note that B2G actually started out using GitHub issues, but moved to Bugzilla to integrate better with the rest of Mozilla.

What kinds of tasks are you wanting to track which don’t fit into Bugzilla components? Could you capture them in a spreadsheet to start off with? Or create new Bugzilla components?

1 Like
#5

A github repo has been made as a short-term solution, because we really need to have this todo list and the overview of what is done/ is a TODO right now and not in months. This may change in the near future.
Here is the link: https://github.com/ensowhat/B2GOS-community/issues
If I understand well, it’s waiting for an integration into Mozilla repo. (@Valentin can you confirm that ?)

@benfrancis: it’s mostly non-technical related task, like communication, translation, documentation tasks.
As we want to keep it easy to get involved here, and have a fast solution, Bugzilla might not be the best solution right now.
But it’s a choice to evaluate in the future - this repo is a temporary solution.

#6

I created a repo on GitHub:
https://github.com/ensowhat/B2GOS-community/issues

It’s on my account for now, but we’ll move it to:
https://github.com/mozilla-b2g

Please take a look and feel free to assign issues to yourself. :slight_smile:

2 Likes
#7

The repo has been successfully moved to the Mozilla-B2G organization on github!

1 Like
#8