Not sure if I have the authority to change these feature flags.  We would
need to go through a process to make sure no one outside is using these
flags in their environment.


On Thu, Mar 20, 2014 at 9:43 AM, David Baumgold <notifications@github.com>wrote:

> In cms/envs/acceptance.py:
>
> > @@ -89,6 +89,10 @@ def seed():
> >  # Use the auto_auth workflow for creating users and logging them in
> >  FEATURES['AUTOMATIC_AUTH_FOR_TESTING'] = True
> >
> > +# For consistency in user-experience, keep the value of this setting in sync with
> > +# the one in lms/envs/acceptance.py
> > +FEATURES['ENABLE_DISCUSSION_SERVICE'] = True
>
> Personally, I don't like feature flags that have names like ENABLE_THISor
> DISABLE_THAT. I think it makes far more sense to just use THIS or THAT in
> the FEATURES dict, and if it's set to True then it's enabled, False and
> it's disabled. That being said, we already have several ENABLE_* feature
> flags, so this is just a nitpick.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/edx/edx-platform/pull/2910/files#r10794745>
> .
>



-- 

edX | nasthagiri@edx.org <andya@edx.org>

141 Portland Street, 9th floor

Cambridge, MA 02139
http://www.edx.org <http://www.edxonline.org/>

[image:
http://www.e-learn.nl/media/blogs/e-learn/edX_Logo_Col_RGB_FINAL.jpg?mtime=1336074566]