.
Cheers,
Simon
I don't have a strong opinion here
Simon
| -Original Message-
| From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of
| Yuras Shumovich
| Sent: 14 October 2014 23:13
| To: ghc-devs@haskell.org Devs
| Subject: Wiki: special namespace for proposals
Message-
| From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of
| Yuras Shumovich
| Sent: 14 October 2014 23:13
| To: ghc-devs@haskell.org Devs
| Subject: Wiki: special namespace for proposals?
|
|
| Hello,
|
| Would it be better to organize proposals under one namespace
I'm all for improving organization of the wiki but I'm not sure about this
idea. What happens when
a proposal gets implemented? You can't just move the page to a new address. You
can create a new
wiki page describing the final dsign that was implemented and replace the
content of the proposal
Suggestion: Why not use the namespace 'Design' rather than 'Proposal'?
Rationale: a Proposal is a proposed design, and a final implementation
is, well, an implementation of that design. So what the thing is does
not change, but its status (proposal vs implemented) does. And, in
fact, there
Instead of encoding the status in the URL, since we don't want URLs to
change with the status of the proposal/feature changes, it sounds like
we really just want something better than TitleIndex for browsing the
wiki. (I've never seen a Trac wiki where TitleIndex is that useful
anyway, other than
On 2014-10-15 at 18:09:32 +0200, Andrew Farmer wrote:
[...]
I'm not really familiar with what Trac Wiki is capable of. Is it
possible to add tags/categories to a page and then make an
auto-generated list of links to all pages with a given tag/category?
Fyi, Trac by default has no tags, and
Joachim yes, you are right that proposals and designs are different things.
And we already have a namespace for that: Commentary!
Good point.
So when a Proposal gets implemented, this should be clearly noted at the
top of the Proposal page, linking to the relevant Comentary page
(...)
The
Hi,
Am Mittwoch, den 15.10.2014, 18:48 +0200 schrieb Jan Stolarek:
Joachim yes, you are right that proposals and designs are different
things.
And we already have a namespace for that: Commentary!
Good point.
So when a Proposal gets implemented, this should be clearly noted at the
yeah, agreed
currently on the wiki its sometimes hard to determine which pages are this
is how we implemented it vs
this is a bunch of different ideas and approaches we're trying to layout
On Wed, Oct 15, 2014 at 12:58 PM, Joachim Breitner m...@joachim-breitner.de
wrote:
Hi,
Am Mittwoch,
Hello,
Would it be better to organize proposals under one namespace? Right now
they belongs to root namespace, so title index
( https://ghc.haskell.org/trac/ghc/wiki/TitleIndex ) is hard to use.
I was going to start new page describing language extension, but I don't
want do increase entropy
Hi,
Am Mittwoch, den 15.10.2014, 01:12 +0300 schrieb Yuras Shumovich:
Would it be better to organize proposals under one namespace? Right now
they belongs to root namespace, so title index
( https://ghc.haskell.org/trac/ghc/wiki/TitleIndex ) is hard to use.
I was going to start new page
11 matches
Mail list logo
