Re: Project status and proposal

[Alexandre Franke <afranke gnome org>]

On Thu, Aug 3, 2017 at 7:25 PM, Gonzalo Aguilar Delgado
<gaguilar aguilardelgado com> wrote:
> Hello all,

Hi,

> It seems you are in the road to rewritting this wonderful piece of software
> that so many happines gave me in the past. So I can see if I can do
> something for the tool. Since the Gantt chart seems to be a problem I
> propose:
[…]
> What do you think?

As I suggested earlier, the way forward is to make it a bunch of GTK+
widgets (i.e. the whole chart is a widget containing widgets that each
represtent tasks, milestones…).

> I also moved to meson all my projects for building. The difference is GREAT.
> Compilation times and manageability are exceptional. And you don't have to
> wait 20 minutes for a build... I think it would be a win. Everyone is also
> moving.

Yes, meson is the hip thing and could be the way forward. However it
does not play nice for now with Python+C (+FlatPak) projects and there
is no rush to do that.

> About the use of Vala... will you reconsider it?

No.

> Lot of wonderful projects
> are written in vala (gnome-builder for instance) and it's working nice.

Builder is not written in Vala. You need to do better research.

> And no I don't think it will dissapear. Specially if we use it.

I couldn’t care less if it disappeared. I cannot recommend that anyone uses it.

> About new features... I think the same than Andrew Miloradovsky. Maybe is
> not time for it. But giving a chance for new features it can give a boost to
> the project (but also kill it :-( ). Maybe new developers join... So we can
> propose, then it should be implemented... if possible.

Patching new features into legacy code is bad practice, a waste of
time and energy, and just increases the amount of work.

> Add a Kanban style chart for the tasks. Grouped on milestones and with
> status depending if it has a resource or not, but also if someone has
> advanced it based on progress.

You’ll have to explain how to map kanban swimlanes and columns map to
Gantt concepts. I think there is a clash between the methodologies
those tools support and I am not convinced a single tool should
contain both. I do use both, but in different contexts.

> Add Scrum backlog based on the tasks. And maybe grouped on sprints.
> Some progress reporting reports would be nice to have.

I haven’t used Scrum backlogs, but they seem similar to kanban boards
so the same concerns apply.

> This could be a great win for the project and merging the best of both
> worlds can be a win. Cause the tools I see for Agile are specific for it.
> Not using a merge of Agile and traditional. And can give the project new
> visibility.

How about we make it great again for traditional planning first, then
see where we can go from there?

Cheers,

-- 
Alexandre Franke
GNOME Hacker & Foundation Director