Alan Burlison wrote:
Mark Martin wrote:
I'm reaching out to the website team as I know some of this might
impact what they're doing. I don't know why I haven't seen any
materials or plans about what they're planning long term, but I
presume as part of this website stabilization effort that is
underway, follow on improvement work is being planned on the site
overall. I do know there's a wiki replacement sometime in our
future. Possibly. Are there dependencies or overlaps on the OpenRTI
and (defects|bugs) tools?
The plans have been discussed at length on the website-discuss alias,
the prototype of the new user management system is at
auth.opensolaris.org, the prototype of the new wiki is at
hub.opensolaris.org.
Thanks for the clarification. Must be farther back in the archives than
since I've subscribed or have searched. I'll take your word on it as
it's not so important for purposes of this effort and I'll not mention
it further.
More information can be found at http://opensolaris.org/os/community/web
Been there, seen it, thanks. But again, that's not so germane to where
I'm trying to delve unless you folks think so.
By the way, 404 for
http://opensolaris.org/os/community/web/restructuring.html
ARC case files make up over 50% of the content on opensolaris.org, and
we have a strong suspicion that they are a significant contributor to
the instability we are seeing. If that proves to be the case, we'll
be addressing that issue with some urgency.
So to me, it seems like the ability to generate content dynamically is
probably the only thing that'll work long term. At a minimum, some sort
of ability to allow users to generate and satisfy queries, and provide
top-level case listings without throwing `ls -R` into the navigation.
Does it need to integrate with the new wiki?
I guess that presupposes that any viewer on the case repository must be
able to interface with the VCS if there is one.
As for addressing the ARC content=instability issue short term, may I
ask what the tentative plan of attack is, or have you not gotten that far?
_______________________________________________
website-discuss mailing list
[email protected]
