Looking at the votes I think moving to github has the major support.
Let's discuss how to proceed from here (but in another thread).
Martijn
stalled mostly because Apache and
Google were in talks about a new service called Apache Extras [1].
Fortunately those talks are now over and we can continue our future of
Wicket Stuff hosting discussion.
In my opinion there are two possible hosting solutions for Wicket Stuff:
- the newly
Also, if things move to Github and issues need to be moved, I spent some time
getting too familiar with how that process works. There are no easy to use
tools to move issues, it is inexact at best, but I do have the code that was
used to move the Brix issues and am happy to post to Github if
are now over and we can continue our future of
Wicket Stuff hosting discussion.
In my opinion there are two possible hosting solutions for Wicket Stuff:
- the newly announced Apache Extras
- github's organization feature
For Wicket Stuff we have a couple of things that worked fairly badly
].
Fortunately those talks are now over and we can continue our future of
Wicket Stuff hosting discussion.
In my opinion there are two possible hosting solutions for Wicket Stuff:
- the newly announced Apache Extras
- github's organization feature
For Wicket Stuff we have a couple of things
and we can continue our future of
Wicket Stuff hosting discussion.
In my opinion there are two possible hosting solutions for Wicket Stuff:
- the newly announced Apache Extras
- github's organization feature
For Wicket Stuff we have a couple of things that worked fairly badly
on with Wicket Stuff to newer ground. We have had this
discussion before and the discussion stalled mostly because Apache and
Google were in talks about a new service called Apache Extras [1].
Fortunately those talks are now over and we can continue our future of
Wicket Stuff hosting discussion
+1 for Apache.
Let's keep Wicketstuff as close as possible to wicket.
Stefan
+1 Apache Extras
http://www.apache-extras.org/
https://blogs.apache.org/foundation/entry/the_apache_software_foundation_launches
On Tue, Dec 14, 2010 at 3:22 PM, Stefan Lindner lind...@visionet.de wrote:
+1 for Apache.
Let's keep Wicketstuff as close as possible to wicket.
Stefan
Moving to Github
+1 for github. It makes distributed development so much easier. As for
staying close to Apache... apache.org is only a link away.
Carl-Eric
www.wicketbuch.de
GitHub may be a little better for developers, but I think it's quite
intimidating to users (people who just want to easily download the
binaries and read the documentation).
Google Code (thus, Apache extras) is much more friendly to non-committer-users.
But well, if one is fine with that
because Apache and
Google were in talks about a new service called Apache Extras [1].
Fortunately those talks are now over and we can continue our future of
Wicket Stuff hosting discussion.
In my opinion there are two possible hosting solutions for Wicket Stuff:
- the newly announced Apache
this
discussion before and the discussion stalled mostly because Apache and
Google were in talks about a new service called Apache Extras [1].
Fortunately those talks are now over and we can continue our future of
Wicket Stuff hosting discussion.
In my opinion there are two possible hosting solutions
We moved Brix to Github over the last several weeks. I was somewhat skeptical
at first, but I like it a lot. People that want a patch can just fork the
project, and if the project wants their changes, they are trivial to grab.
The issue management at Github is pretty weak. Usable for
I'm just saying that Google Code's interface is much cleaner and
friendlier, which helps a lot with projects' adoption (you don't get a
.
And it supports Mercurial, which is pretty much the same as git in
terms of cloning and merging changes back.
On Tue, Dec 14, 2010 at 5:17 PM, Martin
imho.
most people download through maven, so the downloading interface is
irrelevant. and even looking at it: googlecode has a downloads tab,
github has a big button on the front page - little difference.
the only other relevant part is the wiki - imho they are pretty much
the same on github and
What is the criteria being used for making this decision?
What is easiest for the developer:
Checkout/checkin/branching/merging/etc
What is easiest for the user:
Getting releases or snapshots/logging bugs/bug status/getting help/etc
If only developers are voting (those who commit
17 matches
Mail list logo
