Agilito hackday... or weekend

[Matías Iturburu]

Hi guys:

This is an idea that's in my head for a while now and it's been a while since I have  worked with the team (miss you guys :) so this is what I have in mind:

In terms of features that would be cool to add or improve in agilito:
 - Planning workflow:
      - Easier ranking (may be with drag and drop)
      - "Add to current iteration" sort of thing for user stories.
      - "Log time in this task" for tasks, obviously
 - Real user profiles, with avatars, availability, teams, and so on
 - Project setup public view, so we don't touch the django admin anymore (it makes baby jesus cry quite often)
 - Notifications
 - Improvements to the "hours" page:
      - Statistics
      - Fine grained hours report
  - Project dashboard, with the task I have assigned to me or that I have logged time into.
  - Others that where noted in get satisfaction and in the list but I haven't look when I wrote this.

There is a branch and a bunch of patches from emiliano that needs review too.

So what I propose is to take a day or two in the not much far future (first half of february), set a hq somewhere (may be we can provide this), try to coordinate with people that don't live in Cordoba obviously (Chis, Gerry, ¿Emiliano?), and with people that lives in córdoba but may not be in this list (emanuel, mainly).

The thing is that I don't know how you guys are in availability, I haven't heard of ale or john in quite a long time.

What do you guys think?


ps: it's 3am here so bee cool with criticism :D




    

--
Matías Iturburu
Revoluciones Informáticas
www.revolucionesweb.com.ar
http://www.linkedin.com/in/miturburu

[Emiliano Heyns]

On Jan 15, 6:12 am, "Matías Iturburu" <maturb...@gmail.com> wrote:

> In terms of features that would be cool to add or improve in agilito:
>  - Planning workflow:
>       - Easier ranking (may be with drag and drop)
>       - "Add to current iteration" sort of thing for user stories.
>       - "Log time in this task" for tasks, obviously

Some of these I'm already working on.

> There is a branch and a bunch of patches from emiliano that needs review
> too.

That's pretty important to me -- my patches are stacking up, and I'm
keeping them current agains the trunk (which is dormant at the
moment). I'd rather not be surprised with a lot of work back-merging
these to a different branch. The only branch in svn is "newstyle", and
that hasn't seen much activity recently either.

When is the vote due on my commit access? It's getting harder and
harder to keep my patches neatly separated.

> So what I propose is to take a day or two in the not much far future (first
> half of february), set a hq somewhere (may be we can provide this), try to
> coordinate with people that don't live in Cordoba obviously (Chis, Gerry,
> ¿Emiliano?), and with people that lives in córdoba but may not be in this
> list (emanuel, mainly).

I don't live in Cordoba, no ;) A full weekend is hard to arrange; a
sunday is manageable, after 11:30 CET.

Emile

[Christopher Johnson]

Hey Matias,

Thanks for pulling together the idea! As I mentioned, I am definitely for a sprint day(s) in near term. Items that would be highest priority for me are:
- log time in this task
- review and incorporate Emiliano's changes
- not making baby jesus cry (i guess that means make setup easier!)

I haven't reviewed the GS list yet either, so perhaps we can do that in prep.

I would be fine with weekdays (Thurs/Fri), and possibly could do weekend. As I am not coding, though, may only be needed in chunks.

Cheers,
Chris

--
Cofounder and CEO
ifPeople - Innovation for People
www.ifpeople.net
t: 678-608-3408 x16

[Emanuel Sartor]

On Thursday 15 January 2009 03:12:48 Matías Iturburu wrote:
> - Improvements to the "hours" page:
> - Statistics
> - Fine grained hours report

I'd add:
- Expose this in the GUI:
http://code.google.com/p/agilito/wiki/TaskLogReports

> So what I propose is to take a day or two in the not much far future (first
> half of february), set a hq somewhere (may be we can provide this), try to
> coordinate with people that don't live in Cordoba obviously (Chis, Gerry,
> ¿Emiliano?), and with people that lives in córdoba but may not be in this
> list (emanuel, mainly).

+1

Best,
Emanuel

[Emiliano Heyns]

> Thanks for pulling together the idea! As I mentioned, I am definitely for a
> sprint day(s) in near term. Items that would be highest priority for me are:
>
> - log time in this task

Done.

> - review and incorporate Emiliano's changes

You guys are not keeping up!

> - not making baby jesus cry (i guess that means make setup easier!)

That definitely needs work.

> I would be fine with weekdays (Thurs/Fri), and possibly could do weekend. As
> I am not coding, though, may only be needed in chunks.

While I approve of the idea in general, I would be happy to see some
activity in the meantime; review of the stuff I've been committing,
more talk about priorities and new functionality. Is anyone else
currently working on stuff? I'm thinking it would be useful to set up
a backlog, so we can discuss priorities.

Many of the things that I needed immediately I have now done. The next
cluster of work, for me, would revolve around adding archival
functions (some already added) so agilito can be used to track long-
term team performance, and to be able to look back to what has been
done and how we got here. The current implementation seems to aim more
towards the "now", which is obviously important, but deleting tasks
and userstories (with all the task logging and test results and
whatnot attached) destroys important information.

So here's something I could use some input on: if you re-assign the
iteration a story belongs to, you'll most likely want to delete the
attached tasks, etc, or it wouldn't be very useful in the new
iteration. I would suggest that editing a story would work as usual,
but that changing the assigned iteration for a story that has tasks
assigned to it would actually create a basic copy of the story,
without the task and/or attachments.

Thoughts?

Emile

