[development] Best practices: Config settings

[Gerhard Killesreiter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

my question is: Where should contrib module authors put config options
for their modules?

1) Should this always be the individual module's settings page?

2) Should it try to add the config option to a more generic place
(either provided by core or another module it depends on)?

3) Should it add it to both places?

Concrete example:

I've added a performance related variable to event module. The value of
the variable decides whether to do a full node load for each event on a
calendar or to only use title, start, and end date from one mysql query.

Now I need to put the UI for this variable somewhere...

The variable also has influence on the theme you use since you can't
print out any other node content fields if they aren't there. The event
functions that event.module ships with for example expect the presence
of a teaser field.

In principle, I think that the variable should be set at
admin/settings/performance but who is going to look there again after
each newly installed module?

Cheers,
	Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHetFwfg6TFvELooQRAtEXAJ9sU3W05FUyTydSeI85m5XeQRL0RQCeO78A
pXSmapndM+S87aiVN3gYed0=
=Ood9
-----END PGP SIGNATURE-----