search

aragon / issues

A centralized repo for managing public issues with the Aragon desktop app, the web app and the contracts that power them. Purely technical topics belong to each project repository.
4 stars 1 forks source link

Github issues and project management structure #73

Closed izqui closed 6 years ago

izqui commented 7 years ago

My current opinion is leave aragon/issues as a centralized support ticket tracker and high-level feature multi-disciplinary project management tool using projects and millestones

For specific technical issues and PRs we could use the projects (aragon-dapp, aragon-core or any code repo) issues and PRs. Those should be used to conduct the commiteth bounty programs too.

Only question remaining is what do we do with aragon/aragon? It is the most starred repo and we are only using it to do the dapp releases. Any opinions?

luisivan commented 7 years ago

I agree with everything. I'd leave aragon/aragon for the dapp, which right now kind of encompasses all the subprojects. What do you think?

onbjerg commented 7 years ago

If you're only using aragon/aragon for releases of the ÐApp, then why not move the entirety of the codebase into that repository as well? It seems a bit overhead-y to have "empty" repositories.

izqui commented 7 years ago

Yep, that was what I was talking to Luis. Migrate aragon-dapp to aragon, as this repo is going to have less and less code and be an umbrella project composed by multiple other submodules.

Smokyish commented 7 years ago

Yeah, i like the idea to migrate aragon-dapp to aragon and having issues in the repos, it should make it easier to track the issues.

If we move technical issues to the repos, I'm not sure if aragon/issues is needed, because Github shouldn't be a support platform, but used for the technicals, so you can concentrate on these issues and not have distracting things that would be better fitted elsewhere.

izqui commented 7 years ago

Progress: