Closed Bug 637813 Opened 14 years ago Closed 14 years ago

access request to create and edit public web pages in the NSS security area

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
x86
Linux
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jdennis, Assigned: jlaz)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20110103 Fedora/3.6.13-1.fc14 Firefox/3.6.13 Build Identifier: I maintain a project related to NSS (python-nss) and would like to be able to create and edit web content for the project. I would also like to be able to edit NSS content. From the mozilla.dev.tech.crypto mailing list: On 25/02/11 23:55, John Dennis wrote: > > Yes, that's a deficiency. The lack of a project page is part due the > > fact I'm the only person supporting the project and the difficulty of > > getting the right Mozilla mojo to maintain public pages. So I do > > apologize for that, it really should be done. File an access request bug and CC me. Gerv Reproducible: Always
What sort of vouching is needed to give access to the mozilla.org webtree. David? Gerv
FWIW, I already have CVS write access and an account on stage.mozilla.org for pushing releases out on the FTP server.
There are two things to discuss here. * Getting access is just a matter of getting vouched by the owners of the content you're interested in. In this case it looks like someone from this list: https://wiki.mozilla.org/Modules/All#security * Where should this content live? In addition to having NSS pages on mozilla.org there are also NSS pages on MDN and the wiki. https://wiki.mozilla.org/NSS https://developer.mozilla.org/en/NSS We should figure out where it makes the most sense for this content to live and then migrate over the other content and set up redirects so people don't come across old content. Both MDN and the wiki are much easier to update than mozilla.org, fwiw.
Bob Relyea and Wan-Teh Chang have vouched for me in the past.
OK, if someone on the security team vouches in this bug we can work out the access part. Any thoughts on the question about where NSS content should live?
Bob and Wan-Teh, I have added you to the cc list for this administration request to be granted access to maintain python-nss project web pages and I was hoping one or both of you would vouch for me. From time to time while working on the binding I've found omissions, errors or clarifications needed in the existing API doc, if you see fit I'd like permission to make edits there to enhance the doc, but I would understand if you preferred team review of any changes in the core doc (or possibly the master lives in source code control somewhere and the web content is just a shadow copy). You might also want to chime in on the NSS content question. I know improving the doc has been a long term goal. However, in any event I do need to create and maintain python-nss content.
Bob and Wan-Teh, please see the question in comment #3 about where this content should live. Editing documents on the wiki or MDN is much easier and therefore the pages are likely to stay more up to date. Plus we have been slowly migrating technical documents off of mozilla.org and I think MDN may be a better fit (although I don't know exactly what the plans are for the NSS pages).
Assignee: desktop-support → server-ops
Component: Server Operations: Account Requests → Server Operations
I vouch for John Dennis. The area John needs access to is http://www.mozilla.org/projects/security/pki/. John: you should put python-nss docs on https://developer.mozilla.org. Use https://wiki.mozilla.org for project planning only. Treat http://www.mozilla.org/projects/security/pki/ as in maintenance mode.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OK, can someone in server ops give John access to the projects/security/pki/ directory in the mozilla.org SVN repository? Note, if there is interest in migrating the data from mozilla.org to MDN I'm happy to help with that.
Added to authz [/projects/security/pki] jdennis@redhat.com = rw
Assignee: server-ops → jlazaro
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
No, this should be /projects/mozilla.org/trunk/security/pki
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Changed to reflect comment #11
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Do we usually give people access to subsets of the mozilla.org webtree? I thought normal practice was just to give people access to the whole thing. Gerv
Reed would know more about this than I do, but I believe we've limited access inside the repository in other cases.
I'm getting "access denied" errors when I try to do a commit. Who can I work with to get this resolved?
Shot you an email, we can discuss over email or IRC
All set, now correctly pointing to the right repo in authz [/projects/mozilla.org/trunk/projects/security/pki] jdennis@redhat.com = rw
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.