You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Otho <ta...@googlemail.com> on 2009/05/01 08:43:30 UTC

Re: Solving the T5 Documentation Dilemma

I would suggest splitting the documentation.

There should be the reference documentation by the creators/commiters of the
project, whis is organized like a book covering all the different aspects of
tapestry 5 in a reference manner eg like spring or hibernate docs. These are
tied to the release version, too.

And then there should be the community docs with tutorials, howto's, recipes
and so on on a wiki. There should be a pattern in the templates which
requires or at least pushes you, to mention the version of Tapestry you are
using.

And lastly I would suggest setting up a forum. Information is more easily
organized there and searching is more convenient than wíth a mailing list
alone. I would think that the barrier of contributing to a forum is lower
than that of contributing to / asking on a mailinglist. Well, the latter can
also be seen as a feature in a way, but publicity and visibility never
really hurt IMO.

2009/4/30 Piero Sartini <ps...@sartini-its.com>

> > I don't think Tapestry's wiki, http://wiki.apache.org/tapestry, is up
> > to the task.
>
> Confluence is available with apache as well. There is already a space
> available at http://cwiki.apache.org/TAPESTRY/ ... maybe its just a matter
> of
> adding content to it?
>
> Anyway.. on Tapestry360 someone would not need to sign a CLA to contribute
> to
> the documentation.
>
>        Piero
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

Re: Solving the T5 Documentation Dilemma

Posted by manuel aldana <al...@gmx.de>.
yes, I know nabble, and I think it is great. I also think usenet is 
generally great, but at some point of support it does not scale.

At mailinglists you don't have topic categories + sticky notes which I 
think are quite important for navigation. Further more it lacks and a 
notification system by topic there. In my view a first class spring 
support (like in spring support forum) wouldn't be possible with a 
mailinglist only.


Ben Gidley schrieb:
> I must also say I prefer mailing lists - it is easier to follow it. If you
> want a forum why not use the nabble or markmail interfaces to the mailing
> lists?
> e.g. http://tapestry.markmail.org/ or
> http://www.nabble.com/Tapestry---User-f340.html
>
> Ben Gidley
>
> www.gidley.co.uk
> ben@gidley.co.uk
>
>
> On Fri, May 1, 2009 at 12:45 PM, Andy Pahne <an...@googlemail.com>wrote:
>
>   
>> except when they are down, just like the hibernate forums recently. I
>> always preferred mailing lists...
>> just my 2 cents
>>
>>
>> manuel aldana schrieb:
>>
>>     
>>> Otho schrieb:
>>>
>>>       
>>>> And lastly I would suggest setting up a forum. Information is more easily
>>>> organized there and searching is more convenient than wíth a mailing list
>>>> alone. I would think that the barrier of contributing to a forum is lower
>>>> than that of contributing to / asking on a mailinglist. Well, the latter
>>>> can
>>>> also be seen as a feature in a way, but publicity and visibility never
>>>> really hurt IMO.
>>>>
>>>>
>>>>         
>>> +1 on this one.
>>>
>>> mailinglist is really nice, but forum often provides better search and
>>> layout advantages (especially for code snippets). Further more you have a
>>> better organization (categories, sticky notes etc.).
>>>
>>>
>>>       
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>     
>
>   


-- 
 manuel aldana
 aldana@gmx.de
 software-engineering blog: http://www.aldana-online.de


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Solving the T5 Documentation Dilemma

Posted by Ben Gidley <be...@gidley.co.uk>.
I must also say I prefer mailing lists - it is easier to follow it. If you
want a forum why not use the nabble or markmail interfaces to the mailing
lists?
e.g. http://tapestry.markmail.org/ or
http://www.nabble.com/Tapestry---User-f340.html

Ben Gidley

www.gidley.co.uk
ben@gidley.co.uk


On Fri, May 1, 2009 at 12:45 PM, Andy Pahne <an...@googlemail.com>wrote:

>
>
> except when they are down, just like the hibernate forums recently. I
> always preferred mailing lists...
> just my 2 cents
>
>
> manuel aldana schrieb:
>
>> Otho schrieb:
>>
>>> And lastly I would suggest setting up a forum. Information is more easily
>>> organized there and searching is more convenient than wíth a mailing list
>>> alone. I would think that the barrier of contributing to a forum is lower
>>> than that of contributing to / asking on a mailinglist. Well, the latter
>>> can
>>> also be seen as a feature in a way, but publicity and visibility never
>>> really hurt IMO.
>>>
>>>
>> +1 on this one.
>>
>> mailinglist is really nice, but forum often provides better search and
>> layout advantages (especially for code snippets). Further more you have a
>> better organization (categories, sticky notes etc.).
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

