Anyways, there is a few changes we can do to help without major changes to the site.

http://drupal.org/cvs-application/requirements

Should be limited to the topic. I cant edit it, so I proposal the following quick edits...

The main features of that motivation message that assist the administrator are details of your proposed contributions. For example:-

Module contributions: If you wish to contribute a new module to Drupal.org and the wider community please provide as much detail as possible regarding your modules functionalty and what new features the module will offer end users.

Additionally, please provide a link to where your module can be downloaded in case a review is required. Not providing a link may well result in an automatic denial of your request for a CVS account.

It's important to note that CVS applications are often denied when an tendered module duplicates the features and functions of an existing module and in these cases applicants are referred to the module's maintainer to offer collaboration on improving that existing module.

Theme contributions: If you wish to contribute a theme please ensure your motivation message includes links to either (or both) screenshots of your intended theme contribution or a working demonstration site that uses your theme. 

Translations: If you wish to contribute translations then please first use the project issues queues to submit a couple of translations before applying for a CVS account. In that way your first contributions can be reviewed. After that a CVS account will be granted and translators will be able to commit directly to project translation folders. 

api.drupal.org Documentation contributions: If you wish to contribute additional documentation that gets integrated with http://api.drupal.org/ please ensure your motivation message includes links to issues in the documentation issue queue where you have created a patch for your proposed change. The docuementation behind api.drupal.org is stored in the contributions/docus folder of cvs.drupal.org and, if you are unsure how to do it there is lots of documentation on how to create a patch

Should simply be removed. Why? Because if you made it this far into the documentation, You should already know what you are contributing. Plus there are separate sections that deal with this information. Allot of the information could be added to the base document http://drupal.org/node/7765

Also docuementation is spealed wrong and "api.drupal.org Documentation contributions: " should simply be Documentation contributions... api.drupal.org is in the body of the document.

Mike

Comments

MGParisi’s picture

MGParisi commented

I just want to propose that this document be cut down, and limited to how to apply for cvs access... keep it closer to scope, or else people will simply scroll down and click the link. Also the big WARNING was useless (and probably still is) because I have found a number of documents that point to the cvs application directly. I have corrected this issue, but who ever wrote this should be aware that there are probably more links that bypass this documentation.

add1sun’s picture

add1sun commented
Project: Documentation » Drupal.org site moderators
Version: 6.x-1.x-dev »
Component: Correction/Clarification » Textual improvements

Since I consider this the realm of the CVS admins, I'm going to move this to the webmasters queue to get more feedback.

dww’s picture

dww
we/he/they
commented

Although I created that page to fix #126206: Can't print: node redirect aborts book export, I don't really care about it much. This is more in the realm of the folks who deal with approving CVS applications (mostly AjK), not the "CVS admins" (me and killes) per se. I don't know why it's locked for editing with Full HTML (when I created it, it was just filtered HTML). I'm completely happy to delegate any and all authority about the content and structure of this page to the doc team. Whatever y'all think is best on this -- knock yourselves out, and don't wait for me about it. ;)

That said, AjK is really the one you should try to hear from about this page -- he's the one who does the bulk of the work processing the resulting applications, and he did the vast majority of the revisions on that node. He's clearly got his reasons for doing so, and he should probably speak up before you radically change the page.

Thanks,
-Derek

add1sun’s picture

add1sun commented

Ah righto, I sort of assumed AjK was a CVS admin, and he was the main target of my moving this.

MGParisi’s picture

MGParisi commented

Since this is now moved from Documents -> Webmasters, there is allot of things that should be mentioned that are not apart of this post, that us documentation team are talking about.

I want to redo most of the parent items to this document. Allot of the parent documentation overlaps with the CVS section and other area's of the website. I would like to reduce the duplication of this information, with links to related information, and create a better navigation for users to get the information they need.

For example, the parent sections deal with themes, translations, documentaition, and many other topics. I propose that this is mixed up among the documents and should be put into a new site map so that people can find things easier.

For instance, many documents contain information on multiple areas of contributions. If I am writing a module, I do not want to read things about making themes!

I think what was left out of this original post was this re-organization, which will I believe will help with better applications for CVS access. I believe a well thought out site map, with well thought out document scopes will allow us to create better documents. I Know that most of this information is already written, and that what is really needed is Cut and Paste from the documents that exist into more target driven documents.

Some of this was covered in a mailing list post.

I wanted to make these document team discussions known to the target of this post, as to put it into scope with additional changes I would like to make.

However, there is sometime before we can move on all of this, since there is a IA person coming in to help sort this all out. I am more then willing to help out with this project, as I myself is a IA person. (I am not a project Manager However)

dww’s picture

dww
we/he/they
commented

Cool, thanks for the additional info. Sounds good.

MGParisi’s picture

MGParisi commented

check out http://drupal.org/node/446744

I have started to create a sitemap for this specific section. I have been hammering away at fixing what I can, and reading all the associated documentation. I think this will help... though If it doesn't change because of input from the community then I will be discouraged. At least it will give the IA person a starting point.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Did anybody asked to AjK about the page?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Closed (won't fix)

I am marking this task as won't fix.
The assumption if you made it this far into the documentation, You should already know what you are contributing is not true; then, the purpose of that paragraph is to make clear what it is allowed, and how.