Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | don't have commit access to www as Content Developer | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Unknown <non-migrated> |
Component: | _openoffice.org CVS (obsolete) | Assignee: | Unknown <non-migrated> |
Status: | CLOSED FIXED | QA Contact: | issues@www <issues> |
Severity: | Trivial | ||
Priority: | P2 | CC: | issues, lsuarezpotts, nesshof |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Unknown
2001-12-20 11:44:39 UTC
I gave Armin the Role "Developer" instead of only "Content Developer". Seems that the definition that a "Content Developer" may commit to the www area doesn't work for the www project (www/www) P1 -> P2 thanks, stefan. Hmm. I thought I had already given him the role of developer... odd. sorry for the mixup. -louis Is this resolved? Resolved? Yes and No. Yes: Armin's problem is solved. No: Shouldn't "Content Developer" be sufficient? Do we care about this inconsistency compared with other projects (P2->P3)? This has been entered for investigation as pcn7109. The Content Developer Role should be sufficient for making these types of changes in any project including www. Thank you Kat Changing summary. Reassigning all of kat's open issues to support so that I can go through them. This is assigned to our instantiations engineer, but I need to follow up with him, as he's currently occupied with the NetBeans upgrade. *** Issue 2854 has been marked as a duplicate of this issue. *** are there any updates on this issue ? Still working on getting this to pop up in his queue. I raised the status of this to p2. It's important; Ooo has many would-be content developers. louis This is still in the same queue with the netbeans solaris migration. Cecilia is talking to Eric about prioritization here. adding louis to cc list We've gotten help from our permissions specialist, and replicated the issue. Upon analyzing the situation, he estimates that the problem is localized in our cvs tools (not in our permissioning tools). We will be working with the cvs specialists also to localize this problem further. Okay, so we've got a fix. Apparently by default in this revision the "All web pages" resource had a typo (leading slash). I created a new "All Web Pages Workaround" resource and changed all Content Developer permissions which referred to "All web pages" to the workaround resource. I've tested, and it's working now. Please verify! As agreed by Louis I will close these resolved fixed support-owned issues now. If you have trouble with that, please re-open the issue. As agreed by Louis I will close these resolved fixed support-owned issues now. If you have trouble with that, please re-open the issue. |