Re: Solving the T5 Documentation Dilemma

Posted by Andy Pahne <an...@googlemail.com>.

except when they are down, just like the hibernate forums recently. I 
always preferred mailing lists...
just my 2 cents


manuel aldana schrieb:
> Otho schrieb:
>> And lastly I would suggest setting up a forum. Information is more 
>> easily
>> organized there and searching is more convenient than wíth a mailing 
>> list
>> alone. I would think that the barrier of contributing to a forum is 
>> lower
>> than that of contributing to / asking on a mailinglist. Well, the 
>> latter can
>> also be seen as a feature in a way, but publicity and visibility never
>> really hurt IMO.
>>   
> +1 on this one.
>
> mailinglist is really nice, but forum often provides better search and 
> layout advantages (especially for code snippets). Further more you 
> have a better organization (categories, sticky notes etc.).
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Solving the T5 Documentation Dilemma

Posted by manuel aldana <al...@gmx.de>.
Otho schrieb:
> And lastly I would suggest setting up a forum. Information is more easily
> organized there and searching is more convenient than wíth a mailing list
> alone. I would think that the barrier of contributing to a forum is lower
> than that of contributing to / asking on a mailinglist. Well, the latter can
> also be seen as a feature in a way, but publicity and visibility never
> really hurt IMO.
>   
+1 on this one.

mailinglist is really nice, but forum often provides better search and 
layout advantages (especially for code snippets). Further more you have 
a better organization (categories, sticky notes etc.).

-- 
 manuel aldana
 aldana@gmx.de
 software-engineering blog: http://www.aldana-online.de


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Solving the T5 Documentation Dilemma

Posted by Joel Halbert <jo...@su3analytics.com>.
The primary concern, at the moment, seems to be encouraging people to
contribute documentation, tutorials and examples. Making the adding,
updating and extension of docs as open (so anyone can do it) and simple
(so it is not an arduous task) is the key to this. Howard's suggestion
of using the confluence Wiki  - and taking snapshots of  docs whenever a
new release is done makes sense. I would encourage anyone to contribute,
and I'm sure that the regular reviewers will compensate for occasional
inaccuracies. Anything more cumbersome will put people off. I don't like
the idea of tying it into Maven. I for one don't use Maven, and the
perceived additional complexity may put others off experimenting & using
Tap.

-----Original Message-----
From: Otho <ta...@googlemail.com>
Reply-To: Tapestry users <us...@tapestry.apache.org>
To: Tapestry users <us...@tapestry.apache.org>
Subject: Re: Solving the T5 Documentation Dilemma
Date: Fri, 1 May 2009 08:43:30 +0200

I would suggest splitting the documentation.

There should be the reference documentation by the creators/commiters of the
project, whis is organized like a book covering all the different aspects of
tapestry 5 in a reference manner eg like spring or hibernate docs. These are
tied to the release version, too.

And then there should be the community docs with tutorials, howto's, recipes
and so on on a wiki. There should be a pattern in the templates which
requires or at least pushes you, to mention the version of Tapestry you are
using.

And lastly I would suggest setting up a forum. Information is more easily
organized there and searching is more convenient than wíth a mailing list
alone. I would think that the barrier of contributing to a forum is lower
than that of contributing to / asking on a mailinglist. Well, the latter can
also be seen as a feature in a way, but publicity and visibility never
really hurt IMO.

2009/4/30 Piero Sartini <ps...@sartini-its.com>

> > I don't think Tapestry's wiki, http://wiki.apache.org/tapestry, is up
> > to the task.
>
> Confluence is available with apache as well. There is already a space
> available at http://cwiki.apache.org/TAPESTRY/ ... maybe its just a matter
> of
> adding content to it?
>
> Anyway.. on Tapestry360 someone would not need to sign a CLA to contribute
> to
> the documentation.
>
>        Piero
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Solving the T5 Documentation Dilemma

Posted by Joel Halbert <jo...@su3analytics.com>.
ditto.
-1 forum

