-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TaskTemplate definition #408
Comments
Ignore label issue - that is subsumed by #590. There is a legitimate point about the definition, copied here: Definition of TaskTemplate: An outline of [sic] task of a particular type, that will, when instantiated, generate an actual (unscheduled) task. Why must the resulting task be unscheduled? I have a recipe for muffins that I plan to execute at 3pm today. |
Proposed definition: An outline of a particular task that the execution of a task is based on. Revised definition of |
Roll into PR for #590. |
Update annotations for Template (Issue #408)
Update annotations for Template (Issue #408)
Update annotations for Template (Issue #408)
Update annotations for Template (Issue #408)
Update annotations for Template (Issue #408)
Update annotations for Template (Issue #408)
This has been done and merged #691 |
Definition of TaskTemplate: An outline of [sic] task of a particular type, that will, when instantiated, generate an actual (unscheduled) task.
Why must the resulting task be unscheduled? I have a recipe for muffins that I plan to execute at 3pm today.
I am concerned about the name TaskTemplate. Perhaps the reason it has generated to much confusion (e.g., Should gist:Template be a subclass of gist:Specification? #60 and related issues) is that the name is not very intuitive. We don't tend to describe things like recipes and instructions for assembling furniture as "templates." I don't have a great suggestion at the moment. TaskInstructions is better understood but awkward. TaskOutline?
The text was updated successfully, but these errors were encountered: