Re: Project status and proposal

This is a multi-part message in MIME format.
--===============4155336491601552608==
Content-Type: multipart/alternative;
 boundary="------------02DEFC812F988ABF447F54E6"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------02DEFC812F988ABF447F54E6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Alexandre,

I cannot be more aligned with you except for the vala stuff.

For the gnome-builder you were also true. I mistakenly confused myself
because was investigating the vala-pack plugin that's written in vala,
but that's just one plugin. baobab is written in vala and working well,
but anyway.=20

Once we do the migration stuff of the critical stuff. We can start a new
thread for the kanban and scrum.

But first, let's clean the code out if you agree. I will start trying to
make a gantt widget with new components and avoid legacy code as much as
possible.

Any guidelines, or points to examples of similar widgets will be welcome.=


I have to write some widgets for a system I'm developing so this will be
treated as a conceptual UI reasearch under GTK. That way I can work on
it while get paid.

Let me start. I will open a bug report (if it's not already open) and do
a branch for the update.

Do you agree?

Best regards,


El 03/08/17 a las 20:19, Alexandre Franke escribi=C3=B3:
> On Thu, Aug 3, 2017 at 7:25 PM, Gonzalo Aguilar Delgado
> <[email protected]> wrote:
>> Hello all,
> Hi,
>
>> It seems you are in the road to rewritting this wonderful piece of sof=
tware
>> 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:
> [=E2=80=A6]
>> 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=E2=80=A6).
>
>> I also moved to meson all my projects for building. The difference is =
GREAT.
>> Compilation times and manageability are exceptional. And you don't hav=
e 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=
=2E
> 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=E2=80=99t 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 bo=
ost to
>> the project (but also kill it :-( ). Maybe new developers join... So w=
e 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=E2=80=99ll 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=E2=80=99t 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 n=
ew
>> visibility.
> How about we make it great again for traditional planning first, then
> see where we can go from there?
>
> Cheers,
>


--------------02DEFC812F988ABF447F54E6
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000099" bgcolor="#FFFFFF">
    <p><font face="Helvetica, Arial, sans-serif">Hi Alexandre, <br>
      </font></p>
    <p><font face="Helvetica, Arial, sans-serif">I cannot be more
        aligned with you except for the vala stuff. <br>
      </font></p>
    <p><font face="Helvetica, Arial, sans-serif">For the gnome-builder
        you were also true. I mistakenly confused myself because was
        investigating the vala-pack plugin that's written in vala, but
        that's just one plugin. baobab is written in vala and working
        well, but anyway. </font></p>
    <p>Once we do the migration stuff of the critical stuff. We can
      start a new thread for the kanban and scrum. <br>
    </p>
    <p>But first, let's clean the code out if you agree. I will start
      trying to make a gantt widget with new components and avoid legacy
      code as much as possible. <br>
    </p>
    <p>Any guidelines, or points to examples of similar widgets will be
      welcome. <br>
    </p>
    <p>I have to write some widgets for a system I'm developing so this
      will be treated as a conceptual UI reasearch under GTK. That way I
      can work on it while get paid. <br>
    </p>
    <p>Let me start. I will open a bug report (if it's not already open)
      and do a branch for the update. <br>
    </p>
    <p>Do you agree?</p>
    <p>Best regards,<br>
    </p>
    <br>
    <div class="moz-cite-prefix">El 03/08/17 a las 20:19, Alexandre
      Franke escribió:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJ-e=JCZTm_4HE-yegP5oFA3Y6V+LWsghZsmHXQSfRhFDT70aw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org">
      <pre wrap="">On Thu, Aug 3, 2017 at 7:25 PM, Gonzalo Aguilar Delgado
<a class="moz-txt-link-rfc2396E" href="mailto:[email protected]">&lt;[email protected]&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hello all,
</pre>
      </blockquote>
      <pre wrap="">
Hi,

</pre>
      <blockquote type="cite">
        <pre wrap="">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:
</pre>
      </blockquote>
      <pre wrap="">[…]
</pre>
      <blockquote type="cite">
        <pre wrap="">What do you think?
</pre>
      </blockquote>
      <pre wrap="">
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…).

</pre>
      <blockquote type="cite">
        <pre wrap="">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.
</pre>
      </blockquote>
      <pre wrap="">
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.

</pre>
      <blockquote type="cite">
        <pre wrap="">About the use of Vala... will you reconsider it?
</pre>
      </blockquote>
      <pre wrap="">
No.

</pre>
      <blockquote type="cite">
        <pre wrap="">Lot of wonderful projects
are written in vala (gnome-builder for instance) and it's working nice.
</pre>
      </blockquote>
      <pre wrap="">
Builder is not written in Vala. You need to do better research.

</pre>
      <blockquote type="cite">
        <pre wrap="">And no I don't think it will dissapear. Specially if we use it.
</pre>
      </blockquote>
      <pre wrap="">
I couldn’t care less if it disappeared. I cannot recommend that anyone uses it.

</pre>
      <blockquote type="cite">
        <pre wrap="">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.
</pre>
      </blockquote>
      <pre wrap="">
Patching new features into legacy code is bad practice, a waste of
time and energy, and just increases the amount of work.

</pre>
      <blockquote type="cite">
        <pre wrap="">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.
</pre>
      </blockquote>
      <pre wrap="">
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.

</pre>
      <blockquote type="cite">
        <pre wrap="">Add Scrum backlog based on the tasks. And maybe grouped on sprints.
Some progress reporting reports would be nice to have.
</pre>
      </blockquote>
      <pre wrap="">
I haven’t used Scrum backlogs, but they seem similar to kanban boards
so the same concerns apply.

</pre>
      <blockquote type="cite">
        <pre wrap="">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.
</pre>
      </blockquote>
      <pre wrap="">
How about we make it great again for traditional planning first, then
see where we can go from there?

Cheers,

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------02DEFC812F988ABF447F54E6--

--===============4155336491601552608==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
planner-dev-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/planner-dev-list

--===============4155336491601552608==--