-----Original Message-----
From: Christian Edward Gruber <ch...@gmail.com>
Reply-To: Tapestry users <us...@tapestry.apache.org>
To: Tapestry users <us...@tapestry.apache.org>
Subject: Re: Solving the T5 Documentation Dilemma
Date: Wed, 13 May 2009 09:29:10 -0400

-1 on forum for the same reasons.

On 13-May-09, at 07:36 , Alfie Kirkpatrick wrote:

> -1 for a forum. I like the fact I can choose between users and users- 
> digest, and I can use nabble or markmail to browse the archive.  
> Unless the proposal is to stop the mailing list, I feel that a forum  
> will simply act to fragment discussions which are an invaluable  
> information source.
>
> Best regards, Alfie.
>
> -----Original Message-----
> From: liigo [mailto:com.liigo@gmail.com]
> Sent: 13 May 2009 03:02
> To: Tapestry users
> Subject: Re: Solving the T5 Documentation Dilemma
>
> +1 for Official docs and User docs, and +1 for tapestry forum

Christian Edward Gruber
e-mail: christianedwardgruber@gmail.com
weblog: http://www.geekinasuit.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Solving the T5 Documentation Dilemma

Posted by Christian Edward Gruber <ch...@gmail.com>.
-1 on forum for the same reasons.

On 13-May-09, at 07:36 , Alfie Kirkpatrick wrote:

> -1 for a forum. I like the fact I can choose between users and users- 
> digest, and I can use nabble or markmail to browse the archive.  
> Unless the proposal is to stop the mailing list, I feel that a forum  
> will simply act to fragment discussions which are an invaluable  
> information source.
>
> Best regards, Alfie.
>
> -----Original Message-----
> From: liigo [mailto:com.liigo@gmail.com]
> Sent: 13 May 2009 03:02
> To: Tapestry users
> Subject: Re: Solving the T5 Documentation Dilemma
>
> +1 for Official docs and User docs, and +1 for tapestry forum

Christian Edward Gruber
e-mail: christianedwardgruber@gmail.com
weblog: http://www.geekinasuit.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


RE: Solving the T5 Documentation Dilemma

Posted by Alfie Kirkpatrick <Al...@ioko.com>.
-1 for a forum. I like the fact I can choose between users and users-digest, and I can use nabble or markmail to browse the archive. Unless the proposal is to stop the mailing list, I feel that a forum will simply act to fragment discussions which are an invaluable information source.

Best regards, Alfie.

-----Original Message-----
From: liigo [mailto:com.liigo@gmail.com] 
Sent: 13 May 2009 03:02
To: Tapestry users
Subject: Re: Solving the T5 Documentation Dilemma

+1 for Official docs and User docs, and +1 for tapestry forum

Re: Solving the T5 Documentation Dilemma

Posted by liigo <co...@gmail.com>.
+1 for Official docs and User docs, and +1 for tapestry forum

2009/5/1 Otho <ta...@googlemail.com>

> I would suggest splitting the documentation.
>
> There should be the reference documentation by the creators/commiters of
> the
> project, whis is organized like a book covering all the different aspects
> of
> tapestry 5 in a reference manner eg like spring or hibernate docs. These
> are
> tied to the release version, too.
>
> And then there should be the community docs with tutorials, howto's,
> recipes
> and so on on a wiki. There should be a pattern in the templates which
> requires or at least pushes you, to mention the version of Tapestry you are
> using.
>
> And lastly I would suggest setting up a forum. Information is more easily
> organized there and searching is more convenient than wíth a mailing list
> alone. I would think that the barrier of contributing to a forum is lower
> than that of contributing to / asking on a mailinglist. Well, the latter
> can
> also be seen as a feature in a way, but publicity and visibility never
> really hurt IMO.
>
> 2009/4/30 Piero Sartini <ps...@sartini-its.com>
>
> > > I don't think Tapestry's wiki, http://wiki.apache.org/tapestry, is up
> > > to the task.
> >
> > Confluence is available with apache as well. There is already a space
> > available at http://cwiki.apache.org/TAPESTRY/ ... maybe its just a
> matter
> > of
> > adding content to it?
> >
> > Anyway.. on Tapestry360 someone would not need to sign a CLA to
> contribute
> > to
> > the documentation.
> >
> >        Piero
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>