On Wed, Sep 20, 2006 at 12:28:54PM +0200, Markus Schaber wrote:
> Maybe you should rename the public writable Wiki page list to Wishlist
> instead of Todo, to make the difference more explicit.
Hmm, all the stuff there now does refer to things that are on the TODO
list (I think). So it's not wishl
Hi, Martijn,
Martijn van Oosterhout wrote:
> 2. I can see the official todo list being in CVS, which gives it all
> the access protection it needs. A wiki todo list can stay where it is,
> just that it's not official.
>
> [I've just made a reference to the TODO list in CVS from the wiki, that
>
Jim Nasby wrote:
Ok, so what is it you need help with?
see previous discussion about what is required to keep a tracker system
healthy. In particular:
. items appearing in other media need to be put in the tracker
. items entered in the tracker need to be regularly triaged, reviewed
and upd
Ok, so what is it you need help with?
On Sep 18, 2006, at 1:24 AM, Joshua D. Drake wrote:
Jim C. Nasby wrote:
On Sun, Sep 17, 2006 at 12:32:13PM -0700, Joshua D. Drake wrote:
Tom proposed a modest roadmap type experiment a week or so ago.
I'd like to see that pursued. After all, we know of s
Jim C. Nasby wrote:
On Sun, Sep 17, 2006 at 12:32:13PM -0700, Joshua D. Drake wrote:
Tom proposed a modest roadmap type experiment a week or so ago. I'd like
to see that pursued. After all, we know of some things that are at least
at first cut stage for 8.3, and a few things high on may people'
On Sun, Sep 17, 2006 at 12:32:13PM -0700, Joshua D. Drake wrote:
>
> >Tom proposed a modest roadmap type experiment a week or so ago. I'd like
> >to see that pursued. After all, we know of some things that are at least
> >at first cut stage for 8.3, and a few things high on may people's
> >agen
Tom proposed a modest roadmap type experiment a week or so ago. I'd like
to see that pursued. After all, we know of some things that are at least
at first cut stage for 8.3, and a few things high on may people's
agenda. I'd also like to see some work done on using a tracker (for
features as w
Tom Lane wrote:
Martijn van Oosterhout writes:
On Sat, Sep 16, 2006 at 09:15:24PM -0400, Tom Lane wrote:
Fortunately, none of the real developers would have to pay any attention
to any such page ... and you can bet they wouldn't.
If someone wants to spend an afternoon pu
Martijn van Oosterhout writes:
> On Sat, Sep 16, 2006 at 09:15:24PM -0400, Tom Lane wrote:
>> Fortunately, none of the real developers would have to pay any attention
>> to any such page ... and you can bet they wouldn't.
> If someone wants to spend an afternoon putting up a coherent
> descriptio
On Sat, 16 Sep 2006, Josh Berkus wrote:
Hi,
Greg,
I think the lessons of wikipedia is precisely that you *don't* want to add
such barriers. You want to let people add stuff pretty much freely. That
encourages people to get involved and put up information.
The other lesson of Wikipedia is tha
Gregory Stark wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
1. Authorized user: is that someone with an account, or someone who has
been authorized by someone else?
In my mind it is someone who without threw a process of email confirmation.
Just to help stave off the amount of trolling
t;[EMAIL PROTECTED]>;
"Dave Page" ; "pgsql-hackers@postgresql.org"
Sent: 17/09/06 14:22
Subject: RE: [pgsql-www] [HACKERS] Developer's Wiki
> Dave took it off when he moved the wiki to it's correct place (being
developer.postgresql.org)
I left it there, but un-
> >> 1. It isn't easy to login
> >
> > Really? You're kidding, right? You click a link that
> requires login,
> > and you get a browser login box. How much easier can it be?
>
> What URL are you talking about?
>
> http://www.postgresql.org/docs/techdocs
Yes.
> Where do I click login? Where d
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>> 1. Authorized user: is that someone with an account, or someone who has
>> been authorized by someone else?
>
> In my mind it is someone who without threw a process of email confirmation.
> Just to help stave off the amount of trolling that may happ
Magnus Hagander wrote:
Two points I'm not clear about on this thread though:
1. Authorized user: is that someone with an account, or
someone who has been authorized by someone else?
IIRC, the idea was "someone with an account". Basically you add a (very
very small) hurdle so you only get the
1. It isn't easy to login
Really? You're kidding, right? You click a link that requires login, and
you get a browser login box. How much easier can it be?
What URL are you talking about?
http://www.postgresql.org/docs/techdocs
Where do I click login? Where do I click create account? Where
1. Authorized user: is that someone with an account, or someone who has
been authorized by someone else?
In my mind it is someone who without threw a process of email
confirmation. Just to help stave off the amount of trolling that may happen.
Joshua D. Drake
2. I can see the official t
> > > The wiki has been sitting there for two weeks and hasn't had any
> > > problems.
> >
> > Uh, you mean apart from the fact that it took very little
> time (days,
> > IIRC) before we had people writing attempts at user documentation,
>
>
>
> Really? Where was that? Did it get deleted in t
On Sun, Sep 17, 2006 at 03:09:29PM +0200, Magnus Hagander wrote:
> > The wiki has been sitting there for two weeks and hasn't had
> > any problems.
>
> Uh, you mean apart from the fact that it took very little time (days,
> IIRC) before we had people writing attempts at user documentation,
Rea
> Two points I'm not clear about on this thread though:
>
> 1. Authorized user: is that someone with an account, or
> someone who has been authorized by someone else?
IIRC, the idea was "someone with an account". Basically you add a (very
very small) hurdle so you only get the people who actuall
> Techdocs is a different problem all together. Josh has
> already mentioned some problems with it. I can mention more.
[warning: thread hi-jack]
> 1. It isn't easy to login
Really? You're kidding, right? You click a link that requires login, and
you get a browser login box. How much easier ca
> The wiki has been sitting there for two weeks and hasn't had
> any problems.
Uh, you mean apart from the fact that it took very little time (days,
IIRC) before we had people writing attempts at user documentation,
somthing that we already have *two* different systems (interactive docs
+ new tec
On Sat, Sep 16, 2006 at 09:15:24PM -0400, Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > Gregory Stark wrote:
> >> A TODO list people can freely add stuff to is precisely what would make it
> >> useful. It would have things we don't already know.
>
> > I am just going to hope
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Gregory Stark wrote:
>> A TODO list people can freely add stuff to is precisely what would make it
>> useful. It would have things we don't already know.
> I am just going to hope that you are kidding about this one.
Fortunately, none of the real de
Gregory Stark wrote:
Josh Berkus writes:
The other lesson of Wikipedia is that maintaining wiki quality for a generally
editable wiki requires a full-time dedicated staff. We don't even have any
volunteers who have 4 hours/week to commit to cleaning up the wiki, unless
you're volunteering.
Josh Berkus writes:
> The other lesson of Wikipedia is that maintaining wiki quality for a
> generally
> editable wiki requires a full-time dedicated staff. We don't even have any
> volunteers who have 4 hours/week to commit to cleaning up the wiki, unless
> you're volunteering.
Bullshit.
Gregory Stark wrote:
Josh Berkus writes:
I was actually hoping for more feedback on the content itself. I'm
still not clear if it's supposed to be "developers only - to the
exclusion of users" or "developers only - but accessable to anyone".
It should be readable by everyone, but editable onl
Greg,
> I think the lessons of wikipedia is precisely that you *don't* want to add
> such barriers. You want to let people add stuff pretty much freely. That
> encourages people to get involved and put up information.
The other lesson of Wikipedia is that maintaining wiki quality for a generally
Josh Berkus writes:
>> I was actually hoping for more feedback on the content itself. I'm
>> still not clear if it's supposed to be "developers only - to the
>> exclusion of users" or "developers only - but accessable to anyone".
>
> It should be readable by everyone, but editable only by authori
Martjin,
> I was actually hoping for more feedback on the content itself. I'm
> still not clear if it's supposed to be "developers only - to the
> exclusion of users" or "developers only - but accessable to anyone".
It should be readable by everyone, but editable only by authorized users.
--
Jo
30 matches
Mail list logo