-
Notifications
You must be signed in to change notification settings - Fork 2
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
Scheduled Operations: Post a digest of unanswered StackExchange questions to Matrix #21
Comments
Is there an RSS feed for this? |
@lovelaced they have an API. I'm thinking we could use github workflow cron job (similar to https://github.com/paritytech/opstooling/blob/master/.github/workflows/good-morning-techops.yml, simple python script) @cmichi few questions:
|
|
Just thought of this: For the updated format I meant it like this:
Unfortunately there are more smart contract questions with no answers. The above list is limited to 15 entries. Please check StackExchange directly for the others. |
so basically it will be like:
|
Describe your problem and idea for the tool
I would like to have a bot that posts unanswered Substrate StackExchange questions for specified tags to our core team channel in Matrix.
This is the format I imagine:
Please just keep the number of days and don't shorten it to weeks. Please sort by longest unanswered on the top.
Those are the tags that should be watched:
ink
,smart-contract
,pallet-contracts
,substrate-contracts-node
,cargo-contract
,contracts
.The digest should be posted to https://matrix.to/#/!nqwrcufvSwqTNsLMkj:matrix.parity.io?via=matrix.parity.io&via=web3.foundation.
Talk to me (Matrix: @michi:matrix.parity.io) or @athei (Matrix: @alext:matrix.parity.io) if you need an admin to set up the bot in the channel.
How do you solve this problem now?
There is no solution yet and asking people to go through unanswered questions by themselves hasn't been fruitful.
Importance and impact
Deadline
31 June
Additional info
The text was updated successfully, but these errors were encountered: