You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Илья Нарыжный <ph...@ydn.ru> on 2016/01/31 01:38:23 UTC
WicketStuff status and future; awesome-wicket project
Guys,
Please help me understand what's status of wicketstuff project and
what's a roadmap for the future?
I'm asking, because from community stand point I don't see so much pros.
Pros:
1) It's easy to have all wicket related projects in place and observe at once.
But this pros can be easily done by creating a library of links to all
wicket related project. What else do you have in mind?
List of cons is longer:
1) It's hard to manage issues baceuse there are multiple projects and
multiple authors.
2) It's expected that versions of wicketstuff projects are in sync
with wicket version. But in reality, as I can see, significant part of
projects update just pom.xml to a newer version. So: it brings
redundant versions for those projects
3) Hard to search. Yes - google can find everything, but on github
it's much more reasonable to have separate repository per project.
4) When project jumps to wicketstuff: all dependencies should be
updated. And sometimes it's not easy: for example if you include
ProjectA which includes ProjectB and projectB jump to wicketstuff.
5) And finally: most of projects are already outdated and not
supported by authors
For my own purposes I started to collect wicket related projects here:
https://github.com/PhantomYdn/awesome-wicket
Collection of links might be move beneficial for the community rather
that moving everything under single project (WicketStuff), I think.
Thanks,
Ilya
---------------------------------------------
Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff status and future; awesome-wicket project
Posted by Štefan Šimík <st...@gmail.com>.
I find the list excellent. I had no idea, about so many useful things out
there!
Thank you for your effort!
It definitely goes to one of primary wicket related links ;)
On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный <ph...@ydn.ru> wrote:
> Guys,
>
> Please help me understand what's status of wicketstuff project and
> what's a roadmap for the future?
>
> I'm asking, because from community stand point I don't see so much pros.
>
> Pros:
>
> 1) It's easy to have all wicket related projects in place and observe at
> once.
>
> But this pros can be easily done by creating a library of links to all
> wicket related project. What else do you have in mind?
>
> List of cons is longer:
>
> 1) It's hard to manage issues baceuse there are multiple projects and
> multiple authors.
> 2) It's expected that versions of wicketstuff projects are in sync
> with wicket version. But in reality, as I can see, significant part of
> projects update just pom.xml to a newer version. So: it brings
> redundant versions for those projects
> 3) Hard to search. Yes - google can find everything, but on github
> it's much more reasonable to have separate repository per project.
> 4) When project jumps to wicketstuff: all dependencies should be
> updated. And sometimes it's not easy: for example if you include
> ProjectA which includes ProjectB and projectB jump to wicketstuff.
> 5) And finally: most of projects are already outdated and not
> supported by authors
>
> For my own purposes I started to collect wicket related projects here:
> https://github.com/PhantomYdn/awesome-wicket
> Collection of links might be move beneficial for the community rather
> that moving everything under single project (WicketStuff), I think.
>
> Thanks,
>
> Ilya
>
> ---------------------------------------------
> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: WicketStuff status and future; awesome-wicket project
Posted by Sebastien <se...@gmail.com>.
Hi Ilya
wicket-calendar is now little bit old...
A more recent implementation (fullcalendar v2) can be found in the
wicket-jquery-ui project (artifact: wicket-jquery-ui-calendar)
Also, an implementation of the Kendo UI library exists in the same project
(artifact: wicket-kendo-ui)
Thanks & best regards,
Sebastien.
Re: WicketStuff status and future; awesome-wicket project
Posted by Francois Meillet <fr...@gmail.com>.
Hi Ilya,
I just use google !
François
Le 4 févr. 2016 à 01:28, Илья Нарыжный <ph...@ydn.ru> a écrit :
> François,
>
> Thanks for the list! Just few questions/comments:
>
> 1) How did you collect that lists? Probably I can dig more by that way.
> 2) Regarding solutions: I don't want to have in the list sites - under
> solutions I assume just software which can be installed standalone.
>
> Regards,
> Ilya
>
> ---------------------------------------------
> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>
> 2016-02-02 23:43 GMT-08:00 Francois Meillet <fr...@gmail.com>:
>> Hi Ilya,
>>
>>
>> You can add theses products :
>>
>>
>> Under Web Frameworks
>>
>> Apache OODT http://oodt.apache.org
>> Data grid framework for transparent search and discovery of disparate science resources
>>
>> Apache Openmeetings http://openmeetings.apache.org
>> Apache Openmeetings provides video conferencing, instant messaging, white board, collaborative document editing and other groupware tools
>>
>> Apache Nutch https://nutch.apache.org
>> Apache Nutch is a highly extensible and scalable open source web crawler software project
>>
>> Apache Syncope https://syncope.apache.org
>> Apache Syncope is an Open Source system for managing digital identities in enterprise environments
>>
>> Dcm4che http://www.dcm4che.org
>> Open Source Clinical Image and Object Management Dcm4che
>>
>> WebAnno https://webanno.github.io/webanno/
>> WebAnno, general purpose web-based annotation tool for a wide range of linguistic annotations
>>
>>
>>
>>
>> Under Solutions
>>
>> CA http://www.ca.com
>> Identity Governance products
>>
>> Callfire https://www.callfire.com
>> Phone Numbers, Voice Broadcasting & Auto Dialer Software
>>
>> Cqrollcall http://cqrollcall.com/products-services/cqrc-engage/
>> All-in-one tool to execute advocacy campaigns
>>
>> Flowzone http://www.flowzone.com
>> The planet's most adaptable project management
>>
>> GeoServer http://geoserver.org
>> GeoServer is an open source server for sharing geospatial data
>>
>> Jfrog http://www.jfrog.com
>> Managing Binaries for Maven Repository, Docker, .Net, Ruby and More
>>
>> Jumio https://www.jumio.com
>> Scan and Validate Credit Cards and IDs
>>
>> Multicom http://multicom.co.uk
>> Online travel, booking, agent, management software multicom
>>
>> OpenCRS http://www.openroadsconsulting.com/intelligent-transportation-systems/products/opencrs/
>> Data Fusion and Condition Reporting Tool OpenCRS
>>
>> Servoy https://www.servoy.com
>> Business Application Platform for ISVs
>>
>> Soweroasis http://www.poweroasis.com
>> Energy management solutions
>>
>> Tentelemed http://www.tentelemed.com
>> Trusted Information systems for health professionals
>>
>>
>>
>> François
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Le 2 févr. 2016 à 08:26, Tobias Soloschenko <to...@googlemail.com> a écrit :
>>
>>> Hi Ilya,
>>>
>>> In your list the nashorn project is missing - it is a way to allow users to execute javascript on server side. I am going to add it to the list of submodules, now.
>>>
>>> Anyway it is up to the community to update the wiki or to bring projects up to date and this would be a lot harder if it would not be at a central place.
>>>
>>> kind regards
>>>
>>> Tobias
>>>
>>>> Am 31.01.2016 um 23:41 schrieb Илья Нарыжный <ph...@ydn.ru>:
>>>>
>>>> Thank you, Martin!
>>>> After you reply I understand that significant part of my concerns
>>>> actually related to moving everything under single repository (Core).
>>>> I mean, that migration of a project just to community group will help
>>>> pretty much the same benefits: ability to take over some project after
>>>> loosing of interest from author.
>>>> Btw, I also recommend to establish one more "condition" for moving
>>>> project to wicketstuff: delete source repository or mention that
>>>> project has been moved. I know a couple of projects for which it's
>>>> hard to understand that they were moved and newer version can be found
>>>> in wicketstuff.
>>>> Also, as I can see, not all good projects have wiki page or README.md
>>>> well prepared...
>>>>
>>>> Regards,
>>>>
>>>> Ilya
>>>> ---------------------------------------------
>>>> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>>>>
>>>> 2016-01-31 12:45 GMT-08:00 Martin Grigorov <mg...@apache.org>:
>>>>> Hi,
>>>>>
>>>>>
>>>>>> On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный <ph...@ydn.ru> wrote:
>>>>>>
>>>>>> Guys,
>>>>>>
>>>>>> Please help me understand what's status of wicketstuff project and
>>>>>> what's a roadmap for the future?
>>>>>>
>>>>>> I'm asking, because from community stand point I don't see so much pros.
>>>>>>
>>>>>> Pros:
>>>>>>
>>>>>> 1) It's easy to have all wicket related projects in place and observe at
>>>>>> once.
>>>>>>
>>>>>> But this pros can be easily done by creating a library of links to all
>>>>>> wicket related project. What else do you have in mind?
>>>>>
>>>>> The biggest pros is that WicketStuff is already known to the community.
>>>>> Whenever someone needs some Wicket integration I guess Google's first
>>>>> recommendation would be WicketStuff.
>>>>>
>>>>>
>>>>>>
>>>>>> List of cons is longer:
>>>>>>
>>>>>> 1) It's hard to manage issues baceuse there are multiple projects and
>>>>>> multiple authors.
>>>>>
>>>>> By "donating" a project to WicketStuff authors hope that other people will
>>>>> also use it and improve it,
>>>>> i.e. implement new features and fix bugs.
>>>>> Every author of a WicketStuff module is a member of the Collaborators team
>>>>> and thus is notified whenever
>>>>> there is a issue report for any project. I personally have fixed several
>>>>> issues for projects which I either use or I care about.
>>>>> There are other people doing this too.
>>>>>
>>>>>
>>>>>> 2) It's expected that versions of wicketstuff projects are in sync
>>>>>> with wicket version. But in reality, as I can see, significant part of
>>>>>> projects update just pom.xml to a newer version. So: it brings
>>>>>> redundant versions for those projects
>>>>>
>>>>> Pros:
>>>>> 1) the projects are migrated to 6.0.0/7.0.0 by others, not by the original
>>>>> authors
>>>>> 2) the projects are build with the latest version of Wicket and their tests
>>>>> are executed
>>>>> 3) I use WicketStuff build to validate Wicket's releases themselves
>>>>>
>>>>>
>>>>>> 3) Hard to search. Yes - google can find everything, but on github
>>>>>> it's much more reasonable to have separate repository per project.
>>>>>
>>>>> I think it is easier to search at one known place than many unknown ones
>>>>>
>>>>>
>>>>>> 4) When project jumps to wicketstuff: all dependencies should be
>>>>>> updated. And sometimes it's not easy: for example if you include
>>>>>> ProjectA which includes ProjectB and projectB jump to wicketstuff.
>>>>>
>>>>> In this case you can still use ProjectB versionBeforeWicketStuff
>>>>>
>>>>>
>>>>>> 5) And finally: most of projects are already outdated and not
>>>>>> supported by authors
>>>>>
>>>>> From time to time contributors appear with some fixes/improvements.
>>>>> Very recently a user revived Jamon integration from wicket-1.4.x branch!
>>>>>
>>>>>
>>>>>>
>>>>>> For my own purposes I started to collect wicket related projects here:
>>>>>> https://github.com/PhantomYdn/awesome-wicket
>>>>>
>>>>>
>>>>> This is great initiative! Thank you!
>>>>>
>>>>> But what you said for WicketStuff I can say for this list too - many of the
>>>>> projects are outdated and not supported by their authors.
>>>>> Most probably they will never be updated to a newer version.
>>>>> Someone may fork them and update, but then it becomes even harder for other
>>>>> users to find the best solution for a problem.
>>>>>
>>>>>
>>>>>>
>>>>>> Collection of links might be move beneficial for the community rather
>>>>>> that moving everything under single project (WicketStuff), I think.
>>>>>
>>>>> Maybe you are right, maybe not!
>>>>>
>>>>> My biggest problem with WicketStuff is that it becomes bigger and bigger
>>>>> and releasing it takes more and more time.
>>>>> It was almost 6 hours at some point. Now we disabled the deployment of
>>>>> -examples modules to Maven Central and it is back to ~1h, so please keep
>>>>> them coming! :-)
>>>>>
>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Ilya
>>>>>>
>>>>>> ---------------------------------------------
>>>>>> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
Re: WicketStuff status and future; awesome-wicket project
Posted by Илья Нарыжный <ph...@ydn.ru>.
François,
Thanks for the list! Just few questions/comments:
1) How did you collect that lists? Probably I can dig more by that way.
2) Regarding solutions: I don't want to have in the list sites - under
solutions I assume just software which can be installed standalone.
Regards,
Ilya
---------------------------------------------
Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
2016-02-02 23:43 GMT-08:00 Francois Meillet <fr...@gmail.com>:
> Hi Ilya,
>
>
> You can add theses products :
>
>
> Under Web Frameworks
>
> Apache OODT http://oodt.apache.org
> Data grid framework for transparent search and discovery of disparate science resources
>
> Apache Openmeetings http://openmeetings.apache.org
> Apache Openmeetings provides video conferencing, instant messaging, white board, collaborative document editing and other groupware tools
>
> Apache Nutch https://nutch.apache.org
> Apache Nutch is a highly extensible and scalable open source web crawler software project
>
> Apache Syncope https://syncope.apache.org
> Apache Syncope is an Open Source system for managing digital identities in enterprise environments
>
> Dcm4che http://www.dcm4che.org
> Open Source Clinical Image and Object Management Dcm4che
>
> WebAnno https://webanno.github.io/webanno/
> WebAnno, general purpose web-based annotation tool for a wide range of linguistic annotations
>
>
>
>
> Under Solutions
>
> CA http://www.ca.com
> Identity Governance products
>
> Callfire https://www.callfire.com
> Phone Numbers, Voice Broadcasting & Auto Dialer Software
>
> Cqrollcall http://cqrollcall.com/products-services/cqrc-engage/
> All-in-one tool to execute advocacy campaigns
>
> Flowzone http://www.flowzone.com
> The planet's most adaptable project management
>
> GeoServer http://geoserver.org
> GeoServer is an open source server for sharing geospatial data
>
> Jfrog http://www.jfrog.com
> Managing Binaries for Maven Repository, Docker, .Net, Ruby and More
>
> Jumio https://www.jumio.com
> Scan and Validate Credit Cards and IDs
>
> Multicom http://multicom.co.uk
> Online travel, booking, agent, management software multicom
>
> OpenCRS http://www.openroadsconsulting.com/intelligent-transportation-systems/products/opencrs/
> Data Fusion and Condition Reporting Tool OpenCRS
>
> Servoy https://www.servoy.com
> Business Application Platform for ISVs
>
> Soweroasis http://www.poweroasis.com
> Energy management solutions
>
> Tentelemed http://www.tentelemed.com
> Trusted Information systems for health professionals
>
>
>
> François
>
>
>
>
>
>
>
>
>
>
>
> Le 2 févr. 2016 à 08:26, Tobias Soloschenko <to...@googlemail.com> a écrit :
>
>> Hi Ilya,
>>
>> In your list the nashorn project is missing - it is a way to allow users to execute javascript on server side. I am going to add it to the list of submodules, now.
>>
>> Anyway it is up to the community to update the wiki or to bring projects up to date and this would be a lot harder if it would not be at a central place.
>>
>> kind regards
>>
>> Tobias
>>
>>> Am 31.01.2016 um 23:41 schrieb Илья Нарыжный <ph...@ydn.ru>:
>>>
>>> Thank you, Martin!
>>> After you reply I understand that significant part of my concerns
>>> actually related to moving everything under single repository (Core).
>>> I mean, that migration of a project just to community group will help
>>> pretty much the same benefits: ability to take over some project after
>>> loosing of interest from author.
>>> Btw, I also recommend to establish one more "condition" for moving
>>> project to wicketstuff: delete source repository or mention that
>>> project has been moved. I know a couple of projects for which it's
>>> hard to understand that they were moved and newer version can be found
>>> in wicketstuff.
>>> Also, as I can see, not all good projects have wiki page or README.md
>>> well prepared...
>>>
>>> Regards,
>>>
>>> Ilya
>>> ---------------------------------------------
>>> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>>>
>>> 2016-01-31 12:45 GMT-08:00 Martin Grigorov <mg...@apache.org>:
>>>> Hi,
>>>>
>>>>
>>>>> On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный <ph...@ydn.ru> wrote:
>>>>>
>>>>> Guys,
>>>>>
>>>>> Please help me understand what's status of wicketstuff project and
>>>>> what's a roadmap for the future?
>>>>>
>>>>> I'm asking, because from community stand point I don't see so much pros.
>>>>>
>>>>> Pros:
>>>>>
>>>>> 1) It's easy to have all wicket related projects in place and observe at
>>>>> once.
>>>>>
>>>>> But this pros can be easily done by creating a library of links to all
>>>>> wicket related project. What else do you have in mind?
>>>>
>>>> The biggest pros is that WicketStuff is already known to the community.
>>>> Whenever someone needs some Wicket integration I guess Google's first
>>>> recommendation would be WicketStuff.
>>>>
>>>>
>>>>>
>>>>> List of cons is longer:
>>>>>
>>>>> 1) It's hard to manage issues baceuse there are multiple projects and
>>>>> multiple authors.
>>>>
>>>> By "donating" a project to WicketStuff authors hope that other people will
>>>> also use it and improve it,
>>>> i.e. implement new features and fix bugs.
>>>> Every author of a WicketStuff module is a member of the Collaborators team
>>>> and thus is notified whenever
>>>> there is a issue report for any project. I personally have fixed several
>>>> issues for projects which I either use or I care about.
>>>> There are other people doing this too.
>>>>
>>>>
>>>>> 2) It's expected that versions of wicketstuff projects are in sync
>>>>> with wicket version. But in reality, as I can see, significant part of
>>>>> projects update just pom.xml to a newer version. So: it brings
>>>>> redundant versions for those projects
>>>>
>>>> Pros:
>>>> 1) the projects are migrated to 6.0.0/7.0.0 by others, not by the original
>>>> authors
>>>> 2) the projects are build with the latest version of Wicket and their tests
>>>> are executed
>>>> 3) I use WicketStuff build to validate Wicket's releases themselves
>>>>
>>>>
>>>>> 3) Hard to search. Yes - google can find everything, but on github
>>>>> it's much more reasonable to have separate repository per project.
>>>>
>>>> I think it is easier to search at one known place than many unknown ones
>>>>
>>>>
>>>>> 4) When project jumps to wicketstuff: all dependencies should be
>>>>> updated. And sometimes it's not easy: for example if you include
>>>>> ProjectA which includes ProjectB and projectB jump to wicketstuff.
>>>>
>>>> In this case you can still use ProjectB versionBeforeWicketStuff
>>>>
>>>>
>>>>> 5) And finally: most of projects are already outdated and not
>>>>> supported by authors
>>>>
>>>> From time to time contributors appear with some fixes/improvements.
>>>> Very recently a user revived Jamon integration from wicket-1.4.x branch!
>>>>
>>>>
>>>>>
>>>>> For my own purposes I started to collect wicket related projects here:
>>>>> https://github.com/PhantomYdn/awesome-wicket
>>>>
>>>>
>>>> This is great initiative! Thank you!
>>>>
>>>> But what you said for WicketStuff I can say for this list too - many of the
>>>> projects are outdated and not supported by their authors.
>>>> Most probably they will never be updated to a newer version.
>>>> Someone may fork them and update, but then it becomes even harder for other
>>>> users to find the best solution for a problem.
>>>>
>>>>
>>>>>
>>>>> Collection of links might be move beneficial for the community rather
>>>>> that moving everything under single project (WicketStuff), I think.
>>>>
>>>> Maybe you are right, maybe not!
>>>>
>>>> My biggest problem with WicketStuff is that it becomes bigger and bigger
>>>> and releasing it takes more and more time.
>>>> It was almost 6 hours at some point. Now we disabled the deployment of
>>>> -examples modules to Maven Central and it is back to ~1h, so please keep
>>>> them coming! :-)
>>>>
>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Ilya
>>>>>
>>>>> ---------------------------------------------
>>>>> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff status and future; awesome-wicket project
Posted by Francois Meillet <fr...@gmail.com>.
Hi Ilya,
You can add theses products :
Under Web Frameworks
Apache OODT http://oodt.apache.org
Data grid framework for transparent search and discovery of disparate science resources
Apache Openmeetings http://openmeetings.apache.org
Apache Openmeetings provides video conferencing, instant messaging, white board, collaborative document editing and other groupware tools
Apache Nutch https://nutch.apache.org
Apache Nutch is a highly extensible and scalable open source web crawler software project
Apache Syncope https://syncope.apache.org
Apache Syncope is an Open Source system for managing digital identities in enterprise environments
Dcm4che http://www.dcm4che.org
Open Source Clinical Image and Object Management Dcm4che
WebAnno https://webanno.github.io/webanno/
WebAnno, general purpose web-based annotation tool for a wide range of linguistic annotations
Under Solutions
CA http://www.ca.com
Identity Governance products
Callfire https://www.callfire.com
Phone Numbers, Voice Broadcasting & Auto Dialer Software
Cqrollcall http://cqrollcall.com/products-services/cqrc-engage/
All-in-one tool to execute advocacy campaigns
Flowzone http://www.flowzone.com
The planet's most adaptable project management
GeoServer http://geoserver.org
GeoServer is an open source server for sharing geospatial data
Jfrog http://www.jfrog.com
Managing Binaries for Maven Repository, Docker, .Net, Ruby and More
Jumio https://www.jumio.com
Scan and Validate Credit Cards and IDs
Multicom http://multicom.co.uk
Online travel, booking, agent, management software multicom
OpenCRS http://www.openroadsconsulting.com/intelligent-transportation-systems/products/opencrs/
Data Fusion and Condition Reporting Tool OpenCRS
Servoy https://www.servoy.com
Business Application Platform for ISVs
Soweroasis http://www.poweroasis.com
Energy management solutions
Tentelemed http://www.tentelemed.com
Trusted Information systems for health professionals
François
Le 2 févr. 2016 à 08:26, Tobias Soloschenko <to...@googlemail.com> a écrit :
> Hi Ilya,
>
> In your list the nashorn project is missing - it is a way to allow users to execute javascript on server side. I am going to add it to the list of submodules, now.
>
> Anyway it is up to the community to update the wiki or to bring projects up to date and this would be a lot harder if it would not be at a central place.
>
> kind regards
>
> Tobias
>
>> Am 31.01.2016 um 23:41 schrieb Илья Нарыжный <ph...@ydn.ru>:
>>
>> Thank you, Martin!
>> After you reply I understand that significant part of my concerns
>> actually related to moving everything under single repository (Core).
>> I mean, that migration of a project just to community group will help
>> pretty much the same benefits: ability to take over some project after
>> loosing of interest from author.
>> Btw, I also recommend to establish one more "condition" for moving
>> project to wicketstuff: delete source repository or mention that
>> project has been moved. I know a couple of projects for which it's
>> hard to understand that they were moved and newer version can be found
>> in wicketstuff.
>> Also, as I can see, not all good projects have wiki page or README.md
>> well prepared...
>>
>> Regards,
>>
>> Ilya
>> ---------------------------------------------
>> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>>
>> 2016-01-31 12:45 GMT-08:00 Martin Grigorov <mg...@apache.org>:
>>> Hi,
>>>
>>>
>>>> On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный <ph...@ydn.ru> wrote:
>>>>
>>>> Guys,
>>>>
>>>> Please help me understand what's status of wicketstuff project and
>>>> what's a roadmap for the future?
>>>>
>>>> I'm asking, because from community stand point I don't see so much pros.
>>>>
>>>> Pros:
>>>>
>>>> 1) It's easy to have all wicket related projects in place and observe at
>>>> once.
>>>>
>>>> But this pros can be easily done by creating a library of links to all
>>>> wicket related project. What else do you have in mind?
>>>
>>> The biggest pros is that WicketStuff is already known to the community.
>>> Whenever someone needs some Wicket integration I guess Google's first
>>> recommendation would be WicketStuff.
>>>
>>>
>>>>
>>>> List of cons is longer:
>>>>
>>>> 1) It's hard to manage issues baceuse there are multiple projects and
>>>> multiple authors.
>>>
>>> By "donating" a project to WicketStuff authors hope that other people will
>>> also use it and improve it,
>>> i.e. implement new features and fix bugs.
>>> Every author of a WicketStuff module is a member of the Collaborators team
>>> and thus is notified whenever
>>> there is a issue report for any project. I personally have fixed several
>>> issues for projects which I either use or I care about.
>>> There are other people doing this too.
>>>
>>>
>>>> 2) It's expected that versions of wicketstuff projects are in sync
>>>> with wicket version. But in reality, as I can see, significant part of
>>>> projects update just pom.xml to a newer version. So: it brings
>>>> redundant versions for those projects
>>>
>>> Pros:
>>> 1) the projects are migrated to 6.0.0/7.0.0 by others, not by the original
>>> authors
>>> 2) the projects are build with the latest version of Wicket and their tests
>>> are executed
>>> 3) I use WicketStuff build to validate Wicket's releases themselves
>>>
>>>
>>>> 3) Hard to search. Yes - google can find everything, but on github
>>>> it's much more reasonable to have separate repository per project.
>>>
>>> I think it is easier to search at one known place than many unknown ones
>>>
>>>
>>>> 4) When project jumps to wicketstuff: all dependencies should be
>>>> updated. And sometimes it's not easy: for example if you include
>>>> ProjectA which includes ProjectB and projectB jump to wicketstuff.
>>>
>>> In this case you can still use ProjectB versionBeforeWicketStuff
>>>
>>>
>>>> 5) And finally: most of projects are already outdated and not
>>>> supported by authors
>>>
>>> From time to time contributors appear with some fixes/improvements.
>>> Very recently a user revived Jamon integration from wicket-1.4.x branch!
>>>
>>>
>>>>
>>>> For my own purposes I started to collect wicket related projects here:
>>>> https://github.com/PhantomYdn/awesome-wicket
>>>
>>>
>>> This is great initiative! Thank you!
>>>
>>> But what you said for WicketStuff I can say for this list too - many of the
>>> projects are outdated and not supported by their authors.
>>> Most probably they will never be updated to a newer version.
>>> Someone may fork them and update, but then it becomes even harder for other
>>> users to find the best solution for a problem.
>>>
>>>
>>>>
>>>> Collection of links might be move beneficial for the community rather
>>>> that moving everything under single project (WicketStuff), I think.
>>>
>>> Maybe you are right, maybe not!
>>>
>>> My biggest problem with WicketStuff is that it becomes bigger and bigger
>>> and releasing it takes more and more time.
>>> It was almost 6 hours at some point. Now we disabled the deployment of
>>> -examples modules to Maven Central and it is back to ~1h, so please keep
>>> them coming! :-)
>>>
>>>
>>>>
>>>> Thanks,
>>>>
>>>> Ilya
>>>>
>>>> ---------------------------------------------
>>>> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
Re: WicketStuff status and future; awesome-wicket project
Posted by Tobias Soloschenko <to...@googlemail.com>.
Hi Ilya,
In your list the nashorn project is missing - it is a way to allow users to execute javascript on server side. I am going to add it to the list of submodules, now.
Anyway it is up to the community to update the wiki or to bring projects up to date and this would be a lot harder if it would not be at a central place.
kind regards
Tobias
> Am 31.01.2016 um 23:41 schrieb Илья Нарыжный <ph...@ydn.ru>:
>
> Thank you, Martin!
> After you reply I understand that significant part of my concerns
> actually related to moving everything under single repository (Core).
> I mean, that migration of a project just to community group will help
> pretty much the same benefits: ability to take over some project after
> loosing of interest from author.
> Btw, I also recommend to establish one more "condition" for moving
> project to wicketstuff: delete source repository or mention that
> project has been moved. I know a couple of projects for which it's
> hard to understand that they were moved and newer version can be found
> in wicketstuff.
> Also, as I can see, not all good projects have wiki page or README.md
> well prepared...
>
> Regards,
>
> Ilya
> ---------------------------------------------
> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>
> 2016-01-31 12:45 GMT-08:00 Martin Grigorov <mg...@apache.org>:
>> Hi,
>>
>>
>>> On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный <ph...@ydn.ru> wrote:
>>>
>>> Guys,
>>>
>>> Please help me understand what's status of wicketstuff project and
>>> what's a roadmap for the future?
>>>
>>> I'm asking, because from community stand point I don't see so much pros.
>>>
>>> Pros:
>>>
>>> 1) It's easy to have all wicket related projects in place and observe at
>>> once.
>>>
>>> But this pros can be easily done by creating a library of links to all
>>> wicket related project. What else do you have in mind?
>>
>> The biggest pros is that WicketStuff is already known to the community.
>> Whenever someone needs some Wicket integration I guess Google's first
>> recommendation would be WicketStuff.
>>
>>
>>>
>>> List of cons is longer:
>>>
>>> 1) It's hard to manage issues baceuse there are multiple projects and
>>> multiple authors.
>>
>> By "donating" a project to WicketStuff authors hope that other people will
>> also use it and improve it,
>> i.e. implement new features and fix bugs.
>> Every author of a WicketStuff module is a member of the Collaborators team
>> and thus is notified whenever
>> there is a issue report for any project. I personally have fixed several
>> issues for projects which I either use or I care about.
>> There are other people doing this too.
>>
>>
>>> 2) It's expected that versions of wicketstuff projects are in sync
>>> with wicket version. But in reality, as I can see, significant part of
>>> projects update just pom.xml to a newer version. So: it brings
>>> redundant versions for those projects
>>
>> Pros:
>> 1) the projects are migrated to 6.0.0/7.0.0 by others, not by the original
>> authors
>> 2) the projects are build with the latest version of Wicket and their tests
>> are executed
>> 3) I use WicketStuff build to validate Wicket's releases themselves
>>
>>
>>> 3) Hard to search. Yes - google can find everything, but on github
>>> it's much more reasonable to have separate repository per project.
>>
>> I think it is easier to search at one known place than many unknown ones
>>
>>
>>> 4) When project jumps to wicketstuff: all dependencies should be
>>> updated. And sometimes it's not easy: for example if you include
>>> ProjectA which includes ProjectB and projectB jump to wicketstuff.
>>
>> In this case you can still use ProjectB versionBeforeWicketStuff
>>
>>
>>> 5) And finally: most of projects are already outdated and not
>>> supported by authors
>>
>> From time to time contributors appear with some fixes/improvements.
>> Very recently a user revived Jamon integration from wicket-1.4.x branch!
>>
>>
>>>
>>> For my own purposes I started to collect wicket related projects here:
>>> https://github.com/PhantomYdn/awesome-wicket
>>
>>
>> This is great initiative! Thank you!
>>
>> But what you said for WicketStuff I can say for this list too - many of the
>> projects are outdated and not supported by their authors.
>> Most probably they will never be updated to a newer version.
>> Someone may fork them and update, but then it becomes even harder for other
>> users to find the best solution for a problem.
>>
>>
>>>
>>> Collection of links might be move beneficial for the community rather
>>> that moving everything under single project (WicketStuff), I think.
>>
>> Maybe you are right, maybe not!
>>
>> My biggest problem with WicketStuff is that it becomes bigger and bigger
>> and releasing it takes more and more time.
>> It was almost 6 hours at some point. Now we disabled the deployment of
>> -examples modules to Maven Central and it is back to ~1h, so please keep
>> them coming! :-)
>>
>>
>>>
>>> Thanks,
>>>
>>> Ilya
>>>
>>> ---------------------------------------------
>>> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff status and future; awesome-wicket project
Posted by Илья Нарыжный <ph...@ydn.ru>.
Thank you, Martin!
After you reply I understand that significant part of my concerns
actually related to moving everything under single repository (Core).
I mean, that migration of a project just to community group will help
pretty much the same benefits: ability to take over some project after
loosing of interest from author.
Btw, I also recommend to establish one more "condition" for moving
project to wicketstuff: delete source repository or mention that
project has been moved. I know a couple of projects for which it's
hard to understand that they were moved and newer version can be found
in wicketstuff.
Also, as I can see, not all good projects have wiki page or README.md
well prepared...
Regards,
Ilya
---------------------------------------------
Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
2016-01-31 12:45 GMT-08:00 Martin Grigorov <mg...@apache.org>:
> Hi,
>
>
> On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный <ph...@ydn.ru> wrote:
>
>> Guys,
>>
>> Please help me understand what's status of wicketstuff project and
>> what's a roadmap for the future?
>>
>> I'm asking, because from community stand point I don't see so much pros.
>>
>> Pros:
>>
>> 1) It's easy to have all wicket related projects in place and observe at
>> once.
>>
>> But this pros can be easily done by creating a library of links to all
>> wicket related project. What else do you have in mind?
>>
>
> The biggest pros is that WicketStuff is already known to the community.
> Whenever someone needs some Wicket integration I guess Google's first
> recommendation would be WicketStuff.
>
>
>>
>> List of cons is longer:
>>
>> 1) It's hard to manage issues baceuse there are multiple projects and
>> multiple authors.
>>
>
> By "donating" a project to WicketStuff authors hope that other people will
> also use it and improve it,
> i.e. implement new features and fix bugs.
> Every author of a WicketStuff module is a member of the Collaborators team
> and thus is notified whenever
> there is a issue report for any project. I personally have fixed several
> issues for projects which I either use or I care about.
> There are other people doing this too.
>
>
>> 2) It's expected that versions of wicketstuff projects are in sync
>> with wicket version. But in reality, as I can see, significant part of
>> projects update just pom.xml to a newer version. So: it brings
>> redundant versions for those projects
>>
>
> Pros:
> 1) the projects are migrated to 6.0.0/7.0.0 by others, not by the original
> authors
> 2) the projects are build with the latest version of Wicket and their tests
> are executed
> 3) I use WicketStuff build to validate Wicket's releases themselves
>
>
>> 3) Hard to search. Yes - google can find everything, but on github
>> it's much more reasonable to have separate repository per project.
>>
>
> I think it is easier to search at one known place than many unknown ones
>
>
>> 4) When project jumps to wicketstuff: all dependencies should be
>> updated. And sometimes it's not easy: for example if you include
>> ProjectA which includes ProjectB and projectB jump to wicketstuff.
>>
>
> In this case you can still use ProjectB versionBeforeWicketStuff
>
>
>> 5) And finally: most of projects are already outdated and not
>> supported by authors
>>
>
> From time to time contributors appear with some fixes/improvements.
> Very recently a user revived Jamon integration from wicket-1.4.x branch!
>
>
>>
>> For my own purposes I started to collect wicket related projects here:
>> https://github.com/PhantomYdn/awesome-wicket
>
>
> This is great initiative! Thank you!
>
> But what you said for WicketStuff I can say for this list too - many of the
> projects are outdated and not supported by their authors.
> Most probably they will never be updated to a newer version.
> Someone may fork them and update, but then it becomes even harder for other
> users to find the best solution for a problem.
>
>
>>
>> Collection of links might be move beneficial for the community rather
>> that moving everything under single project (WicketStuff), I think.
>>
>
> Maybe you are right, maybe not!
>
> My biggest problem with WicketStuff is that it becomes bigger and bigger
> and releasing it takes more and more time.
> It was almost 6 hours at some point. Now we disabled the deployment of
> -examples modules to Maven Central and it is back to ~1h, so please keep
> them coming! :-)
>
>
>>
>> Thanks,
>>
>> Ilya
>>
>> ---------------------------------------------
>> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: WicketStuff status and future; awesome-wicket project
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный <ph...@ydn.ru> wrote:
> Guys,
>
> Please help me understand what's status of wicketstuff project and
> what's a roadmap for the future?
>
> I'm asking, because from community stand point I don't see so much pros.
>
> Pros:
>
> 1) It's easy to have all wicket related projects in place and observe at
> once.
>
> But this pros can be easily done by creating a library of links to all
> wicket related project. What else do you have in mind?
>
The biggest pros is that WicketStuff is already known to the community.
Whenever someone needs some Wicket integration I guess Google's first
recommendation would be WicketStuff.
>
> List of cons is longer:
>
> 1) It's hard to manage issues baceuse there are multiple projects and
> multiple authors.
>
By "donating" a project to WicketStuff authors hope that other people will
also use it and improve it,
i.e. implement new features and fix bugs.
Every author of a WicketStuff module is a member of the Collaborators team
and thus is notified whenever
there is a issue report for any project. I personally have fixed several
issues for projects which I either use or I care about.
There are other people doing this too.
> 2) It's expected that versions of wicketstuff projects are in sync
> with wicket version. But in reality, as I can see, significant part of
> projects update just pom.xml to a newer version. So: it brings
> redundant versions for those projects
>
Pros:
1) the projects are migrated to 6.0.0/7.0.0 by others, not by the original
authors
2) the projects are build with the latest version of Wicket and their tests
are executed
3) I use WicketStuff build to validate Wicket's releases themselves
> 3) Hard to search. Yes - google can find everything, but on github
> it's much more reasonable to have separate repository per project.
>
I think it is easier to search at one known place than many unknown ones
> 4) When project jumps to wicketstuff: all dependencies should be
> updated. And sometimes it's not easy: for example if you include
> ProjectA which includes ProjectB and projectB jump to wicketstuff.
>
In this case you can still use ProjectB versionBeforeWicketStuff
> 5) And finally: most of projects are already outdated and not
> supported by authors
>
>From time to time contributors appear with some fixes/improvements.
Very recently a user revived Jamon integration from wicket-1.4.x branch!
>
> For my own purposes I started to collect wicket related projects here:
> https://github.com/PhantomYdn/awesome-wicket
This is great initiative! Thank you!
But what you said for WicketStuff I can say for this list too - many of the
projects are outdated and not supported by their authors.
Most probably they will never be updated to a newer version.
Someone may fork them and update, but then it becomes even harder for other
users to find the best solution for a problem.
>
> Collection of links might be move beneficial for the community rather
> that moving everything under single project (WicketStuff), I think.
>
Maybe you are right, maybe not!
My biggest problem with WicketStuff is that it becomes bigger and bigger
and releasing it takes more and more time.
It was almost 6 hours at some point. Now we disabled the deployment of
-examples modules to Maven Central and it is back to ~1h, so please keep
them coming! :-)
>
> Thanks,
>
> Ilya
>
> ---------------------------------------------
> Orienteer(http://orienteer.org) - Modern Data Warehouse for your business.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>