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

Technical Support in Github #3126

Closed
jjatie opened this issue Dec 21, 2017 · 4 comments
Closed

Technical Support in Github #3126

jjatie opened this issue Dec 21, 2017 · 4 comments

Comments

@jjatie
Copy link
Collaborator

jjatie commented Dec 21, 2017

I think we should follow in the footsteps of Alamofire and many other popular repos, and restrict issues to be about the repo itself (bugs, implementation details, feature requests, etc.), and not support in how to use the framework. We should direct support questions to Stack Overflow with the [ios-charts] tag.

The biggest benefit is that there is a central spot for all Charts questions. It also allows the maintainers to not be distracted by support tickets. I propose we update README.md to reflect this, and close all support tickets with a comment about the new rule.

@liuxuan30
Copy link
Member

liuxuan30 commented Dec 22, 2017

you cannot stop people doing this I guess. We still need to answer Qs on issues. It's already in README I remember.

If you are having questions or problems, you should:
Make sure you are using the latest version of the library. Check the release-section.
Study the Android version's Documentation-Wiki
Study the (Still incomplete Doc-Percent) Pod-Documentation
Search or open questions on stackoverflow with the ios-charts tag
Search known issues for your problem (open and closed)
Create new issues (please 🔥 search known issues before 🔥, do not create duplicate issues)

@liuxuan30
Copy link
Member

liuxuan30 commented Dec 22, 2017

I used to check every issue on github and manage it. I have been a long time not looking at SO, as there are more people answering. Personally I already get used to it. If more people help answering whatever the issues are, what I do is just judging close or not.

BTW I hate SO's markdown. It's much easier to type on github :)

For the pure "how to use xxx" question, what I did is asking them to refer ChartsDemo. Not much burden

@jjatie jjatie closed this as completed Feb 20, 2018
@liuxuan30
Copy link
Member

@jjatie we might also want have some most popular Q&As and documentations? Like people don't know to call ChartData's notifyDataChanged and ChartView's notifyDataSetChanged after they add new entries. It's also some things we can improve to avoid.

@liuxuan30
Copy link
Member

Let's try route some questions that are suitable for SO community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants