Wednesday, July 10, 2013

Re: RFC: New http://ask.cakephp.org

Personally I don't see the benefit of a subsite, compared to what's available already on stackoverflow.com.

There are some rather significant disadvantages to  using a subsite instead of a tag, including:
  • Reduces the audience
  • Participants have to "opt in" rather than simply browse stack overflow
  • The framework is less visible to non-framework users
  • Requires maintenance, especially to migrate questions from stackoverflow to subsite and vice versa (an ongoing overhead)
For example: questions frequently appear on stack over flow of the form:

> I need to do <something common to any php install> - I'm using CakePHP.

Whereas on stackoverflow answers can come from outside the cakephp community or the question can simply be edited/tagged appropriate - on a subsite the question is invisible to a more appropriate audience (those looking at the php tag on stack overflow) and is effectively off topic on the subsite.

It would be appropriate to have a subsite where questions were considered in some way offtopic on stackoverflow - but that's not the case for CakePHP.

AD





On Wednesday, 10 July 2013 09:50:38 UTC+2, Florian Krämer wrote:
I think the CakePHP tag is good enough. It is not like there is not already enough to maintain and care about, so if a dedicated stack exchange site takes more resources of any kind don't do it and stay with the tag.

On Friday, July 5, 2013 4:21:29 AM UTC+2, mark_story wrote:
A dedicated stackexchange would be great. They take a fair bit of work / community votes to make happen though. That is one reason we're just using the cakephp tag right now.

-Mark

On Thursday, 27 June 2013 20:43:38 UTC-4, ravag...@gmail.com wrote:
[Cross posting this on CakePHP Facebook Group https://www.facebook.com/groups/cake.community/]

Hello everybody

I came across an idea which I wanted to share with and hope to spark some discussion.
Probably - or better said for sure - I'm not even the first one having it.

First some back story:

As you may know CakePHP's Question & Answer site http://ask.cakephp.org/ redirects nowadays to "cakephp" tagged questions on stackoverflow.com.

http://stackoverflow.com/questions/tagged/cakephp

I haven't seen any official statement about that from the development team but the Wayback Machine could crawl the page the last time on 09.05.2013.

http://web.archive.org/web/20130509084040/http://ask.cakephp.org

The CakePHP Questions site before that, http://www.cakeqs.org/ (nowadays a japanese blog), was last seen on 02.10.2010.
Any later request got redirected to http://ask.cakephp.org/.

http://web.archive.org/web/20101002085134/http://cakeqs.org/

So back to the idea...

Recently I came accross one of the many domain/topic specific sub sites of stackoverflow.com.

http://stackexchange.com/sites#technology

For example "Drupal Answers".

http://drupal.stackexchange.com/

And I thought "Hey wouldn't it be nicer to redirect CakePHP's Questions & Answers site to something like this instead of just the tagged with "cakephp" site?".

Like I said I'm not the first one, so this is rather a follow-up on a three years old idea, which time hadn't come yet.

https://groups.google.com/forum/#!searchin/cake-php/stackexchange/cake-php/pA7q6gddW74/aaCntQer_jEJ

But I think the time is now right.
What do you think?
Should we open a proposal for http://cakephp.stackexchange.com/ called "CakePHP Questions & Answers" or something like this?

http://area51.stackexchange.com/faq

I personally think it would strengthen the CakePHP brand even further...

Greetings from Switzerland
Marc

--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
 
---
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscribe@googlegroups.com.
To post to this group, send email to cake-php@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

No comments: