Re: WicketStuff status and future; awesome-wicket project
Hi, On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный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-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
[ANNONCE] Wicket jQuery UI 7.2.0 released
Dear Wicket jQuery & Kendo UI users, Wicket jQuery UI 7.2.0 based on Apache Wicket 7.2.0 is now released. *Changelog* https://github.com/sebfz1/wicket-jquery-ui/releases/tag/wicket-jquery-ui-7.2.0 *Maven dependencies* ** com.googlecode.wicket-jquery-ui wicket-jquery-ui 7.2.0 ** com.googlecode.wicket-jquery-ui wicket-kendo-ui 7.2.0 If you have any *question*, feel free to ask in the forum: http://groups.google.com/group/wicket-jquery-ui/ If you notice a problem, please open an issue here: https://github.com/sebfz1/wicket-jquery-ui/issues Enjoy! :) Sebastien
Re: WicketStuff status and future; awesome-wicket project
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: > Hi, > > > On Sun, Jan 31, 2016 at 1:38 AM, Илья Нарыжный 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-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: WicketStuff status and future; awesome-wicket project
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, Илья Нарыжный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-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >