unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <embe8573@student.uu.se>, help-gnu-emacs@gnu.org
Subject: RE: emacs stackexchange beta site
Date: Fri, 19 Sep 2014 12:55:16 -0700 (PDT)	[thread overview]
Message-ID: <6d57d9d5-46fe-4b30-8500-b775d96c4282@default> (raw)
In-Reply-To: <87sijnbfbn.fsf@debian.uxu>

> > Exactly. Even today one has to follow the emacs tag
> > on stackexchange to get notified of emacs questions on
> > the different sites (SO, Tex, SU, etc.):
> 
> So that will be easier when every thing will be on one
> site.

What gave you the idea that everything concerning Emacs
will be on one site?

> About the tags, we should remember the Emacs tag will
> remain on those other sites

And so will the questions there that are tagged [emacs].
As well they should, as they might also have other tags
(or content) that is specific to that site.

> - as for the Emacs site,
> the tag system will be much more elaborate for
> Emacs-specifics: there will be one Gnus tag, one
> emacs-w3m tag, one Elisp tag, and so one.

Nothing prevents you from adding those tags today.
See Emacs-specific tags such as `font-lock', for example.

> It will be much better for the "follower" and it will
> be PR not just for Emacs but for all those modules as
> well.
>
> > http://stackexchange.com/filters/19474/emacs-questions
> >
> > Adding an emacs SX site just adds one more site to
> > monitor, because I guess it won't be forbiden to ask
> > an emacs question on superuser or tex in the future.
> 
> It won't be. And people will still do it. If it relates
> only to Emacs and nothing whatsoever to for example
> TeX, the question will be moved from that site to the
> Emacs site. The user will thus be notified of that
> site's existence.

Migration of questions across sites is manual.  Just more
bother.  Please consider signing up to help maintain and
manage the overhead you're endorsing.

And your envisioned migration scenario applies only for
questions unrelated to anything else, besides Emacs, on
the given site.  Other questions tagged Emacs might well
be more relevant right where they are.  That's one reason
migration is manual.



  reply	other threads:[~2014-09-19 19:55 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.9059.1410993440.1147.help-gnu-emacs@gnu.org>
2014-09-17 23:26 ` emacs stackexchange beta site Emanuel Berg
2014-09-18  2:06   ` Drew Adams
     [not found]   ` <mailman.9072.1411006041.1147.help-gnu-emacs@gnu.org>
2014-09-18 21:03     ` Emanuel Berg
2014-09-18 23:47       ` Stefan Monnier
2014-09-19 13:34         ` Tom
2014-09-19 14:53           ` Drew Adams
     [not found]           ` <mailman.9197.1411138427.1147.help-gnu-emacs@gnu.org>
2014-09-19 19:13             ` Emanuel Berg
2014-09-19 19:58               ` Drew Adams
     [not found]               ` <mailman.9231.1411156757.1147.help-gnu-emacs@gnu.org>
2014-09-19 20:24                 ` Emanuel Berg
2014-09-19 20:44                   ` Drew Adams
     [not found]                   ` <mailman.9235.1411159521.1147.help-gnu-emacs@gnu.org>
2014-09-19 21:01                     ` Emanuel Berg
     [not found]         ` <mailman.9194.1411136428.1147.help-gnu-emacs@gnu.org>
2014-09-19 19:06           ` Emanuel Berg
2014-09-19 19:55             ` Drew Adams [this message]
     [not found]             ` <mailman.9230.1411156541.1147.help-gnu-emacs@gnu.org>
2014-09-19 20:12               ` Emanuel Berg
2014-09-19  6:13       ` Udyant Wig
2014-09-19 17:57         ` Pascal J. Bourguignon
2014-09-19 18:54         ` Emanuel Berg
2014-09-20  6:58           ` Udyant Wig
2014-09-20 15:02             ` Emanuel Berg
2014-09-21 10:04               ` Udyant Wig
2014-09-21 15:49                 ` Emanuel Berg
2014-09-22  5:10                   ` Udyant Wig
2014-09-22 22:44                     ` Emanuel Berg
     [not found]         ` <mailman.9215.1411149649.1147.help-gnu-emacs@gnu.org>
2014-09-19 18:53           ` Udyant Wig
2014-09-19 19:18             ` Emanuel Berg
2014-09-19 19:22             ` Emanuel Berg
2014-09-19 23:46             ` Pascal J. Bourguignon
2014-09-20  1:24             ` Stefan Monnier
     [not found]             ` <mailman.9241.1411170621.1147.help-gnu-emacs@gnu.org>
2014-09-20  6:14               ` Udyant Wig
2014-09-20 14:47                 ` Emanuel Berg
2014-09-21 10:09                   ` Udyant Wig
2014-09-21 15:52                     ` Emanuel Berg
     [not found]             ` <mailman.9244.1411176300.1147.help-gnu-emacs@gnu.org>
2014-09-20  6:17               ` Udyant Wig
2014-09-19 18:58           ` Emanuel Berg
     [not found]       ` <mailman.9168.1411115739.1147.help-gnu-emacs@gnu.org>
2014-09-19 19:01         ` Emanuel Berg
2014-09-17 22:36 Ian Kelling
2014-10-11 13:33 ` Bastien
     [not found] ` <mailman.10973.1413034461.1147.help-gnu-emacs@gnu.org>
2014-10-17  0:04   ` Emanuel Berg
2014-10-17  0:16     ` Emanuel Berg
2014-10-17 21:37       ` Artur Malabarba
     [not found]       ` <mailman.11408.1413582659.1147.help-gnu-emacs@gnu.org>
2014-10-17 22:35         ` Emanuel Berg
2014-10-18 14:33           ` Rainer M Krug
2014-10-18 17:06           ` Artur Malabarba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6d57d9d5-46fe-4b30-8500-b775d96c4282@default \
    --to=drew.adams@oracle.com \
    --cc=embe8573@student.uu.se \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).