[Chandler-dev] Removing plugins and what else for Preview?
Katie Capps Parlante
capps at osafoundation.org
Wed Feb 7 12:42:01 PST 2007
I'll also point out that the model isn't for plugins to be relegated to
a separate menu over the long term. In the short term, many of the
plugins we have will only have a "demo" level of quality.
Another advantage to not including all "demo" and "test" plugins
out-of-the-box is that we cut out testing work in the Preview timeframe.
We have a higher level of commitment to any menu items available
out-of-the-box (in the Preview timeframe).
After Preview (perhaps even very shortly after preview), we can put work
into the plugins to be more seamlessly integrated into the app. I wish
we had time to do that before Preview, but we have to stay focused on
making the core work first.
Katie Capps Parlante wrote:
> Heikki Toivonen wrote:
>> Andi Vajda wrote:
>>> If we go this route, I'd like to propose renaming the 'Experimental'
>>> menu to 'Plugins'.
>> I think Tools might be more appropriate, as we could then have some
>> other things besides plugins there, like repo check and whatever else we
>> might want to move from the Test menu.
> Mimi and I discussed "Demo", which is appropriate for the current state
> of the flickr/amazon/etc. plugins.
> Perhaps a "Tools" menu makes sense for those items we want to keep
> around in all releases (check repo, etc.). Perhaps the "test" items that
> we fork off into a separate plugin could be added to the "Tools" menu
> when included, and some core functionality could always live in "Tools".
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "chandler-dev" mailing list
More information about the chandler-dev