Skip to content
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

[Process Improvement] Use open-app/holodex waffle board as the primary source of Holodex related tasks #84

Open
simontegg opened this issue May 29, 2015 · 5 comments

Comments

@simontegg
Copy link
Contributor

Value:
Holodex related info and tasks are currently spread across 3 github organisations. By using one waffle board we make it easier for stakeholders including ourselves to see what each other are up to, and give Comms, BizDev and other tasks an equivalent visibility to code.

@simontegg simontegg changed the title [Process Improvement] Use this (waffle board) as the sole source of Holodex related task [Process Improvement] Use this (waffle board) as the sole source of Holodex related tasks May 29, 2015
@ahdinosaur
Copy link
Contributor

i'm unsure about moving everything into this repo. open-app/holodex was supposed to be the sole source of high-level Holodex tasks. the point behind the separation was to split info that is meaningful to stakeholders from the deeply technical info and code chatter. in this way, our problems / user stories are in the high-level task board but the info related to solving / implementing the user stories are in the code repo(s). are we giving up on this and if so, why?

@simontegg
Copy link
Contributor Author

You can filter on github and waffle by tag. If we want to share the user stories etc we can share the filtered view of issues or have regular updates in another format (the open app loomio group for example)

@simontegg
Copy link
Contributor Author

My sense is that non-technical stakeholders prefer a proactive comms channel outside of github.

@ahdinosaur
Copy link
Contributor

hmm, i think my resistance to this is because us having one code repo for the project is something i perceive as a fluke. if we were to have many code repos (api, ui, vocab, ...) what would we do then? it's possible we then still aggregate into a single repo that bundles it all together, so that could work.

then if we do decide to transition, what do we do about our existing issues and milestones on the open-app/holodex repo, do we migrate them as is or maybe it seems we're also interested in defining a new process for how we track and manage issues?

i'm also keen on proactive comms channels outside of GitHub, such as regular update digests via a blog or the open app loomio group.

@ahdinosaur
Copy link
Contributor

@simontegg and i have decided to use open-app/holodex for high-level issues, this issue is now about the migration of all high-level issues and labels here to there.

@ahdinosaur ahdinosaur changed the title [Process Improvement] Use this (waffle board) as the sole source of Holodex related tasks [Process Improvement] Use open-app/holodex waffle board as the primary source of Holodex related tasks Jun 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants