-
Notifications
You must be signed in to change notification settings - Fork 26
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
Best way to handle Questions #253
Comments
If you strongly feel forums then let's shut down gitter and move there. I
|
Hey, hope what I wrote didn't come out the wrong way. I'm ecstatic that you're managing Gitter! It's an amazing addition to the project and I'm super happy we have it going after a lot of convincing on my part (it was first suggested last year I think). I'm really happy from everything I've seen there until now and I think it's a critical space for the community. So thank you again! I don't feel strongly for forums, I don't know how involved I could even be there. The point of this post really was just to get ongoing community feedback, not to try muster up support for forums, especially not at the expense of gitter. I agree that a small space is easier to manage and that we can extend in the future. I'm not looking for a quick answer now, just a space to make sure that view points on this issue get tracked in a single spot over time. |
Okay it is clear and I doubt you could ever do me any harm. You are my
|
Haha awesome! Thanks again. |
My 2 cents: To be honest i love gitter, nice to discuss things - i have learnt a lot, it works well for those 1 liner questions that can take hours to solve instead of writing a whole stack post, however i think stack is definitely needed to build up a library of Q/As that remain "forever" One point: I would be keen to write tutorials - what format do you think is best so i can hand them over to someone? |
@ganySA I am working on a portal for snippets and that should allow blog posting too, I have been a little derailed by my "famous theme for Orion" project. Also I realize yesterday gitter has limited history on free version, perhaps it is time we moved to using that forum @gadicc suggested. My fear about spreading ourself too thing remains but I think we do less work with the forum in place. |
@timfam, you sure? @ganySA, how do you mean hand over? i think they should be online. you could also think about doing live coding tutorials on fview-lab.meteor.com like the ones at fview-lab.meteor.com/fview-team |
We'd like to move ahead with the forums, gitter is getting too crowded. It will be nice besides questions to have a spot for community discussions on various topics. I agree both that stackoverflow (#248) is great, and that forums are next logical step for the community (which covers more than just questions). So, we're going to do both, but I think more of our attention will be in the forums (at least for now). We will still move ahead with getting a tag for SO, and it's clear that some people will always have a preference for SO vs Forums for questions, so I think it's important to offer both but also important to prioritize. Please get involved so we can accurately assess how these things develop :) |
Just looking for some community input here. We discussed on Gitter that Gitter was an ideal place for questions, since it would free up the issue page from non-issues and help build the community.
My only concern is that questions can get lost in there. It's quite nice to have questions in individual threads, where they can be tracked by topic, i.e. make sure they get answered, be able to find them again easily, and add to them.
I don't think I personally mind questions on github, because it's quite easy to track... it's only a problem if i'm the only one answering them, because that can take a long time (since i prioritize development). We also discussed stackoverflow and I guess that really is the way to go. The other options is forums.
I'd love to get opinions all in one place, over time. And that place is here :) For now at least.
The text was updated successfully, but these errors were encountered: