Skip to content
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

Documentation📄: Remove outdated @zulipbot documentation #113

Open
HarshCasper opened this issue Oct 1, 2021 · 6 comments
Open

Documentation📄: Remove outdated @zulipbot documentation #113

HarshCasper opened this issue Oct 1, 2021 · 6 comments
Assignees
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers Hacktoberfest Priority = Low

Comments

@HarshCasper
Copy link
Member

What is the current documentation state?

Currently, the documentation states that we need to tag @zulipbot to take up an issue. This particular information is outdated and doesn't represent the current state of the project.

Where is this stated?

https://docs.moja.global/en/latest/DevelopmentSetup/git_and_github_guide.html#claim-an-issue

Why do you want to improve the statement?

. We would need to ideally refactor this part and mention the correct steps to take up an issue.

Proposed Statement

No response

Additional context.

No response

@HarshCasper HarshCasper added documentation Improvements or additions to documentation good first issue Good for newcomers Hacktoberfest Priority = Low labels Oct 1, 2021
@Samarjeet-singh-chhabra
Copy link
Contributor

Hey Harsh, Can you tell me what should I update it to, what is our new procedure that I should mention!

@HarshCasper
Copy link
Member Author

Hey Harsh, Can you tell me what should I update it to, what is our new procedure that I should mention!

Hi @Samarjeet-singh-chhabra 👋

Thanks for reaching out! I would ideally like to:

  • Remove the portions that mention anything about ZulipBot
  • Mention that to take up an issue you need to tag a maintainer/issue triager to be assigned for the same
  • All further communication would happen on the issue itself

@Samarjeet-singh-chhabra
Copy link
Contributor

Thanks Harsh for assigning, i will be back with updates soon!

@Samarjeet-singh-chhabra
Copy link
Contributor

hey Harsh, I updated the file and created a PR, but no update on that, can you help me with what can I improve on that.

@ORKO06
Copy link

ORKO06 commented Jun 6, 2022

@HarshCasper
Can I work on this issue?

@vedant-z
Copy link

@HarshCasper Looks like this issue is not solved from long time. May I work on this please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers Hacktoberfest Priority = Low
Projects
None yet
Development

No branches or pull requests

4 participants