Honestly, either way this goes, I think that any changes on this should wait until Pete returns from vacation. This is a major change for the project and one that the project lead needs to be part of. I'm not aware of all the conversations related to this, so won't comment on the choices.
Pete will be back the first week in April, and since I don't think there is any critical need to make the move I have a suggestion.
If you need new wiki pages, create them in the sfwk.org
wiki. If you want keep them separate from other wiki pages ( tags, naming, links, whatever ) and self contained. This way no one will be stopped from doing what they need to do, and either way the choice goes you will already have a head start.
The Seam 3 information does need updating, as I can attest with reviewing the current builds and pages, but lets start with this approach, and then work this out as a team when Pete returns.
On Thu, Mar 18, 2010 at 4:48 PM, Gavin King <email@example.com>
Folks, I've listened to all the arguments. I really have. I'm not
going to re-argue the case here, since we would just be beating a dead
horse. And I've taken all these arguments into account in making the
decision that no, we are not going to use the jboss.org infrastructure
instead of the purpose-built software that we created for our own
How does the wiki software affect your ability to "engage the
On Thu, Mar 18, 2010 at 4:33 PM, Lincoln Baxter, III
> I can personally submit my frustration as a new module lead -
is not enough to meet my needs in:
> Engaging the community - promoting the project.
community"? Actually, hibernate.org and seamframework.org have a much,
much better and deeper track record of community building and
community engagement than jboss.org.
Geez. Use the Atom feed like I do. It's much more convenient. Or spend
> Staying aware of what the community is doing, asking for, struggling with,
> talking about. I'm cut out completely on seamframework.org
. I can't get
> email notifications,
5 mins writing a little bit of code to extend the existing email
notification stuff in seam wiki. This is going to be way less work
than migrating content to a new infrastructure.
Huh?! I post links to comments and threads all the time. It's totally trivial.
> I can't paste links to replies, other threads on the
> site itself, or URLs with query=parameters (without using the plain text
> mode which is just terrible.)
This is not an issue of what software platform we run on. We can
> Providing logically organized, clear, and navigable information. How can I
> establish the expectations and guidelines for development on these modules
> when I can't put that on a site that isn't confused with Seam 2 already?
install as many instances of Seam Wiki as we like. And I don't see why
we can't put legacy Seam2-related content in a different area of the
same site. That's just silly.
Funny, I have not seen it down any time in the past 2 years.
> These are just a few of the issues I've encountered - aside from the fact
> that the site is frequently down and is always semi-responsive (5-15s per
> request). It's struggling to keep up with our needs.
Responsiveness is perfectly fine for me, and can easily be improved by
moving it to a new box in the USA.