3 ms·

This looks absolutely wonderful. A few random thoughts: 1. I'm going to play with this as a way of documenting processes. Being able to answer "how do you deve

by IanCal 11y ago

This looks absolutely wonderful. A few random thoughts: 1. I'm going to play with this as a way of documenting processes. Being able to answer "how do you develop features" or "what's best practice for X" with a usable process is great. 1 a) I'm particularly interested in using this for documenting how to perform experiments, and tracking experiments as they go. 2. I think this is amazing for progressively automating things. Split the task up into manageable, clear chunks to be performed by people. Each step can then (if it seems worth it) be replaced by code. 3. I don't think this is present at the moment (and it probably shouldn't be for a first release) but I'd like to see process hierarchies and importing others. I'd like to say 'Use github's "GITFLOW V2" process for managing feature additions and use "MY_COMPANY_QA V3" for reviewing features before full release'. Anyway, this is great, and I look forward to playing around with it. edit - Even without these, I can already see myself using it just for me. edit 2 - It'd be good to work on the getting started, so that there's just a "run this script" or "clone this repo". There's a lot of "download this file and copy it here" that feels like it should be scripted.

dhaas 11y ago
Thanks for the feedback! Your comment about embedding external QA workflows is super interesting. Right now Orchestra does support what we call 'Review Policies', which allow you to specify that a given workflow step be reviewed k times, or with probability X, or by specific expert Z. But it would be interesting to think of whole workflows for QA. Re: getting started, yeah, we're working on a script--turns out cross-platform support is hard!
- IanCal 11y ago
  > Right now Orchestra does support what we call 'Review Policies', which allow you to specify that a given workflow step be reviewed k times, or with probability X, or by specific expert Z. That's handy, I can think of a bunch of things that fit well with that (particularly review a subset of x%) > Re: getting started, yeah, we're working on a script--turns out cross-platform support is hard! Hah, yeah it is! I've got a version setup now, but am struggling a bit to setup workflows & figure out quite what goes where, but I think I've found the right bit of documentation: http://orchestra.readthedocs.org/en/latest/example_use.html http://orchestra.readthedocs.org/en/latest/example_use.html As a suggestion, if you add a new example, try doing it step by step of what you need to add & do. It's more work, but I find it really helps show what someone will actually experience while creating / updating workflows.
  - dhaas 11y ago
    We have an issue open to improve the journalism exaple: https://github.com/unlimitedlabs/orchestra/issues/32 https://github.com/unlimitedlabs/orchestra/issues/32. If you have concrete suggestions for how to make it better, we'd love to hear them--especially for documentation, which can always use work! Also feel free to reach out to us on gitter (https://gitter.im/unlimitedlabs/orchestra https://gitter.im/unlimitedlabs/orchestra) if you're having trouble getting your local setup to run the workflow and we can talk through the details.

by IanCal 11y ago

dhaas 11y ago

Thanks for the feedback! Your comment about embedding external QA workflows is super interesting. Right now Orchestra does support what we call 'Review Policies', which allow you to specify that a given workflow step be reviewed k times, or with probability X, or by specific expert Z. But it would be interesting to think of whole workflows for QA. Re: getting started, yeah, we're working on a script--turns out cross-platform support is hard!

IanCal 11y ago
> Right now Orchestra does support what we call 'Review Policies', which allow you to specify that a given workflow step be reviewed k times, or with probability X, or by specific expert Z. That's handy, I can think of a bunch of things that fit well with that (particularly review a subset of x%) > Re: getting started, yeah, we're working on a script--turns out cross-platform support is hard! Hah, yeah it is! I've got a version setup now, but am struggling a bit to setup workflows & figure out quite what goes where, but I think I've found the right bit of documentation: http://orchestra.readthedocs.org/en/latest/example_use.html http://orchestra.readthedocs.org/en/latest/example_use.html As a suggestion, if you add a new example, try doing it step by step of what you need to add & do. It's more work, but I find it really helps show what someone will actually experience while creating / updating workflows.
- dhaas 11y ago
  We have an issue open to improve the journalism exaple: https://github.com/unlimitedlabs/orchestra/issues/32 https://github.com/unlimitedlabs/orchestra/issues/32. If you have concrete suggestions for how to make it better, we'd love to hear them--especially for documentation, which can always use work! Also feel free to reach out to us on gitter (https://gitter.im/unlimitedlabs/orchestra https://gitter.im/unlimitedlabs/orchestra) if you're having trouble getting your local setup to run the workflow and we can talk through the details.