You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jean T. Anderson" <jt...@bristowhill.com> on 2006/02/17 18:46:40 UTC
[web] wiki vs website (Was "Performance regressions")
Olav Sandstaa wrote:
> Myrna van Lunteren <m....@gmail.com> wrote:
>
>>would it make sense & be ok to point to these tests from the 'tests results'
>>web page?
>
>
> It would definitively be ok to point to these tests. I leave it to
> someone else to decide if it "makes sense" :-)
>
> ..olav
Is there any reason that http://db.apache.org/derby/derby_tests.html
cannot be moved to the Wiki where developers can more easily update it?
Is there any reason to restrict the ability to update this information?
Here are my thoughts on what belongs where.
The web site must host anything that should be write protected (only a
committer updates). Examples include:
(1) Anything having to do with Derby project policies; for example, the
community page at http://db.apache.org/derby/derby_comm.html because of
the policies mentioned.
(2) downloads/releases pages
(3) contributions by authors on a specific topic
The wiki may host anything that should allow update by anyone.
We need to face the reality that very few developers are willing to
update the web site or produce web site patches -- and I'm not just
talking about derby. This is an issue that many ASF projects face. So
I'm inclined to move everything to the wiki that possibly can be.
-jean
Re: [web] wiki vs website (Was "Performance regressions")
Posted by Myrna van Lunteren <m....@gmail.com>.
It's ok with me.
Myrna
On 2/17/06, David W. Van Couvering <Da...@sun.com> wrote:
>
> I support moving this page to the Wiki.
>
> David
>
> Jean T. Anderson wrote:
> > Olav Sandstaa wrote:
> >
> >>Myrna van Lunteren <m....@gmail.com> wrote:
> >>
> >>
> >>>would it make sense & be ok to point to these tests from the 'tests
> results'
> >>>web page?
> >>
> >>
> >>It would definitively be ok to point to these tests. I leave it to
> >>someone else to decide if it "makes sense" :-)
> >>
> >>..olav
> >
> >
> > Is there any reason that http://db.apache.org/derby/derby_tests.html
> > cannot be moved to the Wiki where developers can more easily update it?
> > Is there any reason to restrict the ability to update this information?
> >
> > Here are my thoughts on what belongs where.
> >
> > The web site must host anything that should be write protected (only a
> > committer updates). Examples include:
> > (1) Anything having to do with Derby project policies; for example, the
> > community page at http://db.apache.org/derby/derby_comm.html because of
> > the policies mentioned.
> > (2) downloads/releases pages
> > (3) contributions by authors on a specific topic
> >
> > The wiki may host anything that should allow update by anyone.
> >
> > We need to face the reality that very few developers are willing to
> > update the web site or produce web site patches -- and I'm not just
> > talking about derby. This is an issue that many ASF projects face. So
> > I'm inclined to move everything to the wiki that possibly can be.
> >
> > -jean
>
>
>
Re: [web] wiki vs website (Was "Performance regressions")
Posted by "David W. Van Couvering" <Da...@Sun.COM>.
I support moving this page to the Wiki.
David
Jean T. Anderson wrote:
> Olav Sandstaa wrote:
>
>>Myrna van Lunteren <m....@gmail.com> wrote:
>>
>>
>>>would it make sense & be ok to point to these tests from the 'tests results'
>>>web page?
>>
>>
>>It would definitively be ok to point to these tests. I leave it to
>>someone else to decide if it "makes sense" :-)
>>
>>..olav
>
>
> Is there any reason that http://db.apache.org/derby/derby_tests.html
> cannot be moved to the Wiki where developers can more easily update it?
> Is there any reason to restrict the ability to update this information?
>
> Here are my thoughts on what belongs where.
>
> The web site must host anything that should be write protected (only a
> committer updates). Examples include:
> (1) Anything having to do with Derby project policies; for example, the
> community page at http://db.apache.org/derby/derby_comm.html because of
> the policies mentioned.
> (2) downloads/releases pages
> (3) contributions by authors on a specific topic
>
> The wiki may host anything that should allow update by anyone.
>
> We need to face the reality that very few developers are willing to
> update the web site or produce web site patches -- and I'm not just
> talking about derby. This is an issue that many ASF projects face. So
> I'm inclined to move everything to the wiki that possibly can be.
>
> -jean