Given the proliferation of signup-related add-on modules, both inside signup itself, and especially in signup_status, maybe it's time to stop using "Other" on the modules page and define a "Signup" package in the .info files that all signup-related modules can share.

Thoughts?
-Derek

Comments

dww’s picture

dww
we/he/they
commented
Title: Create a "Signup" module package for the admin/build/modules page? » Create a "Signup" module package for the admin/build/modules page
Status: Needs review » Fixed

There was general agreement that this is a good idea, so I committed the change to HEAD and DRUPAL-6--1 of signup (including signup_confirm_email), and HEAD of signup_status (including signup_status_cert, signup_status_mailer, and signup_status_log).

dww’s picture

dww
we/he/they
commented

FYI:
#582010: Use the new "Signup" package in the .info file (Signup Scheduler)
#582012: Use the new "Signup" package in the .info file (Signup Restrict by Role)
#582014: Use the new "Signup" package in the .info file (Signup Integration for Ubercart)

dww’s picture

dww
we/he/they
commented

Whoops, my commit for signup_status left out a few: signup_status_invite, signup_status_notifications, and signup_status_limit (I was working offline and my local copy was a bit stale). Now committed to HEAD.

Status: Fixed » Closed (fixed)

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