Hi,

When I tested my Savannah 'merge' in my test install, I was surprised
to see that some CVS repositories and download areas were not created.

After some head scratching ("where the hell did I introduce a bug!?"),
I saw that disabling an 'active feature' in the group-specific
settings not only stop displaying it in the Savane front-end, but also
prevent its creation in the backend.

As far as I'm concerned, I though disabling an 'active feature' was
only a cosmetic change. Moreover, if I do so after the project
creation, it does not remove/disable the feature on the system. It is
not a way for system administrator to perform per-project
configuration since these settings can be changed by the project
administrator - the system administrator would create a group type
instead.

For example, I disabled the "homepage" in one of my projects because
the homepage was not ready for people to browse it. However, I did
wanted it to exist in the system so I could work on it.

So, I suggest not to take these 'active features' into account when
creating the project facilities on the system. What do you think?

-- 
Sylvain

Reply via email to