Hi Kevin, > 1) Status of Epiphan Matterhorn Device development > * Are there issue tracking for bugs/fixes for this device?
Not a public tracker to my knowledge. > * Who is working on this device (besides Greg Logan)? Just Greg and the folks at Epiphan I believe. > * How is Epiphan involved? They make all the hardware and firmware builds. Greg did the integration over to Matterhorn. > * When will this device be ready for production use? Would love to hear more from Epiphan on this as well. > 2) Database Selection > * How are adopter institutions making their database choices for > Matterhorn deployment? We chose MySQL because it is better than postgres. (ok, it was arbitrary based on our familiarity) > * Will Matterhorn be officially supporting any particular database > for, say, upgrade scripts for new releases? I would encourage the MH team to drop one of the DB's, whichever one, so that QA is easier. My guess is this won't happen though. (as was with 1.2 we shipped with a broken set of postresql ddl scripts) > * In terms of the overall choice between MySQL and PostgreSQL, are > folks concerned that MySQL is now owned by Oracle? Oracle has stated Not really a concern of mine. Matterhorn uses JPA for our DB communication. This means that switching over to a new DB product is pretty trivial for a developer. QA for each platform should be done, and we have (or will, starting with 1.4) introduce some DB guidelines to make this even easier in the future. Nothing fancy is being done on the DB at the moment, though there is room for improvement here. As Hank said, lots is in solr too. I see this as some concern, since it means learning a new query language/system/getting solr admins/etc. But it hasn't bit us at all yet in production, so it might not be a big concern. Chris _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