[Emiliano Heyns]

On Jan 24, 9:36 pm, Emiliano Heyns <Emiliano.He...@gmail.com> wrote:

> > - review and incorporate Emiliano's changes
>
> You guys are not keeping up!

...

> Many of the things that I needed immediately I have now done. The next
> cluster of work, for me, would revolve around adding archival
> functions (some already added) so agilito can be used to track long-
> term team performance, and to be able to look back to what has been
> done and how we got here. The current implementation seems to aim more
> towards the "now", which is obviously important, but deleting tasks
> and userstories (with all the task logging and test results and
> whatnot attached) destroys important information.
>
> So here's something I could use some input on: if you re-assign the
> iteration a story belongs to, you'll most likely want to delete the
> attached tasks, etc, or it wouldn't be very useful in the new
> iteration. I would suggest that editing a story would work as usual,
> but that changing the assigned iteration for a story that has tasks
> assigned to it would actually create a basic copy of the story,
> without the task and/or attachments.
>
> Thoughts?

You guys are still not keeping up. If it makes sense that I work on a
different branch in the repo that's find by me, and that would allow
me to do as I please without disturbing existing functionality or add
new dependencies (pyExcelerator, matplotlib); django/python allows me
to get stuff done fairly quickly (and hooray for that), and I can't
hold off changes that might affect existing behavior for very much
longer, and if discussion is not going to take place we have three
options:
* (my) development effectively comes to a halt
* I go on a separate branch and do as I please
* I stay on the trunk and do as I please

Since I promised to behave I'm putting out a request to create a
situation that allows me to behave while still moving forward.

If I'm going on a separate branch I would kindly request that someone
volunteers to do the merge work. I have too little experience with
branching and merging, so I might muck it up, and the little
experience I do have with it was not a particularly pleasant one. I'd
rather use that time to add features.

Also, there was talk about adding more unit tests, has that seen any
updates that aren't checked in? I'd love to have more testing in
place.

Regards,
Emile

[John Lenton]

by all means, please feel free to do anything you please on a branch.
As long as it's legal :).

I'm afraid I'll have zero time for agilito until the project I'm on
gets to beta; probably another month. It was supposed to be before
that, but I don't see it as realistic right now.

--
John Lenton (jle...@gmail.com) -- Random fortune:
The trouble with a lot of self-made men is that they worship their creator.

[Emiliano Heyns]

On Jan 30, 6:24 pm, John Lenton <jlen...@gmail.com> wrote:
> by all means, please feel free to do anything you please on a branch.
> As long as it's legal :).

Let's just take that as a given... and let's discuss the practical
merits of branching at this moment. Subversion makes branching
deceptively easy; merging is, however, a horrible mess, and cherry-
picking nigh impossible. Unless someone steps up go volunteer for
this, it's just simply not going to happen, and if so, why bother?

If we were branching to prevent concurrent conflicting developments,
I'd understand, but then I could merge frequently and avoid the pain
of a huge merge. What we're discussing right now is imposing this work
on me simply so we'd have the option of nixing my work possibly months
down the line simply because noone can spare the time to even discuss
the work I'm volunteering. That doesn't sound like a good proposition
to me.

At the very least, if we're serious about branching, we should switch
to a versioning system that makes this tolerable. I am as yet
unconvinced this will yield any practical benefits, but if anyone is
willing to share the burden, I'll consider it. If not, for all intents
and purposes this branch would effectively be a fork that just happens
to live in the same repo.

> John Lenton (jlen...@gmail.com) -- Random fortune:

[John Lenton]

On Fri, Jan 30, 2009 at 15:59, Emiliano Heyns <Emilian...@gmail.com> wrote:
>
> Let's just take that as a given... and let's discuss the practical
> merits of branching at this moment. Subversion makes branching
> deceptively easy; merging is, however, a horrible mess, and cherry-
> picking nigh impossible. Unless someone steps up go volunteer for
> this, it's just simply not going to happen, and if so, why bother?

ok, instead of branching, tag the current trunk, document that that is
what works (more or less) as documented, and work on trunk.

How does that sound?

--
John Lenton (jle...@gmail.com) -- Random fortune:

[Emiliano Heyns]

On Jan 30, 7:10 pm, John Lenton <jlen...@gmail.com> wrote:

> On Fri, Jan 30, 2009 at 15:59, Emiliano Heyns <Emiliano.He...@gmail.com> wrote:
>
> > Let's just take that as a given... and let's discuss the practical
> > merits of branching at this moment. Subversion makes branching
> > deceptively easy; merging is, however, a horrible mess, and cherry-
> > picking nigh impossible. Unless someone steps up go volunteer for
> > this, it's just simply not going to happen, and if so, why bother?
>
> ok, instead of branching, tag the current trunk, document that that is
> what works (more or less) as documented, and work on trunk.
>
> How does that sound?

That works for me, and it's now tagged in svn. I'll continue to post
plans on potentially behaviour-breaking changes before committing
them, but if no significant feedback comes I must assume it doesn't
upset anyone, so I can check it in.

Fair?

Emile

[John Lenton]

On Fri, Jan 30, 2009 at 17:15, Emiliano Heyns <Emilian...@gmail.com> wrote:
> I'll continue to post
> plans on potentially behaviour-breaking changes before committing
> them, but if no significant feedback comes I must assume it doesn't
> upset anyone, so I can check it in.
>
> Fair?

works for me. Worst case scenario is I awake a month from now in a
rampage and roll everything back to 1997.

It ain't going to happen :)