When a Sub-Project is tagged by a user who does not have access to the main project, they should not be able to assign a tag that is not on the Project.

Example:
World Pay module is a sub project of E-Commerce, and was tagged as the DRUPAL-4-7. The E-Commerce module has not been tagged with DRUPAL-4-7 which cause a 4.7 archive to be created for the E-Commerce Project.

Users then Complain.

TIA

Comments

dww’s picture

dww
we/he/they
CreditAttribution: dww commented
Priority: Critical » Normal
Status: Active » Closed (won't fix)

subprojects are a huge pain in the ass for everyone involved. it's far better to move them into their own directories, with their own CVS access, own maintainers, own tagging, own releases, etc. trying to handle it all within a bigger directory tree is just more hassle than it's worth.

i'd vote for you opening an infra support ticket about moving all the EC contribs into their own directories (just like we did with OG a while ago), have the maintainers make new project nodes, and live happily ever after.

cheers,
-derek