http://infrastructure.drupal.org/drupal.org-style-guide/prototype/core.html
- The page title here is "Drupal Core"
- The block of developers is labeled: "Developers for Drupal Core"
- Lots of navigation refers to this as "Drupal Core"
Seems like the title of node/3060 needs to become "Drupal Core"...
Can anyone think of something this would break? We'd still keep the project short name to just "drupal" so that none of the issue or project URLs would break. This is simply used for:
a) the page title on the project node
b) the string used in issue metadata summaries
c) the string you have to aim for when changing the project on an issue (we'll still have autocomplete)
d) page title on various issue views
e) the label used on blocks and sub-pages related to projects
...
(c) is about the only one i could think of that could at all confuse people -- however, even then, "Drupal Core" would probably be more clear than just "Drupal".
I guess the big question is if the word "Core" is too much tech jargon for "insiders". However, the redesign mockups put it right in the site navigation (footer links, navigation tabs on "download & extend", etc), so I'm left to assume that Mark + Leisa thought this wasn't a problem.
Any objections? No real reason to wait for launching the redesign to make this change...
Comments
Comment #1
gábor hojtsyI am not sure "Drupal Core" is intuitive as a project name, I regard it too much of a jargon for insiders.
Comment #2
dwwYeah, I'm not sold either, but Mark + Leisa seemed to think that was the way to go. I'm also worried about having a block when you land on node/3060 that says:
"Developers for Drupal"
which lists 9 people, many of whom haven't developed for Drupal in years, and which excludes the hundreds of people who develop for Drupal core (but don't commit the patches) and the thousands of people who develop for Drupal (just contrib).
Side note: I'd propose we rename that block "Maintainers for [project name]" to solve the part of the problem that not all "developers" have commit access...
Comment #3
gábor hojtsyIn that light, well, it is indeed calling out for some distinguished name for the core project. I'd think Mark and Leisa debated this in detail already, it would be good to tap into their mind (ask them to comment :).
Comment #4
dww"ask them to comment"
that's definitely the idea. ;) just wanted to get a redesign issue going so we can track this. it's now on Drupal.org redesign: Questions for Mark (consolidated).
Comment #5
webchickAh, I definitely like "Maintainers" much better than "Developers." The Drupal (Core) project is particularly bad this way in that the maintainer : developer/other contributor ratio is absolutely ridiculous. 1 : 1000 ?
I missed a lot of the discussion around this, but I can see the renaming being valuable from a disambiguation standpoint. Drupal is software, a community, a website, a trademark, an association, a movement, a conference, an IRC channel, a noun, an adjective, probably a verb somewhere :P, etc. "Drupal Core" (once you figure out what the heck "Drupal Core" is) makes it easier for everyone to get on the same page about what it is you're talking about. And it's a term "insiders" use an awful lot that "outsiders" remain clueless of until reading other people saying it enough times that it finally clicks.
I think it would also help the issue queue get fewer off-the-wall support requests from people who think their problem is with "Drupal" since it's a problem with some weird-ass module they downloaded with it. That's probably just wishful thinking though. ;)
Still, it'd be wonderful to have Mark/Leisa chime in about their thinking behind the wording change.
Comment #6
webchickOf course, even better would be something like "Contributors to Drupal Core" Blah blah blah "And 238,792 others
Is there a feature request for some/page/with/status/for/project/contributors that I can subscribe to? ;)
Comment #7
leisareichelt commentedrighto. on the question of 'core', all the research we did indicated that people did understand what 'core' referred to, so rather than try to come up with alternative we have left it. If there's any concern we should just do a little further testing to confirm the best approach.
re: drupal developers vs maintainers. I'm happy to go with whatever you think is best here. The rationale behind this list is to expose members of the Drupal community to newbies, and to show the activity/contributions that are being made. I agree that it makes sense to link to 'active' contributors rather than people who aren't around anymore so perhaps maintainers is the right approach... another option would be to show 'latest' contributors?
at any rate, as long as we're getting a few community names and links to profiles up here, I'd be happy :)
hope that helps, let me know if there's anything more/questions etc.
Comment #8
dwwYes, the current proposal for the block is the top N maintainers ordered by their latest commit, and a link to a page with a table of everyone who's ever committed to the project. N will just be a knob when you configure that block, we'll probably default to 5 or something, but that'll be trivial to change as we see fit. (See #371969: Move developer info into a block provided by cvs.module for more about this block.)
Re: "Core" -- that all sounds good to me. Thanks for clarifying. I'm going to leave this issue open for a little while to give other folks a chance to weigh in before I just make the change, but I think this all makes sense and it's certainly entrenched in the redesign mockups already...
Cheers,
-Derek
Comment #9
gábor hojtsyReading up on Leisa, I agree that "Drupal core" should be fine then.
Re: webchick (#6), I've created an issue for automated tracking of people based on their contributions to releases with prior practice linked at #433050: Add code to parse and aggregate CVS contributor info. Subscribe(TM) to that.
Comment #10
lisarex commentedMoving to the Redesign project. Check to see who has been assigned to implement this section and the staging server it'll live on during implementation here: http://groups.drupal.org/node/37064
Comment #11
drummmaintainer block says maintainers and the original title rename is #688202: Download and Extend Core page content needs to be updated from prototype
Comment #12
dwwIt's not clear why this was merged with a later issue. I just changed the title on node/3060.