You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Thiago H de Paula Figueiredo <th...@gmail.com> on 2013/10/08 21:09:57 UTC
Proposal for a list of modules recommended by the Tapestry team
Hi!
There's an interesting discussion between me and Pieter in
https://issues.apache.org/jira/browse/TAP5-64. The gist of it is that he
wants portlets support in Tapestry, there's tapestry5-portlets, which is
written by at least two Tapestry committers, but the consensus here is to
not add more modules to the Tapestry project itself due to the time to
support it. His argument, and I kind of agree with him, is that having
tapestry5-portlets in the Tapestry project is a seal of quality for the
portlet support.
I propose a compromise: in the Tapestry documentation site, a page
containing third-party Tapestry and Tapestry-IoC modules which the
Tapestry team recommends due to their proven quality. For example,
tapestry-security is written by Kalle Korhonen, which is both a Tapestry
and Shiro committer. Or tapestry-url-rewriter, written by me and Robert
Zeigler and not in Tapestry itself anymore. For a given module to be
listed there, I suggest that we carry a vote just like we do with new
committers. In addition, we could have a page in the Tapestry
documentation with some documentation.
What do you guys think?
Cheers!
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Tue, 08 Oct 2013 20:37:31 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
wrote:
> As much as I hate to say it, just like with the book idea, the Tapestry
> ecosystem isn't big enough
> to have an 'endorsed by' program or any kind of certification. Wish it
> wasn't so but it is.
It's not about certification. It's about people thinking, for example,
that Tapestry 5 doesn't support portlets even when a third-party module
written by at least one committer already does it. It's just about us
saying something in the lines of "this isn't part of the Tapestry project
itself, but you can trust it because we do and we use it". It would have
just a handful of modules such as tapestry-security, tapestry5-portlets
plus some other ones, specially the ones that are widely used and written
by at least one Tapestry committer. I wouldn't even submit my own
tapestry-rss, tapestry-wymeditor and tapestry-syntax-highlighter to it,
just tapestry-url-rewriter, because it used to be part of Tapestry itself
and has good test coverage. In addition, it's used in production in many
sites I've worked on, both personal projects and work ones.
> For example, let's take CDI support. There are at least 3
> implementations, with equal quality as far as I know.
> Who is going to be the judge which one gets the stamp of approval?
If all three are good (I haven't used them) and have extensive code
coverage, them all three could get the stamp of approval. The same level
of quality we expect from Tapestry itself would be expected to this
recommended modules.
> PMC? All committers? Users of the list?
I've already said what my answer to the question above: a standard Apache
Software Foundation vote, so everybody can give their opinion, but only
the PMC members get binding votes.
> Do you think all three should get approval?
> Do you think people are actually going to take a look at all the
> modules, really take a look at them for quality?
I think people should just approve what they already use. No one would be
forced to review anything. I don't use CDI, so I wouldn't vote on any of
its integrations with Tapestry.
> Thiago, as far as your own modules, I think you are doing great work,
> and you should put 'Tapestry Committer and PMC member' with your modules.
> (at least I think you are :)
> That should carry more than enough weight with people.
Good idea. :)
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Bob Harner <bo...@gmail.com>.
And I'm happy to make it a community project in whatever way works, such as
adding people as collaborators to the project in GitHub. Just ask.
On Wed, Oct 9, 2013 at 8:58 PM, Bob Harner <bo...@gmail.com> wrote:
> I really need to spend way more time on it (and I'm open to pull requests
> and contributers). It would fulfill several important needs. But the switch
> to Tapestry 5.4 really slowed me down (Bootstrap really killed the layout
> and all the careful polishing I had done). I wish now that I hadn't
> switched to 5.4 yet, but I wanted to dump prototype.js. So there's still
> some CSS and JavaScript to fix.
>
> The Component World database is pretty up to date. It currently contains
> 358 (!) elements (descriptions of Tapestry-related components, mixins,
> elements, pages, modules, frameworks, and web sites) in a hierarchical
> structure. For example, just yesterday I added Thiago's AddRssLink mixin
> and the Tapestry-rss module it belongs to, which is listed as part of his
> Ars Machina "site".
>
> For each entry the app is tracking its name, description, documentation
> URL, demo URL, Tapestry version compatibility, the license, whether it's a
> Tapestry-provided component or 3rd party, etc.
>
> The https://github.com/bobharner/ComponentWorld/issues page is an
> accurate list of what still needs to be done. Mainly what the app needs is:
>
> 1) A security layer (Tapestry-security) for authentication to the pages
> for adding new entries and doing admin actions.
>
> 2) A few simple crud interfaces for updating the lookup tables in the
> database (entry types, source types, licenses, Tapestry versions
>
> 3) Set it up to run under Tomcat in our Apache jail where the Hotel
> Booking example runs, and point the doc pages to it.
>
>
>
> On Wed, Oct 9, 2013 at 4:58 PM, Thiago H de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
>> On Wed, 09 Oct 2013 15:55:09 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
>> wrote:
>>
>> Perhaps its time to finish it. It looks good from the screen shots that
>>> I've seen. Perhaps it can be seen as community building project.
>>>
>>
>> Agreed. Bob, what's the status of Component World now?
>>
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Tapestry, Java and Hibernate consultant and developer
>> http://machina.com.br
>>
>
>
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Bob Harner <bo...@gmail.com>.
I really need to spend way more time on it (and I'm open to pull requests
and contributers). It would fulfill several important needs. But the switch
to Tapestry 5.4 really slowed me down (Bootstrap really killed the layout
and all the careful polishing I had done). I wish now that I hadn't
switched to 5.4 yet, but I wanted to dump prototype.js. So there's still
some CSS and JavaScript to fix.
The Component World database is pretty up to date. It currently contains
358 (!) elements (descriptions of Tapestry-related components, mixins,
elements, pages, modules, frameworks, and web sites) in a hierarchical
structure. For example, just yesterday I added Thiago's AddRssLink mixin
and the Tapestry-rss module it belongs to, which is listed as part of his
Ars Machina "site".
For each entry the app is tracking its name, description, documentation
URL, demo URL, Tapestry version compatibility, the license, whether it's a
Tapestry-provided component or 3rd party, etc.
The https://github.com/bobharner/ComponentWorld/issues page is an accurate
list of what still needs to be done. Mainly what the app needs is:
1) A security layer (Tapestry-security) for authentication to the pages for
adding new entries and doing admin actions.
2) A few simple crud interfaces for updating the lookup tables in the
database (entry types, source types, licenses, Tapestry versions
3) Set it up to run under Tomcat in our Apache jail where the Hotel Booking
example runs, and point the doc pages to it.
On Wed, Oct 9, 2013 at 4:58 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Wed, 09 Oct 2013 15:55:09 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
> wrote:
>
> Perhaps its time to finish it. It looks good from the screen shots that
>> I've seen. Perhaps it can be seen as community building project.
>>
>
> Agreed. Bob, what's the status of Component World now?
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Wed, 09 Oct 2013 15:55:09 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
wrote:
> Perhaps its time to finish it. It looks good from the screen shots that
> I've seen. Perhaps it can be seen as community building project.
Agreed. Bob, what's the status of Component World now?
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
Perhaps its time to finish it. It looks good from the screen shots that I've seen.
Perhaps it can be seen as community building project.
On Oct 9, 2013, at 2:50 PM, Thiago H de Paula Figueiredo wrote:
> On Wed, 09 Oct 2013 15:18:53 -0300, Lenny Primak <lp...@hope.nyc.ny.us> wrote:
>
>> Bob Harner has already something called a module registry.
>> I think it should be adopted by Tapestry documentation project.
>> No need to create anything new here.
>
> I don't think he actually finished it. At least I can't recall he mentioned that it was ready for use or test. https://github.com/bobharner/ComponentWorld
>
>> Also, even though github is 'in' right now, not everything is on github.
>> lots of projects are hosted on google code, sourceforge, etc.
>> Forcing or pseudo-forcing (i.e. if you are not on github you are not in the registry) isn't a good idea.
>
> We never said that projects outside GitHub wouldn't be included. We just said that *most* projects are on GitHub, so it makes sense to store this registry there.
>
>>
>> On Oct 9, 2013, at 8:42 AM, Thiago H de Paula Figueiredo wrote:
>>
>>> On Wed, 09 Oct 2013 07:50:21 -0300, Barry Books <tr...@gmail.com> wrote:
>>>
>>>> I think there needs to be some repository of 3rd party modules
>>>
>>> Agreed. There's http://tapestry.apache.org/third-party-modules.html, linked on the documentation page. It may not be ideal, but at least that's a start.
>>>
>>>> and I don't think
>>>> the apache site is the place for that. I've been thinking about creating a github project and using that as a way to document what's available. If you have a 3rd party module you could be a contributor and I think it would be pretty easy to create one place to go for info, create bug reports etc.
>>>> I think this could be one step to more cooperation.
>>>
>>> I like the idea. I have some ideas about the distributed configuration JIRA you posted that would make it easier to implement the project above.
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>> Tapestry, Java and Hibernate consultant and developer
>>> http://machina.com.br
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Wed, 09 Oct 2013 15:18:53 -0300, Lenny Primak <lp...@hope.nyc.ny.us>
wrote:
> Bob Harner has already something called a module registry.
> I think it should be adopted by Tapestry documentation project.
> No need to create anything new here.
I don't think he actually finished it. At least I can't recall he
mentioned that it was ready for use or test.
https://github.com/bobharner/ComponentWorld
> Also, even though github is 'in' right now, not everything is on github.
> lots of projects are hosted on google code, sourceforge, etc.
> Forcing or pseudo-forcing (i.e. if you are not on github you are not in
> the registry) isn't a good idea.
We never said that projects outside GitHub wouldn't be included. We just
said that *most* projects are on GitHub, so it makes sense to store this
registry there.
>
> On Oct 9, 2013, at 8:42 AM, Thiago H de Paula Figueiredo wrote:
>
>> On Wed, 09 Oct 2013 07:50:21 -0300, Barry Books <tr...@gmail.com>
>> wrote:
>>
>>> I think there needs to be some repository of 3rd party modules
>>
>> Agreed. There's http://tapestry.apache.org/third-party-modules.html,
>> linked on the documentation page. It may not be ideal, but at least
>> that's a start.
>>
>>> and I don't think
>>> the apache site is the place for that. I've been thinking about
>>> creating a github project and using that as a way to document what's
>>> available. If you have a 3rd party module you could be a contributor
>>> and I think it would be pretty easy to create one place to go for
>>> info, create bug reports etc.
>>> I think this could be one step to more cooperation.
>>
>> I like the idea. I have some ideas about the distributed configuration
>> JIRA you posted that would make it easier to implement the project
>> above.
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Tapestry, Java and Hibernate consultant and developer
>> http://machina.com.br
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
Bob Harner has already something called a module registry.
I think it should be adopted by Tapestry documentation project.
No need to create anything new here.
Also, even though github is 'in' right now, not everything is on github.
lots of projects are hosted on google code, sourceforge, etc.
Forcing or pseudo-forcing (i.e. if you are not on github you are not in the registry)
isn't a good idea.
On Oct 9, 2013, at 8:42 AM, Thiago H de Paula Figueiredo wrote:
> On Wed, 09 Oct 2013 07:50:21 -0300, Barry Books <tr...@gmail.com> wrote:
>
>> I think there needs to be some repository of 3rd party modules
>
> Agreed. There's http://tapestry.apache.org/third-party-modules.html, linked on the documentation page. It may not be ideal, but at least that's a start.
>
>> and I don't think
>> the apache site is the place for that. I've been thinking about creating a github project and using that as a way to document what's available. If you have a 3rd party module you could be a contributor and I think it would be pretty easy to create one place to go for info, create bug reports etc.
>> I think this could be one step to more cooperation.
>
> I like the idea. I have some ideas about the distributed configuration JIRA you posted that would make it easier to implement the project above.
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Wed, 09 Oct 2013 07:50:21 -0300, Barry Books <tr...@gmail.com> wrote:
> I think there needs to be some repository of 3rd party modules
Agreed. There's http://tapestry.apache.org/third-party-modules.html,
linked on the documentation page. It may not be ideal, but at least that's
a start.
> and I don't think
> the apache site is the place for that. I've been thinking about creating
> a github project and using that as a way to document what's available.
> If you have a 3rd party module you could be a contributor and I think it
> would be pretty easy to create one place to go for info, create bug
> reports etc.
> I think this could be one step to more cooperation.
I like the idea. I have some ideas about the distributed configuration
JIRA you posted that would make it easier to implement the project above.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Wed, 09 Oct 2013 09:24:38 -0300, Barry Books <tr...@gmail.com> wrote:
> I think with maven central and github the parts to start something are
> already here. I'd say start building on that and see where it goes.
Yep. Most Tapestry third-party modules are hosted in Github already.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Barry Books <tr...@gmail.com>.
I think with maven central and github the parts to start something are
already here. I'd say start building on that and see where it goes.
On Wed, Oct 9, 2013 at 6:51 AM, Alessio Gambi <ag...@gmail.com> wrote:
> As I said to HLS when we met in London some years ago, we need an open
> MarketPlace where people can easily do their own business: sell software,
> consult experts, browse catalogs of components/pages/services etc.
>
>
> As I see people rising the picks and flames let me also add that:
> - a market place can host/link also open and free projects
>
> - users can 'vote' the quality of the published artifacts, and express
> their opinions
>
> - developers can have some feedback on their work
>
> - <add here what you like >
>
>
> Moreover, despite the failures of 90's-style components market places, now
> everybody is used to AppStores and easy to go solutions that perfectly fit
> the ability of tapestry to embrace new components and module 'almost' for
> free.
>
> Of course it would be great to have it running on tapestry .... ( I have
> in mind several reasons why this choice should benefit to everybody)
>
> BTW, I am also of the idea that, no matter its implementation, such kind
> of things should not be hosted on Apache premises....
>
>
> -- Alessio
>
> On 9-ott-2013, at 12:50, Barry Books <tr...@gmail.com> wrote:
>
> > Lenny I agree with some of what you say and I have a few comments because
> > I've been thinking about this also. I don't really have a problem with 3
> > CDI implementations but I don't think I could find any of them. I think
> > there needs to be some repository of 3rd party modules and I don't think
> > the apache site is the place for that. I've been thinking about creating
> a
> > github project and using that as a way to document what's available. If
> you
> > have a 3rd party module you could be a contributor and I think it would
> be
> > pretty easy to create one place to go for info, create bug reports etc.
> >
> > I think this could be one step to more cooperation.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Alessio Gambi <ag...@gmail.com>.
As I said to HLS when we met in London some years ago, we need an open MarketPlace where people can easily do their own business: sell software, consult experts, browse catalogs of components/pages/services etc.
As I see people rising the picks and flames let me also add that:
- a market place can host/link also open and free projects
- users can 'vote' the quality of the published artifacts, and express their opinions
- developers can have some feedback on their work
- <add here what you like >
Moreover, despite the failures of 90's-style components market places, now everybody is used to AppStores and easy to go solutions that perfectly fit the ability of tapestry to embrace new components and module 'almost' for free.
Of course it would be great to have it running on tapestry .... ( I have in mind several reasons why this choice should benefit to everybody)
BTW, I am also of the idea that, no matter its implementation, such kind of things should not be hosted on Apache premises....
-- Alessio
On 9-ott-2013, at 12:50, Barry Books <tr...@gmail.com> wrote:
> Lenny I agree with some of what you say and I have a few comments because
> I've been thinking about this also. I don't really have a problem with 3
> CDI implementations but I don't think I could find any of them. I think
> there needs to be some repository of 3rd party modules and I don't think
> the apache site is the place for that. I've been thinking about creating a
> github project and using that as a way to document what's available. If you
> have a 3rd party module you could be a contributor and I think it would be
> pretty easy to create one place to go for info, create bug reports etc.
>
> I think this could be one step to more cooperation.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Barry Books <tr...@gmail.com>.
Here are my thoughts on what a GitHub list would be and how it wold work.
GitHub has a feature called gh-pages. If you have a branch called gh-pages
GitHub will build a website from markdown files. Markdown is a simple
markup language. The idea is any one that wants to add their module creates
ticket asking to be a contributor then creates a documentation page and a
repository link. This would provide a list of 3rd party modules with the
data being maintained by the owner of the module.
There are no requirements to host your project on Github and in fact there
is a browser interface for doing this so you would not even need git to
participate. Github also allows an organization to own a repository so it's
possible to delegate the responsibilities and owners can come and go.
I also see benefit in having a Tapestry based site like ComponentWorld and
I don't see the two as mutually exclusive. In fact I believe the Github
list could be the backend data store for a site like ComponentWorld because
there is be a description of the module in markdown and there is plenty of
information in a POM file. I also hope other applications would find this
data useful and I'm thinking about how I could use it if I write a
distributed documentation module.
Barry
On Thu, Oct 10, 2013 at 4:10 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> I just want to point apache-extras.org out as a place for where products
> that are Apache-related but
> not part of Apache products can be hosted. It is based on Google code IIRC.
>
> Uli
>
> On 2013-10-09 12:50, Barry Books wrote:
> > Lenny I agree with some of what you say and I have a few comments because
> > I've been thinking about this also. I don't really have a problem with 3
> > CDI implementations but I don't think I could find any of them. I think
> > there needs to be some repository of 3rd party modules and I don't think
> > the apache site is the place for that. I've been thinking about creating
> a
> > github project and using that as a way to document what's available. If
> you
> > have a 3rd party module you could be a contributor and I think it would
> be
> > pretty easy to create one place to go for info, create bug reports etc.
> >
> > I think this could be one step to more cooperation.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Ulrich Stärk <ul...@spielviel.de>.
I just want to point apache-extras.org out as a place for where products that are Apache-related but
not part of Apache products can be hosted. It is based on Google code IIRC.
Uli
On 2013-10-09 12:50, Barry Books wrote:
> Lenny I agree with some of what you say and I have a few comments because
> I've been thinking about this also. I don't really have a problem with 3
> CDI implementations but I don't think I could find any of them. I think
> there needs to be some repository of 3rd party modules and I don't think
> the apache site is the place for that. I've been thinking about creating a
> github project and using that as a way to document what's available. If you
> have a 3rd party module you could be a contributor and I think it would be
> pretty easy to create one place to go for info, create bug reports etc.
>
> I think this could be one step to more cooperation.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Barry Books <tr...@gmail.com>.
Lenny I agree with some of what you say and I have a few comments because
I've been thinking about this also. I don't really have a problem with 3
CDI implementations but I don't think I could find any of them. I think
there needs to be some repository of 3rd party modules and I don't think
the apache site is the place for that. I've been thinking about creating a
github project and using that as a way to document what's available. If you
have a 3rd party module you could be a contributor and I think it would be
pretty easy to create one place to go for info, create bug reports etc.
I think this could be one step to more cooperation.
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
As much as I hate to say it, just like with the book idea, the Tapestry ecosystem isn't big enough
to have an 'endorsed by' program or any kind of certification. Wish it wasn't so but it is.
For example, let's take CDI support. There are at least 3 implementations, with equal quality as far as I know.
Who is going to be the judge which one gets the stamp of approval? PMC? All committers? Users of the list?
Do you think all three should get approval?
Do you think people are actually going to take a look at all the modules, really take a look at them for quality?
I really don't see this as sustainable long term.
The problem here is more systemic. There is not enough cooperation in the Tapestry world.
There are not enough active committers. Even many 3rd party modules are very duplicative
because their owners want 'their' code 'pure' and not 'contaminate / dump' other's people's
perceived 'inferior' code into their projects.
The solution here is more cooperation and less 'certification'
Thiago, as far as your own modules, I think you are doing great work,
and you should put 'Tapestry Committer and PMC member' with your modules.
(at least I think you are :)
That should carry more than enough weight with people.
On Oct 8, 2013, at 3:09 PM, Thiago H de Paula Figueiredo wrote:
> Hi!
>
> There's an interesting discussion between me and Pieter in https://issues.apache.org/jira/browse/TAP5-64. The gist of it is that he wants portlets support in Tapestry, there's tapestry5-portlets, which is written by at least two Tapestry committers, but the consensus here is to not add more modules to the Tapestry project itself due to the time to support it. His argument, and I kind of agree with him, is that having tapestry5-portlets in the Tapestry project is a seal of quality for the portlet support.
>
> I propose a compromise: in the Tapestry documentation site, a page containing third-party Tapestry and Tapestry-IoC modules which the Tapestry team recommends due to their proven quality. For example, tapestry-security is written by Kalle Korhonen, which is both a Tapestry and Shiro committer. Or tapestry-url-rewriter, written by me and Robert Zeigler and not in Tapestry itself anymore. For a given module to be listed there, I suggest that we carry a vote just like we do with new committers. In addition, we could have a page in the Tapestry documentation with some documentation.
>
> What do you guys think?
>
> Cheers!
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Proposal for a list of modules recommended by the Tapestry team
Posted by Lance Java <la...@googlemail.com>.
I prefer the idea of a registry where all tapestry add ons can get a
mention with the ability to have the community rate and give feedback. Let
the user decide whether the library is ok by croudsourcing feedback.