Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #25804

Re: FAQ

Show key headers only | View raw

Thomas 'PointedEars' Lahn wrote:

> Christoph M. Becker wrote:
> 
>> The great advantage of the current approach: a proposed change (often
>> only fixing a typo or a broken link) will not have to wait forever.
> 
> ISTM you are misunderstanding my approach.  IIRC, the suggestions I have 
> received so far all had the virtue of causing only considerably small, 
> obvious changes, of being submitted *by subscribers of the newsgroup* to no 
> dissent within a reasonable time span, and were therefore implemented by me 
> without consulting the newsgroup any further.

I believe, I do *not* misunderstand your approach.  Thus I wrote
"proposed" (I might have clarified by writing "puclicly proposed") and
"often only fixing a typo or a broken link" (I've added "often", because
there are a few changes, for instance, "Updated paragraph on
'javascript'"[1], which might not be regarded as corrections by *some*
regulars).

> There are other changes overdue in the FAQ content that are not that easy to 
> make, and ISTM that I will have to suggest to the newsgroup because either 
> nobody else sees them or cares about them enough.

I am aware of several issues (*for instance*, "The Internet Explorer
Memory Leak Problem"[2]), but I had not yet found the time to
investigate on them further to be able to make an appropriate proposal.

> Please read my announcement again so that you better understand how I would 
> like this to work.  (Whereas I am working on other ways for people to make 
> suggestions, to be discussed in the newsgroup, than just the newsgroup.)

I believe, that I am well aware of how you would like this to work.
However, when you had announced that, there were several complaints that
your desired approach would not be formal enough.  It seems to me, some
regulars prefer a far more bureaucratic approach.

However, the actual approach might not matter all too much at all.  As
soon as there would be consensus required for a substantial change to
the FAQ, unfortunately there will be none -- at least I'm pretty sure of
that, considering the past.  Votings might be a solution, but:

  * Who would be entitled to vote?
  * Do changes to FAQ require a simple majority, or a supermajority?
  * What would be the rules for three options (keep, remove, improve)?
  * ...

[1]
<http://pointedears.de/wsvn/FAQs?op=comp&compare[]=/trunk/cljs/@29&compare[]=/trunk/cljs/@30>
[2] <http://pointedears.de/scripts/faq/cljs/notes/closures/#clMem>

-- 
Christoph M. Becker

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 14:44 -0700
  Re: Onclick event doesnt work in webkit browser "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-16 00:15 +0200
    Re: Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 15:22 -0700
      Re: Onclick event doesnt work in webkit browser "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-16 00:40 +0200
        Re: Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 15:43 -0700
          Re: Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 15:55 -0700
            Re: Onclick event doesnt work in webkit browser "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-16 10:09 +0200
          Re: Onclick event doesnt work in webkit browser "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-16 10:04 +0200
          Re: Onclick event doesnt work in webkit browser Tim Streater <timstreater@greenbee.net> - 2014-08-16 09:55 +0100
    Re: Onclick event doesnt work in webkit browser "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-16 01:21 +0200
      Re: Onclick event doesnt work in webkit browser PS <poonam.sachdeva5@gmail.com> - 2014-08-15 16:37 -0700
        Re: Onclick event doesnt work in webkit browser "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-16 02:09 +0200
          Re: Onclick event doesnt work in webkit browser John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-16 17:24 +0100
            Re: Onclick event doesnt work in webkit browser "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-16 18:37 +0200
              FAQ (was: Onclick event doesnt work in webkit browser) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-08-16 20:19 +0200
                Re: FAQ (was: Onclick event doesnt work in webkit browser) John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-17 18:10 +0100
                Re: FAQ (was: Onclick event doesnt work in webkit browser) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-17 19:28 +0200
                Re: FAQ (was: Onclick event doesnt work in webkit browser) John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-18 14:44 +0100
                Re: FAQ (was: Onclick event doesnt work in webkit browser) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2014-08-18 22:46 +0200
                Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-17 21:31 +0200
                Re: FAQ John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-18 15:05 +0100
                Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-18 22:38 +0200
                Re: FAQ John Harris <niam@jghnorth.org.uk.invalid> - 2014-08-19 16:23 +0100
                Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-21 00:54 +0200
                Re: FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-08-25 21:01 +0200
                Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-09-02 23:07 +0200
                Re: FAQ Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-09-03 01:53 +0200
                Re: FAQ "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-09-04 02:15 +0200
  Re: Onclick event doesnt work in webkit browser "Christoph M. Becker" <cmbecker69@arcor.de> - 2014-08-16 01:17 +0200

csiph-web