Allow dependencies to be declared elsewhere

[victorb]

Currently, you're only allowed to declare the dependencies in a "depends on " message in the top-level issue. There have been some discussion that this is not enough, and we should be able to declare this elsewhere as well.

Some of the ideas:

• Have a depviz.json file in the repository
• Allow anyone to comment to an issue with "depends on"
• Allow just certain people to comment on a issue with "depends on"

---

depends on #34

[wking]

On Mon, Nov 28, 2016 at 12:13:10PM -0800, ᴠɪᴄᴛᴏʀ ʙᴊᴇʟᴋʜᴏʟᴍ wrote:

• Have a depviz.json file in the repository

I'd rather not, since the issue cloud is fairly independent from the repository it's tracking.

• Allow anyone to comment to an issue with "depends on"
• Allow just certain people to comment on a issue with "depends on"

These sound fine to me, and I'd recommend enabling/disabling them with a config UI. We've also talked about that sort of configurable behavior in #13 and #17.

[jbenet]

I'd rather not, since the issue cloud is fairly independent from the repository it's tracking.

yeah agreed.

we may end up with a depviz.json for other options (like repo-wide settings that SHOULD be set in a repo, and not set in the user's own UI.

These sound fine to me, and I'd recommend enabling/disabling them with a config UI

Yep, agree with this.