Okey-doke.
I think it's unfortunate that we won't have a way to filter user stories to 
find all those that have *some* solution, but I understand your point. Maybe 
tag them "3rd party solution available"?
Galicaster folks, will you go ahead and add comments to the stories that so 
that potential adopters who are looking at open stories will know that there 
exists a solution that works with Matterhorn? (Same goes for any other 3rd 
party vendors who know they've met needs indicated by Matterhorn user stories.)

thanks,
Judy

On Apr 30, 2012, at 11:44 AM, Greg Logan wrote:

> On 12-04-30 11:18 AM, Judy Stern wrote:
>> That makes sense, Greg. 
>> I'd still like a way to indicate that there does exist a solution to the 
>> need indicated by the story.
>> Does it make any sense to resolve such stories as "On Hold", since the 
>> likelihood of them ever being prioritized goes down even further when 3rd 
>> party solutions appear?
> 
> We do need some way to indicate that *someone* has a solution to the
> issue, but I'm not sure that changing the resolution would be the right
> approach.  Once it's on hold developers might look at it and say 'well
> it's already on hold, so someone else must be working on it for mainline
> trunk' and then nothing will ever get done.  I think the Gallicaster
> folks should comment on the ticket to make it clear that their product
> has implemented the story, and leave it at that.  I suppose we could add
> another JIRA field, say a 'The following projects have implemented this
> story', but then we have the overhead of keeping the options updated.
> 
> G
> 
>> Judy
>> 
>> 
>> On Apr 30, 2012, at 10:08 AM, Greg Logan wrote:
>> 
>>> On 12-04-30 11:01 AM, Judy Stern wrote:
>>>> Vicente (and others):
>>>> I'm wondering if we might be able to "close" some of the (overlapping) 
>>>> Matterhorn user stories:
>>>>    • MH-6176 As an instructor, I need feedback when my lecture is being 
>>>> recorded and I need to have some control over recording
>>>>    • MH-1206 As an instructor, I want to start/stop lecture recording (for 
>>>> a dedicated appliance), so that I can control the capture of my lecture.
>>>>    • MH-5693 As an instructor I need feedback that the lecture in the room 
>>>> I am right now is recorded ("on air" lamp) and I need a opportunity to 
>>>> stop it
>>>>    • MH-5908 As an instructor I want to have confidence that my lecture is 
>>>> being captured correctly.
>>>> What do you think? (Both about the stories being satisfied by Galicaster 
>>>> and about the general concept of closing Matterhorn stories that are 
>>>> satisfied by non-Matterhorn software?)
>>> 
>>> Resolving issues which 3rd party software fixes seems like an unwise
>>> decision to me...  There has been lots of demand for live streaming,
>>> which a few of the commercial CA vendors have available.  We don't close
>>> stories for that kind of thing, so I don't think it's appropriate to
>>> close them in this case either.  If they want to contribute the code
>>> back they're certainly welcome to, but unless it's in the mainline
>>> codebase I don't think we can consider the issue resolved.
>>> 
>>> G
>>> 
>>>> Judy
>>>> 
>>>> On Apr 29, 2012, at 1:57 AM, Vicente Goyanes wrote:
>>>> 
>>>>> Hello Andreas,
>>>>> 
>>>>> 
>>>>> AK> ... I'll go install Galicaster next week on one client to have a look
>>>>> AK> at it for myself.
>>>>> 
>>>>> Thank you for give it a try, Andreas. We are keen to hear your feedback.
>>>>> 
>>>>> 
>>>>> AK> but sounds just like what our lecturers are looking for ...
>>>>> 
>>>>> That's the point.
>>>>> 
>>>>> Galicaster was designed to fit the real requirements of two different
>>>>> types of users:
>>>>> 
>>>>> 1. Professors
>>>>> 
>>>>> 2. Audiovisual production staff of a University media service.
>>>>> 
>>>>> The requirements was gathered at the University of Vigo, for the "Campus
>>>>> do Mar" MH pilot project.
>>>>> 
>>>>> As Chris said in other email is good to clarify that, even some of the 
>>>>> developers
>>>>> of Galicaster has been part of the original MH Capture agent development
>>>>> team (leaded by Chris, thank you for that) Galicaster is a completely
>>>>> different piece of software.
>>>>> 
>>>>> Galicast was created from scratch but taking advantage of all we learned
>>>>> working on the development of the original MH-CA and taking in 
>>>>> consideration
>>>>> the new requirements gathered for UVigo's MH pilot. Galicaster is written
>>>>> in Python, (not JAVA) and the license is CC non commercial (not ECL).
>>>>> 
>>>>> We are pretty sure that Galicaster will match the needs of other 
>>>>> Universities
>>>>> in Spain, but regarding to Universities abroad, it's an open question for 
>>>>> us, so
>>>>> we really appreciate any feedback from you and others trying Galicaster 
>>>>> outside Spain.
>>>>> 
>>>>> Thank you again for your interest on Galicaster.
>>>>> 
>>>>> 
>>>>> Best Regards,
>>>>> Vicente
>>>>> 
>>>>> 
>>>>> 
>>>>> AK> :) regards, Andreas
>>>>> 
>>>>> 
>>>>> AK> Vicente Goyanes schrieb am Thu, 26 Apr 2012 betreff 
>>>>> "[Matterhorn-users]...":
>>>>>>> Dear All
>>>>> 
>>>>>>> I'm very pleased to announce the release of Galicaster v1.1 capture 
>>>>>>> software
>>>>> 
>>>>>>> Galicaster based capture agents (CA) can work as improved Matterhorn 
>>>>>>> CAs. they can register as a capture agent, thus being able to receive 
>>>>>>> scheduled recordings and ingest the resulting mediapackages 
>>>>>>> automatically.
>>>>> 
>>>>>>> Quoting one Galicaster user:
>>>>> 
>>>>>>> "Everybody here loves your fine software, it is very polished and gives 
>>>>>>> the much-needed user interface to the recording process. The 
>>>>>>> touch-screen UI is just so inviting, people come into my room and just 
>>>>>>> ask "what's this thing you have" and start playing with it constantly." 
>>>>>>> ( Tero Kärkkäinen, Network systems administrator, University of 
>>>>>>> Helsinki )
>>>>> 
>>>>> 
>>>>>>> For those eager to give it a try or to know how to assemble your own 
>>>>>>> Galicaster based CA, please access the Galicaster website:
>>>>> 
>>>>>>> www.galicaster.org
>>>>> 
>>>>> 
>>>>>>> We are keen to hearing your feedback, suggestions, bug reports, etc... 
>>>>>>> on this list or on Galicaster community list [1]
>>>>> 
>>>>>>> We hope the Galicaster project can enrich the MH CAs ecosystem and add 
>>>>>>> a bit to make Matterhon the best choice for new adopters.
>>>>> 
>>>>> 
>>>>>>> Best Regards
>>>>>>> Vicente
>>>>> 
>>>>>>> PD. Thank you so much, Tero and all the rising Galicaster community
>>>>> 
>>>>>>> [1] http://wiki.teltek.es/display/Galicaster/Community
>>>>> 
>>>>>>> --
>>>>>>> Vicente Goyanes
>>>>>>> Gerente - CEO
>>>>>>> [[email protected]]
>>>>> 
>>>>>>> TELTEK Video Research, S.L.
>>>>>>> Pza Miralles s/n
>>>>>>> 36310 Vigo - Pontevedra
>>>>>>> T (+34) 986 160 125
>>>>>>> M (+34) 619 318 484
>>>>>>> [email protected] | www.teltek.es
>>>>> 
>>>>>>> [IMPORTANTE] La información que pudiera contener este comunicado, 
>>>>>>> relacionada con datos
>>>>>>> de carácter personal, se encuentra amparada en la Ley Orgánica de 
>>>>>>> Protección de Datos
>>>>>>> 15/99, que compromete a no utilizar estos datos para fines que no sean 
>>>>>>> los estrictamente
>>>>>>> necesarios para la realización de su cometido, añadiendo además la 
>>>>>>> absoluta confidencialidad y exclusividad, quedando prohibida a 
>>>>>>> cualquier persona su revelación, copia,
>>>>>>> distribución o el ejercicio de cualquier acción relativa a su 
>>>>>>> contenido. Si recibe este correo electrónico erróneamente, ruego lo 
>>>>>>> elimine de todos sus archivos. [#]
>>>>> 
>>>>> AK> -----------------------
>>>>> AK> [email protected]
>>>>> AK> 01/58801 DW 41523
>>>>> AK> mobil: 0664/60 588 4523
>>>>> AK> TU Wien
>>>>> AK> DVR-Nummer: 0005886
>>>>> AK> -----------------------
>>>>> 
>>>>> 
>>>>> 
>>>>> Un Cordial Saludo / Best Regards
>>>>> 
>>>>> --
>>>>> Vicente Goyanes
>>>>> Gerente - CEO 
>>>>> [[email protected]]
>>>>> 
>>>>> TELTEK Video Research, S.L.
>>>>> Pza Miralles s/n
>>>>> 36310 Vigo - Pontevedra 
>>>>> T (+34) 986 160 125
>>>>> M (+34) 619 318 484 
>>>>> [email protected] | www.teltek.es
>>>>> _______________________________________________
>>>>> Matterhorn-users mailing list
>>>>> [email protected]
>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
>>>> 
>>>> _______________________________________________
>>>> Matterhorn-users mailing list
>>>> [email protected]
>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
>>> 
>>> 
>>> _______________________________________________
>>> Matterhorn-users mailing list
>>> [email protected]
>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
>> 
>> _______________________________________________
>> Matterhorn-users mailing list
>> [email protected]
>> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
> 
> 
> _______________________________________________
> Matterhorn-users mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users

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

Reply via email to