Skip to content

Add PR, Feature Request and Question github templates #1128

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Feb 17, 2020
Merged

Add PR, Feature Request and Question github templates #1128

merged 2 commits into from
Feb 17, 2020

Conversation

alubbe
Copy link
Member

@alubbe alubbe commented Feb 13, 2020

Building on #1112, here are my suggestions for the PR, Feature Request and Question github templates.

Again, they are heavily inspired by https://github.com/facebook/jest/tree/master/.github - but there's one big difference: They don't want the github issue tracker to be used for questions, which are instead handled via discord, stackoverflow, etc. What is our stance here?

We could encourage users to open issues to ask questions but warn them that they might not get answered (but then where should they go). Or we could ask them to use this only for clear bug reports or feature requests and direct them elsewhere (but where). What do you think?

@alubbe alubbe mentioned this pull request Feb 13, 2020
Merged
@Siemienik
Copy link
Member

I use only Github, so ... :)

I think that we could encourage users to open issues to ask questions without warns 🥇
I attempt to respond to 5-10 issue per day, add labels, close or - that I mostly like - resolve them.

Fixing the bugs is for me the important thing. But very often I haven't enough time to do that. So I'm really happy and thankful when someone from our community does it 🚀 🚀 🚀

@alubbe
Copy link
Member Author

alubbe commented Feb 14, 2020 •
edited
Loading

@Siemienik I've tried to describe our approach in the template - what do you think?

Have a question about exceljs? Need help using it a certain way that our README does not seem to explain? Ask away!

Please keep in mind that we're unpaid open souce volunteers, so it will help us greatly if you add as many details as possible to your question and describe what other approaches you've tried out so far. And of course, we'd love for you to contribute back the answer to our README via a pull request!

@alubbe alubbe merged commit c8a26c1 into exceljs:master Feb 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Siemienik Siemienik Siemienik approved these changes

@guyonroche guyonroche Awaiting requested review from guyonroche

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@alubbe @Siemienik
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy