Once you register, the link goes away from there for 6 months (could still appear somewhere else deeper of course).

Then we can do away with the interstitial text/button altogether.

How does that sound?

To receive advance notice of security updates, and to help our usage statistics, please register your site
[Register now]

It is actually a lie that the button will disappear when you click it. The code currently looks like this:

print_box_start('generalbox adminwarning');
if(!isset($CFG->registered)) { print_string('pleaseregister', 'admin'); }
else { /* if (isset($CFG->registered) && $CFG->registered < (time() - 3600*24*30*6)) { */ print_string('pleaserefreshregistration', 'admin', userdate($CFG->registered)); }
print_single_button('register.php', $options, get_string('registration'));
print_box_end();

So I suggest the after registration strings:

This site was registered on dd mmm yyyy. You are subscribed to the security advisory email list using xxx@example.com.
[Update registration details]

or:
This site was registered on dd mmm yyyy. You chose not to subscribe to the security advisory email list.
[Update registration details]

If you are working on this code, these might be good config variables to move to config_plugins.

1- privacy/confidentiality (they may not be allowed to report their choice of software)
2- they haven't noticed the registration link/button
3- they don't see the point in doing that

We can't really do anything about #1.

My suggestion was about improving #3 by naming a good reason to register.

I suppose that your plan of moving the block to a top-level link is designed to address #2. I like the 6-month recurrence for the link, but I wonder: will admins actually notice the registration request if it's a tiny link as opposed to a large button in a block?

Personally I like the idea of the register link in admin menu (after 6 months). Perhaps it could be "Register / Update register".

Anyway, the part I'm more critical is the message in the notifications page, that is "bigger" (hence, distracts more) when you've registered that when you haven't.

Perhaps also the "register/update register" differentiation must be in that button in the notifications page.

Apart of all, yup, agree about the need to be some more explanatory in the notifications page, as comented and agreeded by all you.

Ciao

The registration page needs a big revamp for the course-publishing and hub stuff in Moodle 2.0. It'll involve making that page a proper mform, and adding new sections for courses, metadata, etc ... as well as lots of rewording. I'll leave that to another bug.