Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Process for responding DevX questions #171

Closed
ilblackdragon opened this issue May 16, 2020 · 3 comments
Closed

Process for responding DevX questions #171

ilblackdragon opened this issue May 16, 2020 · 3 comments
Assignees
Labels
P1 Very important process

Comments

@ilblackdragon
Copy link
Member

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:

  • AS sdk doesn’t have a high level API for funds transfer
  • We don’t have an example of AS contract transferring NEAR :face_palm:
  • We don’t have documentation for transferring NEAR (in both AS and RS)

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 - near/docs#341)

@behaviary behaviary added bug Something isn't working P1 Very important labels May 18, 2020
@behaviary
Copy link

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.

@behaviary behaviary added process and removed bug Something isn't working labels May 21, 2020
@ilblackdragon
Copy link
Member Author

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

@behaviary
Copy link

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P1 Very important process
Projects
None yet
Development

No branches or pull requests

2 participants