Hi John, great news on the YouTube bugfix! I have one question on embedding the bundle in Matterhorn:
> Several issues arise with this fix that I, as a new developer, would like > some feedback on: > 1) Can this fix go into the 1.4 release? UC Berkeley would like to see it in > the release as YouTube is one of our main distribution points. >From my point view absolutely. YouTube distribution was working in 1.3 and >does not work anymore in 1.4, so it clearly is a bug. In addition, a bug has >been filed already with a fixed version for 1.4. > 3) Handling and use of the combined Bundle itself. Here is a pom.xml entry > for it: > <dependency> > <groupId>org.sakaiproject.nakamura</groupId> > <artifactId>javax.activation-mail</artifactId> > <version>1.1.1.1.4.2-1.3.0</version> > </dependency> > The options I see for use of it are: > • Install the bundle in the Matterhorn maven repository - my preferred > option > • Add the Sakai repository to our list of maven repositories and pull > it from there > • Build a new bundle from scratch that will be a matterhorn bundle > I did chat with Carl Hall, the developer who built it and is a former > colleague of mine from the Sakai Nakamura project. He said that licensing > will permit option 1 and he agreed with me that having control over it, e.g. > installing it in the Mattehorn repo, is probably the best option. Can I ask why you think 1) would be the best option? Why maintain a bundle ourselves that is already maintained and hosted by the Sakai project? That being said, we can easily - if licensing allows - upload the bundle to the Matterhorn Maven repository. > 4) What to do about the matterhorn-composer use of the service-mix mail > bundle? Have you been able to see how the bundle is being used there? Tobias _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
