Josh,

I'm just curious: how are the msub users managed? When we request access, do
we have to also specify the usernames we would like to have access with? Is
it going to be a single user for institution? In case several users are
allowed, can they manage their password somehow?

I know we briefly talked about it before, but these questions occurred to me
now that we are about to create our own UVigo's msub.

Thanks!

2011/4/25 Josh Holtzman <[email protected]>

> As Matterhorn goes into pilot and production at more institutions, adopters
> will undoubtedly be making changes to the code.  We expect to see custom
> workflows, encoding profiles, security configurations, Atom and RSS feeds,
> and other customizations that we haven't thought of, requiring deeper
> changes to underlying services or user interfaces.
>
> This is why Opencast, through our supporters at Atlassian, offers space in
> our subversion source code repository for institutions to store and share
> their Matterhorn customizations.  We've adopted the Sakai foundation's
> practice of offering "msub" directories in SVN, as described here [1]:
>
> "mSub (or massively-inclusive Subversion) was implemented to provide each
> ... Partner organization with a common, shared space in which to keep a copy
> of their local ... implementation or implementations... This approach offers
> a number of advantages to both the organization itself and the community as
> a whole:
>
>    - easier to manage local customizations
>    - easier to share production code with other organizations
>    - easier to compare customizations across organizations looking for
>    important trends
>    - easier to contribute production-tested code, bug fixes, or
>    customizations back to the community repository for inclusion in future
>    releases"
>
> There are other ways to share customizations, such as using a distributed
> version control system and a public hosting site [2], [3], but these require
> different tools than those being used by the Matterhorn developers and
> therefore make merging between repositories difficult.
>
> We therefore encourage anyone who is interested in customizing Matterhorn
> to do so in a public "msub" directory.  Simply send an email to
> [email protected] to request an msub directory for your
> institution.
>
> Thanks,
> Josh
>
> [1]
> https://confluence.sakaiproject.org/display/PROD/Deployment+Source+Code+Repository+%28mSub%29
> [2] https://github.com/
> [3] https://bitbucket.org/
>
>
>
> _______________________________________________
> 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