webdpack example

@josefdaviescoates - thanks.

https://github.com/benweet/stackedit might not be what @jonrichter was talking about. He said,
"make sure to use http://stackedit-beta.herokuapp.com ".

Kanban boards are nice, but we are also developing kanban-like signals for P2P coordination.

@josefdaviescoates - is the OpenApp gang still using waffle.io? I thought they had quit...?

@bobhaugen no idea if waffle.io actually still being used by this group but it was in this group that I first heard about it - perhaps they were just having a play? /me shrugs

re: stackedit, I'm assuming http://stackedit-beta.herokuapp.com/ is just the stackedit code @jonrichter has got up and running himself there for people to try it out, but I could be wrong :)

@josefdaviescoates - I didn't see the lovely sequence diagram feature in the github repo, but then I could be blind. I assume @jonrichter will set us straight...

we're using scrumdo for the cobudget-ui app and I'm using waffle lots for dev academy.

@bobhaugen @josefdaviescoates

When you go to StackEdit.io and use the # menu to access the About page, you'll find the link to StackEdit 4 beta in the upper right of the overlay.

The Herokuapp is therefore the "official" deployment for its next version. Which eventually includes the flowchart and sequence diagram JS.

Huboard is OSS, too: https://github.com/rauhryan/huboard .

Until I have proper star management at GitHub [1] you can scan my Stars [2] for two more GitHub-based Kanban integrations somewhere near Huboard. Also [3].

[1] https://github.com/bollwyvl/fragile/issues/10
[2] https://github.com/stars/almereyda
[3] https://github.com/stars/almereyda?q=kanban

Thanks Jon.

@jonrichter (or anybody) - I'm confused about something. Do you know how the word "kanban" changed from being a production coordination signal to being a visual display of information?

I worked in manufacturing and supply chain systems when pull signals were revolutionary. Kanban at that time meant the signals, which were usually either cards or labelled tote bins. But they were one small part of the Toyota Production System. Now they are Kanban Boards, and according to this, seem to encompass a whole system. http://agilelion.com/agile-kanban-cafe/open-kanban

What did I miss? (I also lived through most of the development of agile software methods from the beginning when it was just a hint in some Kent Beck emails, so it's not that...)

@bobhaugen Underneath it all, Kanban is a system, as you say. However, there has been liberal interpretation of the system (particularly by the "Lean" people), which has resulted in the various display models. For those who don't know, Kanban works by constraining work in progress (WIP) by using a "pull" mechanism rather than "push". The constraint can be represented as a simple number, but many prefer to represent it using spatial means. For example, if you wanted to limit WIP to four jobs, you set up cards (representing jobs) that are a fixed size and you create a box that is only big enough to hold four of them.

To many people, their only exposure to Kanban is the visual representation, which they are able use without understanding the underlying constraint mechanism. Hence, many misunderstand Kanban as being a simply information visualization tool, rather than a system.

I think that this is how the evolution occurred, but I'm afraid I cannot say that I've been studying this evolution too closely, so I may have missed some key steps.

@craigtaubeschock - that all makes sense to me (as an evolution of a concept, but in the original TPS, kanban was not the system itself, it was a small but important part of the system. Now it has apparently become the name for a system, and the original meaning of a pull signal has apparently been lost). (Edited that paragraph to clarify what made sense to me and what did not.)

The other part of pull signals, besides the limit on WIP, is the coordination of processes. A pull signal tells me to do something. Without a pull signal (if I am working in a pull system), I clean the work station or make some other improvements. You can generalize coordination signals, too. For example, something went wrong. Something new is happening. Etc.

Just for completion, there's another GitHub Issues Kanban board called TaskTub.

Additionally, I can also confirm people get really confused with Kanban boards if they don't know about the Kanban methodology, which means, if people are thrown into using a Kanban board, most popularly Trello, without proper introduction to the left-to-right-workflow and all those details, then the boards will get stuck at some point, as seen in MMM, because the comments conversations will just spread across many cards and therefore become untraceable, different than with Discourse.

The truth I suppose lies somewhere inbetween Trello, Gingkoapp, Federated Wiki, Digital Karrabirr (@elfpavlik ?), Rhizzoma, Metamaps, Metacademy, TiddlyWiki, Wave, Etherpads, IPython, Wagn ... etc. pp.

Please tell me, which was the other development methodology that had been mentionned somewhere else before again, in opposition of lean methods? And what's the difference there?

@richarddbartlett Will the new Angular Loomio client allow refactoring of conversations (Yes, I'm looking at Discourse!)? This topic for example evolved a little ...

PS: MarkDown ;) > http://sofish.github.io/pen, http://www.zenpen.io, http://mattduvall.com/grande.js, http://markitup.jaysalvat.com ...

@jonrichter I don't understand the question?

I see here that even the protagonists of Kanban as the name for a lean software method are confused about the name: http://agilelion.com/agile-kanban-cafe/what-is-kanban

So now they also have "Kanban Thinking", and somebody has written a book about it. It has become a Brand. A long way from a simple pull signal.

@jonrichter - yeah, probably my fault that the topic "evolved", or "devolved", or whatever. Sorry...I'll get back with the program...

@jonrichter: if i understand what you mean, you can somewhat refactor the conversation by editing the discussion context at the top. you can also create a new thread. what functionality would be better (is in Discourse)?

@bobhaugen: don't worry about getting off-topic, i really appreciate how the topic evolved. :) although i wouldn't mind a new discussion thread with the relevant discussion copied regarding kanban, so we don't derail future discussion of elf's great work.

@ahdinosaur - what's the easy way of starting a new thread with the relevant discussion copied over and then deleted here? everybody needs to do their own comments? Or can one person do it all? I understood @jonrichter to be asking for a one-swell-foop method of doing that to refactor conversations. Right, Jon? Or maybe a way to re-assign one or more comments to a different thread?

(oops, now I am starting a New Feature thread...)

haha, we just had a discussion yesterday with James Lewis and Scott Sadler about using comments / discussion as simple case for distributing data. I even suggested trying to hack on loomio and keep in mind open-app development! not sure if we will get on it but who knows... one thing we find very attractive relates to possibility of conversation existing in multiple contexts, kind of improvement over cross posting! 'forking' threads also sounds like a great feature, @jonrichter do you know some kind of screencast showing how discourse does it?

i'll try in next days to get on doing proper sequence diagrams for webdpack plus some simple screencasts

i also plan on doing sequence diagram for http://webmention.io/ , especially if we talk about decentralized conversations + newly created W3C SocialWG will most likely work with it as Tantek Çelik, long time #IndieWeb hacker acts as group chair (together with Evan Prodromou of StatusNet and now http://pump.io/ fame)

@richarddbartlett @ahdinosaur I'm sorry for being so cryptic. And sorry for comparing Loomio to Discourse, but it just raises the stakes on how online communication, IMHO, has to be imagined:

You can pick certain posts within a thread and move them into a new one or merge them into another existing discussion.

Then, the second trick would be to federate conversations, webmention like, between different "conversation graphs" (as I like to refer to forums/conversation software internally) and make them easily traversable.