Bug 1124622

Summary: RFE: Expose Alpha state of new editor to users through an "opt-in" approach
Product: [Retired] Zanata Reporter: Isaac Rooskov <irooskov>
Component: Component-UI, UsabilityAssignee: Damian Jansen <djansen>
Status: CLOSED NEXTRELEASE QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.0CC: aeng, dchen, mkim, yshao, zanata-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: 1
Clone Of: Environment:
Last Closed: 2015-02-25 06:31:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Isaac Rooskov 2014-07-29 23:30:32 UTC 
In order to generate community feedback, involvement and buy-in, we should set it up so a user can select to use the new editor in whatever state it currently is. 

The current editor should remain the default, and a user should have to "opt-in" to using the new editor (in some way). It should also be easy to "opt-out", as the new editor may not work correctly or have some of the features a user likes. 

- It should be clear to the user that the new editor is in an Alpha state. 
- We should be clear about the current limitations of the editor so when users provide us feedback it isn't something like: "X is missing", when "X" was never meant to be there yet.  
- It should be easy for a user to report feedback (provide a link to bugzilla or information on the Zanata freenode channel).
Comment 1 Michelle Kim 2015-02-25 06:31:05 UTC 
Implemented in 3.6 release.