Re: action status type

On 11/04/2014 07:55 PM, Sam Goto wrote:
> On Sat, Nov 1, 2014 at 1:19 PM, ☮ elf Pavlik ☮
> < <>>
> wrote:
>     On 11/01/2014 09:09 PM, Jason Douglas wrote:
>     > Yes, potential actions are a "template" for future action instances and
>     > therefore a bit different.  For example, it doesn't make much sense to
>     > use the *-input stuff on completed actions.
>     >
>     > We did try several iterations of the proposal where action templates
>     > were a distinct class hierarchy, but discarded them as unusable.
>     could you please provide links to those discarded proposals and relevant
>     discussions?
> I can probably dig into some old docs and clean them up to make them
> presentable. Give me a sec, I'll share them with you in a bit.
Thanks a lot Sam!

For the future I would propose trying to minimise use of pdf documents.
I made an example of using flavored markdown, where i converted one of
the pdf documents shared on this list:

You could create dedicated github repository for actions and keep fine
tuning conversation in dedicated issues while circulating major design
choices with this list. Examples worth looking at:

* (i also
work on automating tests of examples included in this spec)

This way we also can use git to make tags and have clear history of
changes with commit messages.

Sorry for side tracking but I really think workflow which automates
saving clear history of development process can help everyone interested
understand better all the rationale behind various design choices!

Received on Tuesday, 4 November 2014 20:57:59 UTC