2012/3/12 Tomáš Fejfar <[email protected]> > The best solution would IMO be that some people (core devs) could get > magically a lot of reputation >
Not possible. (or some other status - like "ZF" badge on profile picture) and posts with > tag ZendFramework would have different theme, still staying on SO. > But from how I see it there is not much chance of this proposal getting > accepted. And I would stick to the advices from Supporting Developer > Communities on Stack Overflow in this post > http://discuss.area51.stackexchange.com/a/4581/54156 > You're missing the point Tomas. Citing that point: Start with a page on your site, listing where developers should go for > various support-related tasks. Stack Overflow should only be ONE of the > option available. > We do not need _another_ support web page. Currently, contributors and ZF core-team are spread thin across: 1. StackOverflow and other Q&A sites 2. Personal blogs + discussions 3. Official Zend forums 4. Plethora of unofficial forums 5. Official mailing lists 6. Official wiki discussions 7. IRC on a couple of channels 8. Ye'olde write an email to contributor Not only it affects the quality of support you might get from a knowledgeable person, but also increases the confusion of end-user when he/she wants to ask a question. Zend Framework 2 additionally brings in: a) A lot more questions coming in, because ZF2 is a new beast. b) New questions are not yet answered, you won't find many of them on Google. c) Tens of new/refactored Components d) Service\* detached from the core e) Potentially tens of third-party modules, which (despite having nothing directly to do with zf2 core) will be associated with zf2. This translates to the number of incoming questions and number of specialty tags we'll need to bring order to the chaos. The motivation for a dedicated Q&A site is to: 1) Have 1 single site where contributors (+module authors) meet with end-users. 2) Have 1 single address where we direct people to ask their questions. 3) Increase the average quality of answers with a voting mechanism, syntax coloring, discussions (comments) and other tools. 4) In time, build a sizable knowledge base containing high-quality answers for zf1 and zf2. 1) some of the people on SO are good programmers AND know ZF, but will not > want to switch to different site and loose their reputation. > Reputation is not an objective here. I can understand that reputation hunting can be a goal of itself for some people, but I believe that me and many other contributors will want to use the new site to help out people, regardless if even the reputation system exists or not. If we go with SE, I will ask their staff if it's possible to migrate some of the reputation from SO when creating an account at new site. > 2) many people will still ask question about ZF on SO and be accused of > offtopic, as there is separate SE for it (how were they supposed to know?) That depends on how we define it and how we manage it. It's exactly the same with IRC, forums, ML and other places. The line is drawn by the people answering questions. You're right, that questions relating to ZF will sometimes intersect with "general-php", apache and other areas. In my opinion that's nothing bad and such questions would get my attention. In case nature of a question is too off, SE gives moderators and contributors a tool to easily migrate the question back to StackOverflow (and back). Furthermore, I'll be asking moderators on StackExchange to migrate existing [zend-framework] tagged questions to the new site. -- __ /.)\ +48 695 600 936 \(./ [email protected]
