Suggestion: 1) Move the caselog tree elsewhere and hide/disable it. Heck, it is a r/o mirror, you could simply just delete it. This will immediately relieve the pressure on the site without having to disable the whole ARC community.
2) Disable the sac/os.o mirror cron job so it doesn't get put back. 3) re-enable the arc community's site to give access to the basic docs. As an ARC Community leader, I resent this unilateral action taken to shut down our community without any interaction or discussion /WITH/ our community. > *Any* nav-bar would struggle with 11,000+ items. ?It was made clear at the > time that the ARC data was first put onto OSO that it was an inappropriate > place for it to go. ?That was ignored, and has eventually brought the site > to its knees. ?As has been explained, this is a short-term workaround until > we can provide a resolution. Wonderful thing, that passive voice. Makes it sound like it is all my fault. The website team was told we needed a place to put the arc stuff. The existing solution was suggested by them, even though it was imperfect, because no alternatives (other than go build your own site yourself) were available, and a replacement site was coming online within a few months. That was several years ago, and in those years, the request to disable/bypass the navbar for the arc community was ignored. > And providing a mechanism to replace the current broken one on sac.eng isn't > in *our* job description. ?We would be justified in turning off the ARC > pages and telling the ARC community to sort out their own mess. ... without first bring this issue up to the community and the OGB for dispute resolution? > That's disingenuous to say the least. ?You were included in the internal > conversation we had about this. Oh, this isn't a COMMUNITY thing, it is an internal-to-Sun thing. Sorry, I thought this was an open source community... -John
