search

near / devx

This is the home of NEAR collective developer experience plans and roadmap.
11 stars 0 forks source link

Process for responding DevX questions #171

Closed ilblackdragon closed 4 years ago

ilblackdragon commented 4 years ago

Do we create issues every time we get a question like this https://near-protocol.slack.com/archives/C01346BPS5T/p1589656379104800 ? E.g. there are 3 issues here:

But more specifically, it’s the process of capturing these -> e.g. ideally the discussion above should be concluded with 3 issues linked. Where 3rd issue should contain response to developer (e.g. like this - https://github.com/nearprotocol/docs/issues/341)

behaviary commented 4 years ago

Note: @amgando and I had a 1-1 discussion that covered this in part. Current iteration will likely involve a bot that can port a message body to an issue in the docs.

ilblackdragon commented 4 years ago

I don't think it's about bot - I think it's about us following process. Also SO should be involved as well.

behaviary commented 4 years ago

@ilblackdragon I agree. In this case, I view the bot as a way to make process really easy, and few steps to follow.