WicketStuff at GitHub
5 views
Skip to first unread message
Bruno Borges
Jun 28, 2011, 10:30:38 PM6/28/11
to visural...@googlegroups.com
Guys, what do you think about bringing Visural to the WicketStuff repository? We are working to make it stable together with Wicket 1.5 and release all (or at least most part) of its projects at the same time as Wicket core.
Would be great to put together all Wicket components available on the net into one single place.
Josh Chappelle
Jun 29, 2011, 10:51:22 AM6/29/11
to visural...@googlegroups.com
I think it's a great project. We use many of the components. Moving it would make it easier for others to find so I think it is a good idea.
Josh
Bruno Borges
Jun 29, 2011, 12:06:40 PM6/29/11
to visural...@googlegroups.com
Let's work on it. Do you mind if I fork the code into a folder inside wicketstuff?
Richard Nichols
Jun 29, 2011, 7:33:24 PM6/29/11
to visural-wicket
Hi Bruno,
I'm the project owner on visural-wicket.
I'm open to the idea of a project merge, but there are a couple of
things about visural-wicket which I feel are done well and has lead to
good adoption rates, and my (perhaps incorrect) impression is they may
not be done as well by wicket-stuff -
- examples are available, user friendly, well documented and
accessible
- ant & maven friendly, JARs and docs are easily accessible
- user onboarding process is good
- decoupled release cycle from Wicket (note there is a 1.5 branch, and
for major Wicket releases, there needs to be synchronisation, but I
don't see it to be an advantage to couple the releases together beyond
major Wicket releases)
My experiences with Wicket-stuff have been frustrating in the past, as
documentation is often lacking, the examples don't always work (or
don't adequately demonstrate all features) and the path of least
resistance assumes we're all using Maven.
Perhaps some points can be addressed with some time and effort... and
some of the things I've done with visural-wicket can be fed into the
wicket-stuff project's various pieces.
On a personal note though, right now I'm very time-poor as our first
baby was born just a week ago.
I'd ask that you don't fork the project until we can discuss it a bit
more. I don't think having a bit of diversity (i.e. more than one
component library) for Wicket is a bad thing, and I don't want to
backtrack on some of things that have been done well with the project
(based on comments I've had from users).
Do you feel the above is a fair assessment and/or are these things we
can work on?
cheers,
Richard.
On Jun 30, 2:06 am, Bruno Borges <bruno.bor...@gmail.com> wrote:
> Let's work on it. Do you mind if I fork the code into a folder inside
> wicketstuff?
>
> *Bruno Borges*www.brunoborges.com.br
> +55 21 76727099
I'm the project owner on visural-wicket.
I'm open to the idea of a project merge, but there are a couple of
things about visural-wicket which I feel are done well and has lead to
good adoption rates, and my (perhaps incorrect) impression is they may
not be done as well by wicket-stuff -
- examples are available, user friendly, well documented and
accessible
- ant & maven friendly, JARs and docs are easily accessible
- user onboarding process is good
- decoupled release cycle from Wicket (note there is a 1.5 branch, and
for major Wicket releases, there needs to be synchronisation, but I
don't see it to be an advantage to couple the releases together beyond
major Wicket releases)
My experiences with Wicket-stuff have been frustrating in the past, as
documentation is often lacking, the examples don't always work (or
don't adequately demonstrate all features) and the path of least
resistance assumes we're all using Maven.
Perhaps some points can be addressed with some time and effort... and
some of the things I've done with visural-wicket can be fed into the
wicket-stuff project's various pieces.
On a personal note though, right now I'm very time-poor as our first
baby was born just a week ago.
I'd ask that you don't fork the project until we can discuss it a bit
more. I don't think having a bit of diversity (i.e. more than one
component library) for Wicket is a bad thing, and I don't want to
backtrack on some of things that have been done well with the project
(based on comments I've had from users).
Do you feel the above is a fair assessment and/or are these things we
can work on?
cheers,
Richard.
On Jun 30, 2:06 am, Bruno Borges <bruno.bor...@gmail.com> wrote:
> Let's work on it. Do you mind if I fork the code into a folder inside
> wicketstuff?
>
> +55 21 76727099
>
> On Wed, Jun 29, 2011 at 11:51 AM, Josh Chappelle <jchappelle...@gmail.com>wrote:
>
>
>
>
>
>
>
> > I think it's a great project. We use many of the components. Moving it
> > would make it easier for others to find so I think it is a good idea.
>
> > Josh
>
> On Wed, Jun 29, 2011 at 11:51 AM, Josh Chappelle <jchappelle...@gmail.com>wrote:
>
>
>
>
>
>
>
> > I think it's a great project. We use many of the components. Moving it
> > would make it easier for others to find so I think it is a good idea.
>
> > Josh
>
Martin Paulo
Jun 29, 2011, 7:51:38 PM6/29/11
to visural...@googlegroups.com
I'd like to back Richard on this: wicket stuff can be (and often is) a
right royal pain to navigate and and use, whereas visural-wicket has
always been great. It would be sad to loose that.
right royal pain to navigate and and use, whereas visural-wicket has
always been great. It would be sad to loose that.
If the goal is to make the library better known then perhaps wicket
stuff could rather add a catalog of known wicket libraries and
components with references to them/reviews etc... (and perhaps act as
an archive if they ever go off line or become orphaned)
If the goal is to centralize all wicket related things, then perhaps
first the infrastructural issues identified by Richard should be
worked on first?
Either way, I thank Richard for making the visural wicket libraries
available: and congratulate him and his family on the birth of their
child!
Martin
--
==================================================================
Martin Paulo, BSc.
Software Developer
Tel : +61-3-9434 2508 (Home)
Tel : 04 205 20339 (Mobile)
Site: http://www.thepaulofamily.net
"Nobody goes there any more. It's too crowded" - Yogi Berra.
Bruno Borges
Jul 3, 2011, 11:40:32 PM7/3/11
to visural...@googlegroups.com
Richard/Martin, I understend your concern. But my goal here is first to have visural in a place where contributions are naturally boosted, thanks to Github. Maybe if you guys moved from Google Code to there, visural could find more attraction. We can talk about merging with Wicketstuff later.
WS has a strick process to make sure components are not simply added and then abandoned. Projects that are on this situation, don't participate in the release. They are commented from the main pom.xml to avoid problems. It is hard to keep the project up to date, but we are working on this. Merging Visural with Wicketstuff is not a matter of just moving code together. It is rather a unification of two great teams. That's what I'm looking for.
What do you guys think?
Richard Nichols
Jul 4, 2011, 12:08:01 AM7/4/11
to visural-wicket
Hi Bruno
I had recently moved the source control of all visural projects from
Google Code to GitHub (as in, in the last month or two). The Source
tabs at google code redirect to github & I'll be working on giving the
github repo more visibility for the next release.
I agree that Github is a much better platform for facilitating
collaboration, and I'll be accepting useful patches there from anyone
that wants to contribute. The project pages / issue tracker will
remain at google code for now (I think the uniformity, tracking and
clear licensing terms etc. that Google Code's project hub offer is a
good thing).
In terms of merging projects, I'd propose let's revisit the discussion
in a few months. As I said in the last message, I'm very short on time
right now, so what little I have I'd like to spend on getting the next
patch release and Wicket 1.5 branch released.
cheers,
Richard
On Jul 4, 1:40 pm, Bruno Borges <bruno.bor...@gmail.com> wrote:
> Richard/Martin, I understend your concern. But my goal here is first to have
> visural in a place where contributions are naturally boosted, thanks to
> Github. Maybe if you guys moved from Google Code to there, visural could
> find more attraction. We can talk about merging with Wicketstuff later.
>
> WS has a strick process to make sure components are not simply added and
> then abandoned. Projects that are on this situation, don't participate in
> the release. They are commented from the main pom.xml to avoid problems. It
> is hard to keep the project up to date, but we are working on this. Merging
> Visural with Wicketstuff is not a matter of just moving code together. It is
> rather a unification of two great teams. That's what I'm looking for.
>
> What do you guys think?
>
I had recently moved the source control of all visural projects from
Google Code to GitHub (as in, in the last month or two). The Source
tabs at google code redirect to github & I'll be working on giving the
github repo more visibility for the next release.
I agree that Github is a much better platform for facilitating
collaboration, and I'll be accepting useful patches there from anyone
that wants to contribute. The project pages / issue tracker will
remain at google code for now (I think the uniformity, tracking and
clear licensing terms etc. that Google Code's project hub offer is a
good thing).
In terms of merging projects, I'd propose let's revisit the discussion
in a few months. As I said in the last message, I'm very short on time
right now, so what little I have I'd like to spend on getting the next
patch release and Wicket 1.5 branch released.
cheers,
Richard
On Jul 4, 1:40 pm, Bruno Borges <bruno.bor...@gmail.com> wrote:
> Richard/Martin, I understend your concern. But my goal here is first to have
> visural in a place where contributions are naturally boosted, thanks to
> Github. Maybe if you guys moved from Google Code to there, visural could
> find more attraction. We can talk about merging with Wicketstuff later.
>
> WS has a strick process to make sure components are not simply added and
> then abandoned. Projects that are on this situation, don't participate in
> the release. They are commented from the main pom.xml to avoid problems. It
> is hard to keep the project up to date, but we are working on this. Merging
> Visural with Wicketstuff is not a matter of just moving code together. It is
> rather a unification of two great teams. That's what I'm looking for.
>
> What do you guys think?
>
Bruno Borges
Jul 4, 2011, 12:11:57 AM7/4/11
to visural...@googlegroups.com
Yes, of course, let's give some time.
Congratulations man, it's wonderful to be a father.
Have a great week,
Reply all
Reply to author
Forward
0 new messages