Loomio

Workflow documentation is outdated.

Nicolas Wormser PublicSeen by 42

Hey guys, I'm progressively settling down and starting working on app development, and I'm a bit lost with our current workflow, and the documents on our Open docs are not helping whatsoever.

First reason why I'm a bit lost is that from what I've understood we're moving away from Trello, but some activity is happening there on the "What we're working on" board. Is that we just replaced the "behind the scenes" with Github issues board but that we're keeping the other boards for all non code-centric stuff? That would make sense I think because I'm finding the Kanban view really helpful to visualise where we're at.
But then why the "Change log" board is not getting updated anymore?

Have I missed a discussion or a document that is updated with the current workflow?

mix irving

Hey @nicolaswormser , my understanding is we're using github for issues/ bug reports and feature requests. There is a deliberately less technical discussion of features on loomio.

Rich and I recently updated the github wiki with some details and a juicy diagram, though you're probably already onboard with that stuff

Nicolas Wormser

Thanks @johnirving.

I guess what feels weird to me then, is that if we use the process described in the wiki, we don't have any feature-level visualisation of the progress we're making, which the "What we're working on" Trello board was providing.

I also think that the Trello board is a much more convenient way to see quickly who is working on what, and what the priorities are, because github task tracker is very messy (which is normal because it is task-level and not kanbanized).

Can anyone confirm that we're still using "What we're working on" Trello board, if it's everyone using and looking at it or just a few people?

mix irving

@jonlemon was talking about a plugin that would make github look more like trello. I'll ask him about that today

Jon Lemmon

Update

We've all had a discussion about this this morning and here's the conclusions we've come to:

We are going to keep the Trello board as a high-level overview of what we're working on and upcoming features.

Meanwhile, we'll continue to use Github for bug-tracking and smaller issues/improvements that do not fit on the Trello board.

We're planning to have a meeting on Monday (tentatively) to have a look through the Trello board again and get it up-to-date with our latest thinking and business needs.

We're also going to start having weekly meeting with dev + business team to prioritise/allocate tasks for the week.

@nicolaswormser @johnirving @richarddbartlett @benjaminknight

Jon Lemmon

I've created a wiki page documenting this basic process. I wasn't really sure where to link it to within the rest of the documentation though.

Nicolas Wormser

Hell yeah! This sounds much better to me.

@johnirving - Yeah, Huboard(the Kanban visualisation tool for GH tracker) is actually quite helpful to me.

mix irving

awesome, thanks for pointing out a need for clarity @nicolaswormser, has helped stimulate conversation moving us in the right direction. I duplicated this workflow in the wiki (page 2)

ran it by richard, feel free to edit

Aaron Thornton

@johnirving nice work on that documentation. Very readable for new people coming on.

Josef Davies-Coates

How does one gain access to view the Trello Board?

Josef Davies-Coates

@richarddbartlett ah, OK, thanks for the info. Would love to know more about the decision that lead to leaving Trello for Pivotal. Even more, I'd love the Enspiral lot to pick and develop/ maintain Bettermeans which is a RedMine fork that works very similar to Pivotal Tracker and has a lot of other nice stuff thrown in too.

This also relates to this new discussion here: https://www.loomio.org/discussions/5164

Aaron Thornton

Bettermeans look like a great fit for Loomio and its principles, much beeter name too :) @jonlemmon what do you say?

Richard D. Bartlett

From my perspective @josefdaviescoates, the killer feature that Pivotal has over Trello is that it is opinionated. Velocity tracking forces us to really think about value delivered to end users as our primary measure.

The team is responsible for so many other things (UI/UX design, testing, bug fixes, system administration, professional development, etc...), without velocity tracking we found it is quite easy to go a whole week working on all this stuff and not delivering anything of immediate value to end users.

It's just part of a general 'tightening up' of our processes, to be much closer to formal Scrum methodology. It's only been a couple of weeks but I reckon we're all enjoying the transition. Ask me again in a couple of months though :)

I am pretty ignorant about Bettermeans - @strypey do you have any insight? I have to say this makes me nervous.

Danyl Strype

Meshed checked out BetterMeans (currently using RedMine), and yes @richarddbartlett it appears to be a dead project, although I have heard on GITHub that sometimes a project lives on through a fork, due to a benevolent dictator (or small core team) dropping out without a handover. Is there any way on GITHub to see a list of forks of a given project, and their activity levels?

Danyl Strype

@richarddbartlett This is cool! Not sure if it's what I had in mind though. According to this blog, that graph maps commits back to the original project. This article, 'On Citizenship in Open Source Software' mentions that sometimes a fork becomes the de facto main branch, due to a lack of formal handover, and contributors end up committing new code there, rather than on the official project.

For example, I notice on the MockDeep fork there is something that was "authored 3 days ago"