Thanks for the response, Rüdiger. I think it doesn't matter at this point, but 
if this is still open or gets re-proposed, I'd change my vote to a "-0" (and 
not higher only because I have concerns about how seriously this feature has 
been tested.)
I'll respond to some of the important issues you bring up re. UX in a 
subsequent message, but want to make it clear that as a general rule, I don't 
believe that useful enhancements should be completely blocked by usability 
issues. I do think, however, that every reasonable attempt should be made to 
address usability issues and that counterproposals that do so should be 
considered. 

Judy


On Feb 24, 2012, at 11:05 AM, Ruediger Rolf wrote:

> Hi Judy,
> 
> yes I looked at you proposals. And I see a dilema here.
> 
> I asked Markus M. if he might have the time to create your second proposal. 
> I'm not sure if this can be done for 1.3 or not. But we have not developed 
> the episode service. There was somehow between others no agreement on this, 
> so that this is not changed yet. Your requested changed is very minor to me 
> and I would not see that the usability will be improved by this change very 
> much.
> 
> But the important question to me is: how will we deal with other upcoming 
> features in Matterhorn? Can useful enhancements be blocked because the 
> usability is not too good? Wouldn't we demotivate developers to contribute 
> their code?
> I would say we need a (style-)guide that gives advice to developers what they 
> have to regard that their code will be accepted. For sure it should be 
> possible, even then, to refuse a new feature as a group if we have good 
> reasons, but it should not be possible for minor reasons that should be 
> covered by the guide.
> 
> In general an UX expert should be involved in the development of the UI for a 
> new feature, but you know best probably that this is not possible because of 
> limited resources.
> 
> Rüdiger
> 
> Am 24.02.2012 18:41, schrieb Judy Stern:
>> Rüdiger,
>> My intention was not to block, but to ensure that a (potentially) very 
>> simple sol'n to the UX issues was considered before we move forward. As I 
>> said, it wouldn't take much to get me to reverse my vote. Did you look at 
>> the design I proposed?
>> 
>> Judy
>> 
>> 
>> On Feb 23, 2012, at 2:00 AM, Ruediger Rolf wrote:
>> 
>>> Hi Judy,
>>> 
>>> okay. Then this is probably stopped, as no one has supported this and you 
>>> block this. I hope you are available on the matterhorn users-list after the 
>>> release to explain to adopters how they can activate the episode management 
>>> in their release.
>>> 
>>> Rüdiger
>>> 
>>> Am 22.02.2012 17:50, schrieb Judy Stern:
>>>> And just to make sure that this #proposal doesn't go thru without further 
>>>> discussion, I want to make it clear that I'm voting -1 for now.
>>>> (This doesn't mean you can't change my mind, i.e. if my design 
>>>> counterproposal is really harder to implement that it looks..but really 
>>>> all I'm asking for is a move from top-level navigation to a subnavigation.)
>>>> 
>>>> Judy
>>>> 
>>>> On Feb 21, 2012, at 9:41 AM, Judy Stern wrote:
>>>> 
>>>>> While I agree that the Episode service is very valuable, from a UX 
>>>>> perspective, I think it is a mistake to have it available by default 
>>>>> exactly as is, for many reasons that I have explained in the earlier 
>>>>> thread [3]. The mockup you point to, Rüdiger, is the more ambitious one 
>>>>> that I understand we can not possibly implement at this time. I did also, 
>>>>> however, propose two simpler approaches, which keep the two UI's (one for 
>>>>> looking at workflow instances, the other for managing media packages) on 
>>>>> separate pages but do not make them seem so completely unrelated and do 
>>>>> not introduce potentially confusing terminology. In particular, Approach 
>>>>> 2  [4] changes very little (I believe, perhaps naively, it would be very 
>>>>> easy to implement), but simply makes both UI's available under the 
>>>>> Recordings tab. I would like to propose this (or something very similar) 
>>>>> as a counterproposal.
>>>>> 
>>>>> Judy
>>>>> 
>>>>> [3] 
>>>>> http://opencast.3480289.n2.nabble.com/Renaming-the-quot-Recordings-quot-tab-proposal-td6783119i20.html#a6803786
>>>>> [4] 
>>>>> http://opencast.jira.com/wiki/display/MH/Keeping+Episodes+UI+Separate+from+Workflow+Instances+UI#KeepingEpisodesUISeparatefromWorkflowInstancesUI-Approach2
>>>>> 
>>>>> 
>>>>> On Feb 21, 2012, at 8:56 AM, Ruediger Rolf wrote:
>>>>>> Hi list,
>>>>>> 
>>>>>> in the developer meeting today the question came up why the Episode UI 
>>>>>> [1] is not activated by default. Several people have not noticed this 
>>>>>> feature yet because of this.
>>>>>> 
>>>>>> There was some discussion on this UI when it was created and there was 
>>>>>> not been a concensus on this UI. So the solution to this was to 
>>>>>> deactivate by default. There were some
>>>>>> 
>>>>>> But the Episode service is one of the main enhancements in 1.3 and 
>>>>>> anyone in the dev meeting today felt sorry that most users cannot use it 
>>>>>> because of the hidden UI.
>>>>>> 
>>>>>> There is already a proposal on how to combine the workflow and the 
>>>>>> episode service in the UI [2], but implementing this is out of focus for 
>>>>>> 1.3 and maybe even for 1.4 as no one has himself commited to this 
>>>>>> feature yet.
>>>>>> 
>>>>>> So the proposal is to active the "episode" UI despite all concerns, with 
>>>>>> no or only minor changes (changing the name of the tab i.e.). We want to 
>>>>>> avoid a long discussion that may delay the release, as we hope that the 
>>>>>> release is only one release blocker away... so let us keep the 
>>>>>> discussion short and give your +1 or -1.
>>>>>> 
>>>>>> Thanks
>>>>>> Rüdiger
>>>>>> 
>>>>>> [1] see here how to activated this: 
>>>>>> http://opencast.jira.com/wiki/display/MH/The+Episode+Service
>>>>>> [2] I hope I found the right mockup: 
>>>>>> http://opencast.jira.com/wiki/display/MH/Combining+Episodes+and+Workflow+Instances
>>>>>> 
>>>>>> -- 
>>>>>> 
>>>>>> ________________________________________________
>>>>>> Rüdiger Rolf, M.A.
>>>>>> Universität Osnabrück - Zentrum virtUOS
>>>>>> Heger-Tor-Wall 12, 49069 Osnabrück
>>>>>> Telefon: (0541) 969-6511 - Fax: (0541) 969-16511
>>>>>> E-Mail: [email protected]
>>>>>> Internet: www.virtuos.uni-osnabrueck.de
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Matterhorn mailing list
>>>>>> [email protected]
>>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>>> 
>>>>>> 
>>>>>> To unsubscribe please email
>>>>>> [email protected]
>>>>>> _______________________________________________
>>>> _______________________________________________
>>>> Matterhorn mailing list
>>>> [email protected]
>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>> 
>>>> 
>>>> To unsubscribe please email
>>>> [email protected]
>>>> _______________________________________________
>>>> 
>>> 
>>> -- 
>>> 
>>> ________________________________________________
>>> Rüdiger Rolf, M.A.
>>> Universität Osnabrück - Zentrum virtUOS
>>> Heger-Tor-Wall 12, 49069 Osnabrück
>>> Telefon: (0541) 969-6511 - Fax: (0541) 969-16511
>>> E-Mail: [email protected]
>>> Internet: www.virtuos.uni-osnabrueck.de
>>> 
>>> _______________________________________________
>>> Matterhorn mailing list
>>> [email protected]
>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>> 
>>> 
>>> To unsubscribe please email
>>> [email protected]
>>> _______________________________________________
>> _______________________________________________
>> Matterhorn mailing list
>> [email protected]
>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>> 
>> 
>> To unsubscribe please email
>> [email protected]
>> _______________________________________________
>> 
> 
> 
> -- 
> 
> ________________________________________________
> Rüdiger Rolf, M.A.
> Universität Osnabrück - Zentrum virtUOS
> Heger-Tor-Wall 12, 49069 Osnabrück
> Telefon: (0541) 969-6511 - Fax: (0541) 969-16511
> E-Mail: [email protected]
> Internet: www.virtuos.uni-osnabrueck.de
> 
> _______________________________________________
> Matterhorn mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> 
> 
> To unsubscribe please email
> [email protected]
> _______________________________________________

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to