Posted by cyberswat on March 9, 2009 at 4:48pm
Jump to:
| Project: | Project CVS instructions |
| Version: | 6.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I think this is the module adding the "CVS Instruction" tab to module pages on d.o. now. If it is, what are the chances of getting the tab to show up on http://drupal.org/project/drupal
Freaking awesome job btw.
Comments
#1
The module is specifically designed to work with contributed modules and themes.
The Drupal project is a special case:
* It uses a separate CVS root.
* Access control is by branch instead of for the Drupal project as a whole. (This conflicts with the module's maintainer/non-maintainer detection.)
For these reasons, it's not simple. I could write a special case for the Drupal project, but it would basically be the same as the handbook page explaining how to get an anonymous Drupal checkout.
This isn't a "no." I'm just carefully considering this module's scope.
#2
I think we should do this. From IRC:
[3:54pm] mcrittenden: anybody have the link handy w/ instructions to install D7 via CVS?[3:54pm] dww: the "CVS instructions" tab at http://drupal.org/project/drupal and select "HEAD" as the branch. ;)
[3:55pm] dww: argh!
[3:55pm] dww: there's no such tab for core.
[3:55pm] • dww facepalms
[3:56pm] dww: http://drupal.org/node/396186
[3:56pm] Druplicon: http://drupal.org/node/396186 => Add to Drupal project page => Project CVS instructions, Miscellaneous, normal, active, 1 IRC mention
The ACL being per-branch vs. per-project is a non-issue. We should just write the tab to assume everyone is anonymous. Clearly, the 4 people with commit access to the core repo don't need this tab to remember what they're doing. This tab is needed by the other 99.99999% of the community. ;)
I think the rest (e.g. different CVSROOT, etc) can be fairly easily special-cased...
#3
Personally, I find the inconsistency here an issue. I find the cvs tab extremely handy on contrib project pages and I believe the same convenience should be brought to the drupal project page well. Even if it is a special case as pointed out in #2, I think the benefit far out-weighs the cost.
#4
Subscribe
#475826: CVS Instructions on Project Page
#5
yes, we badly need to do this. People even created a Druplicon factoid "checkout head?" to access this info somewhere. But that's only IRC.
#6
+1
Here is some instruction:
http://drupal.org/node/320
Temporary you could add this link on the Project Page.
But where I can find instruction to download DRUPAL-7 via CVS?
no such tag `DRUPAL-7'!
#7
This came up again today, duplicate: #975144: Drupal core project page should have a CVS instructions local task
http://drupal.org/node/320 is not nearly as useful as the CVS instructions local task: it only includes a subset of the commands CVS instructions provides, and includes a whole bunch of mostly-irrelevant corner-case discussion. Drupal core could really use a contributor cheat sheet.