I think that would be a fine idea, but it's always hard
- pages change their status (a proposal becomes part of GHC)
- a page may belong in multiple places
- people keep URLs in bookmarks, and they are linked from other pages in Trac
so moving pages is painful.
The last is significant. Do we
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
Hi Austin,
I haven't heard back from you about this, and D302 has been waiting for
review in phab for two weeks. This seems to be a minor change, so if I
don't hear otherwise by the end of the week, I'm going to go ahead and
merge.
Thanks,
Geoff
On 08/29/2014 01:29 PM, Geoffrey Mainland wrote:
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,
Hi Geoff,
Sorry about that - this one slipped by my radar amongst a lot of other
things. I'm spending today in the review queue, so I'll get to it.
On Wed, Oct 15, 2014 at 10:43 AM, Geoffrey Mainland
mainl...@apeiron.net wrote:
Hi Austin,
I haven't heard back from you about this, and D302 has
OK, to kick this thread around:
It seems like several people who touch the users guide are in favor of
this due to:
- Simpler markup
- DocBook compatibility
- Hopefully attracting more users if it's easier to manage.
Cons:
- +1 Dependency (minor)
- No formal grammar (I don't think it
11 matches
Mail list logo