"Projects" terminology confusing for Drupal users/devs?
| Project: | Drupal Automated Staging Toolkit |
| Version: | 5.x-2.0 |
| Component: | User interface |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Again, I love his effort (and would have paid more attention during the development, but I was already mentioning 3 other SoC projects). However, I'm wondering if the "projects" terminology might be a little confusing for Drupal users and developers. :( We all think of and talk about projects as the kinds of things that modules, themes, install profiles, etc, all are. E.g. your "project page", your "project issue queue", etc. There's already enough confusion in the works with "profiles" vs. "install profiles", etc. Now we're going to have "projects" and "DAST projects". Maybe "project" really makes the most sense for this, and it's probably too late to rename, but I just wanted to mention it in case someone has a better idea. Feel free to "won't fix" this issue if "project" is really the best word for this.

#1
Hmm, didn't think about it like that. The "build project" tag is just arbitrary - something I just came up with to describe a container for build scripts and properties files. I don't think it should be confusing for users as long as it's used in the right context, but I'll keep this open if anybody has a better naming suggestion.