yes i have the same questions as igor.
What do we move completely to Apache?
Is it so that when we have moved then only jira an confluence are still
there
for just Wicket-Stuff?
Everything else, so the auto building and auto deploying and serving of the
latest examples
are done then on the
On 1/18/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
...Problem is that to be able to do
that, you need to earn karma, and IMO you won't get karma until you
help administer stuff.
Are you aware of the Solaris zones?
See http://www.apache.org/dev/solaris-zones.html - I don't know much
about
can we get a zone if we are just incubating?
-igor
On 1/19/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
On 1/18/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
...Problem is that to be able to do
that, you need to earn karma, and IMO you won't get karma until you
help administer stuff.
Igor Vaynberg wrote:
can we get a zone if we are just incubating?
At this point, I personally would stick with either Sourceforge or Servoy.
The main issue being that zones aren't intended for use for public
websites, more for demos, tests, builds, etc, and you cannot map a
domain to a zone
It has been proposed in several threads, so I'd like to make it more formal:
currently we host wicketframework.org on the sf.net servers. We can
move the content of the site to our own box (provided by
http://servoy.com) and host it there, and redirect traffic from the
sf.net server to the our
we could register wicketstuff.org, host our website there until we are ready
to move it to apache, we can even setup our confluence install there to
export our website to apache so we dont have to go through headaches
just dont think of wicketstuff.org as related directly to
wicket-stuff.sf.net
On 1/18/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
Using Apache hardware seems to be a big deal for a community feel and
for a legal standpoint (iianm), and /should/ make things easier. If we
get migraines from dealing with the apache process, then we should get
more involved in the infra
