Add 'markup' component to Drupal project.
webchick - June 18, 2009 - 16:21
| Project: | Drupal.org webmasters |
| Component: | Textual improvements |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Based on discussion at #491454: Provide a way to add a new default component to existing projects (which was originally in this queue), there seemed to be good consensus for adding this for designers.
Since the upgrade path over there wouldn't affect the Drupal project - since it has a heavily customized component list already - I went ahead and added it there.
Let me know if there are any problems with this, but I think it's a good improvement.
#1
I'm ok with it, though core is a bit of a special case. There are so many different parts of core (distinct modules) that the component list there is a) huge and b) silo'ed. As with my opposition to a "tests" component, "markup" could be a class of bugs in any of the other components. I follow update.module issues closely, but I'm not going to see "markup" issues about update.modlue.
IMHO, in core we should use component for "where" and tags for "what".
That said, other than making a huge dropdown a little more huge, I'm not really opposed, and if we think this will make designers feel more welcome, great. I'm just worried that maintainers like me are going to miss relevant issues.
/me shrugs
#2
Yeah, unfortunately removing the "tests" component has really stymied the test writing community we were attempting to build. Tags are only applied very sporadically by those "in the know" that a tag exists, and only sought after by those who have stumbled across a tag in reading other issues. It's very difficult anymore to point someone who knows SimpleTest really well at a place they can be most effective.
I'd like to NOT see this happen with the design community we're building as well.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.