as long as we don't call it the "AppStore". :)
http://www.cnn.com/2011/TECH/web/03/22/apple.amazon.app.fast/index.html

On Mon, Mar 26, 2012 at 4:54 PM, Michelle Ziegmann <
[email protected]> wrote:

>  Unfortunately, I don't have those notes any more. But I may be able to
> resurrect the old site and offer some screenshots. What I had built was
> very similar to Atlassian's plugin exchange (though I see
> http://plugins.atlassian.com has since undergone a big facelift),
> providing a public forum for organizations to post available addons,
> workflows, etc.
>
> For this public website, I would really recommend using a well known
> content management framework like Drupal to build this, to make it easier
> to update the theme and add new features as things evolve. We could set
> this up at a subdomain like http://apps.opencast.org, maybe?
>
> Michelle
>
>
> On 3/26/2012 3:52 PM, Adam Hochman wrote:
>
> I was politely reminded by my colleague, Michelle Ziegmann, that she
> created an exchange presence on our former Matterhorn web site.   It was on
> my plate to review it and promote it, but sadly it fell off my radar.  It
> is a good example of why the list is so important, and that others should
> be invested and involved. She alerted me she had done a bunch of research
> on the site which hopefully she still has and can share with you.
>
>  Best,
> Adam
>
> On Mon, Mar 26, 2012 at 3:21 PM, Adam Hochman <[email protected]>wrote:
>
>> I've dreamed of having a Matterhorn Market Place since Matterhorn's
>> inception and would be thrilled if you could take at least modest steps to
>> make this happen.  Currently we have stuff referenced on the wiki and
>> contrib tools in an svn repo.  Some of these tools are well documented but
>> there are quite a few that are no longer relevant.  There was some work on
>> building this marketplace using Drupal, but for a variety of reasons it
>> never came to fruition.
>>
>>  One of the most difficult challenges is determining which version of
>> Matterhorn the "contrib" supports and clear documentation to install and
>> describe it.  Another challenge is seeding the marketplace with enough
>> goodies to make it a destination.  If there are only a few items submitted
>> and it remains static for a long time, it ceases to be worthwhile.
>>
>>  If you're looking for examples, I am particularly impressed with
>> Atlassian's plugin marketplace and management tool, and I think it would be
>> a great example to strive for.
>>
>>  On Mon, Mar 26, 2012 at 7:13 AM, zf6465 <[email protected]> wrote:
>> <SNIP>
>>
>>> 1. Matterhorn Market Place
>>>
>>> I have rich knowledge in Java, Javascript and HTML which is required for
>>> this idea. And I am very interested to design and implement a market
>>> place
>>> for Matterhorn.
>>>
>>> For this project, I understand that a website should be built for market
>>> place, and should be integrated into the current admin UI. But I am not
>>> clear about the last requirement, which is "people can upload the modules
>>> workflow definitions, etc. that they want to offer", does it mean that
>>> the
>>> customer can offer suggestion or requirement so that Matterhorn can serve
>>> them better? Could you please elaborate more on this?
>>>
>>>
>
>
> _______________________________________________
> Community mailing 
> [email protected]http://lists.opencastproject.org/mailman/listinfo/community
>
>
> To unsubscribe please [email protected]
> _______________________________________________
>
>
> --
>
> Michelle Ziegmann
> Educational Technology Services
> University of California Berkeley
>
>
> _______________________________________________
> Community mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/community
>
>
> To unsubscribe please email
> [email protected]
> _______________________________________________
>
_______________________________________________
Community mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/community


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to