Closed (fixed)
Project:
Documentation
Component:
Correction/Clarification
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
24 Nov 2010 at 19:35 UTC
Updated:
18 Apr 2013 at 14:48 UTC
Just had the urge to shorten the title on the following page to make it more concise, and realized that not any old fool could do it:
http://drupal.org/update/theme
So to whom do I need to prove my worth in order to make this change? What should I do? Does it involve a test of wits? A series of lightening rounds, each more difficult than the last? A display of magic in front of a small gathering of witnesses? Either way, sign me up. (However, if the qualifier is a magic trick, I must insist that you all stand about 10 feet away, and place a hand over one eye.)
Comments
Comment #1
arianek commentedHi Patrick - Anyone can be on the "Docs Team" http://drupal.org/contribute/documentation/join - but being assigned the "Documentation Admin" role is really something that's only done for active documentation maintainers. There are a small number of pages that are "locked" either because of the content, or because of the input format needed for embedding images and using tables.
So, unless you really work with docs a lot or maintain a module and its docs, the way to get changes on pages like this is simply to file an issue!
What's the suggested title you'd want to replace it with? I'm happy to update it if it seems reasonable.
Comment #2
patcon commentedThanks Arianek :)
It hardly seems worth the trouble, but I was going to say "Converting theme versions" or "Updating theme versions". All the other titles at the top level seemed relatively concise, and I thought it looked messy in the contents block on the right. But perhaps that's OCD on my part :)
Anyhow, whatever you think is best!
Comment #3
arianek commentedHuh, I had to agree it was a little circular or confusing or something. I changed it to "Updating a theme to a new version" (since I still wanted to somehow imply that the update was in relation to Drupal's version, not just the theme's). Does that seem better?
Comment #4
patcon commentedOh man, I feel totally nitpicky in retrospect. Your change is definitely an improvement in that I was just trying to think of a way to bring the character count of the title down :)
Thanks for humouring me!
Comment #5
arianek commentedHaha, I don't mind a little nitpicking, I think it's a sign of a good potential Docs Team member, if nothing else!
Comment #7
brst t commentedBoldly changed this without discussion to from a mix of 'Updating' and 'Converting' themes to a linguistically consistent
'Upgrading'
I argue that themes are 'upgraded' if core is also 'upgraded' http://drupal.org/documentation/upgrade/6/7
I think it'd be great to introduce a taxonomy term with synonyms (update and convert) before D6 stops being supported to tag issues/documentation etc. to help minimize search effort.
The url-aliases could use a rewrite from 'update' to 'upgrade'
http://drupal.org/update/theme
http://drupal.org/update/themes/6/7
http://drupal.org/update/themes/5/6
Comment #8
batigolixDon't use this closed issue for this. Start a new one or find a related issue.Did you see? --> #941896: "Upgrade" vs. "Update" language
Update: I see that the other commenters already changed the subject to a 'update' vs 'upgrade' discussion. Still, let's move this discussion elsewhere
Comment #9
brst t commentedNope. I didn't. This node was referenced in the revision log http://drupal.org/node/13222/revisions :
I searched http://drupal.org/search/site/upgrade%20theme%20d6 and http://drupal.org/search/site/update%20theme%20d6 and that node wasn't listed.
How would I have found it?
My goal was simply to document and reference the change I made in the referenced discussion which I assumed was relevant, given the revision log.
Comment #10
batigolixApologies. Title and issue comments dont match, which confused me.
Google is way better for finding stuff in d.o.
Comment #11
brst t commentedS'alright.
Two topics in this thread make for a continuity challenge.