As custodians of the Drupal.org project namespace, I would like to get some feedback from the webmasters regarding this issue #3042550: Code standards issue: The decrypt function.

Will be acceptable to "grab" the currently unused namespace for a dummy "Decrypt" project? ("Solution 1" in the related issue.)

The project would be sandbox only implementing hook_help() explaining why it exists.

The motivation for doing so is:

  1. Not breaking or disrupting the existing API. (I.e. not impose the burden of an API-change on current users.)
  2. Avoid future namespace conflicts by making the infringed namespace unavailable to other projects.

Or is "grabbing" a project namespace with no intention of creating a "real" project outside community norms?

Comments

gisle created an issue. See original summary.

avpaderno’s picture

If the purpose is avoiding a user creates a module where a function has a name that is equal to the project machine name, that would eventually be a problem for every project using a verb as machine name, not just for a Decrypt project somebody could create.

Given the problem is not with the namespace, but the content of a module, and given the "issue" would involve many project names, we cannot take any proactive action, nor take it for a very specific case that is a single case out of many possible cases.

avpaderno’s picture

I spoke of projects that use a verb as machine name, but that could also be true for projects using a noun as machine name, or a combination of verb and noun, like spam, cookies, send_email, encrypt_file.

avpaderno’s picture

Component: Project/Git problem » Other
avpaderno’s picture

Status: Active » Fixed
avpaderno’s picture

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.