You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Jürgen Schmidt <jo...@gmail.com> on 2012/09/11 12:26:56 UTC
[DISCUSS]: What should be part of AOO by default or what belongs
more into a broader eco-system around AOO
Hi,
based on an enquiry for some partnership I think it make sense to
discuss a general question. Which features, improvements, enhancements
should be part of AOO by default or which belongs more in a broader
eco-system around AOO and should be better provided as an extension.
Means we provide support on basis of technical collaboration to achieve
the realization of such an extension but we prefer probably the
realization (hosting) outside of the project to avoid confusion or to
benefit some parties over others.
There are more things that should be taken into account and I would like
to hear other opinions on this as well.
Things that comes to my mind where I would always prefer an extension
solution:
- Connectors to some non free, non open source software based on
proprietary API's. It can be different when a solution is based on open
standards and is of more general use like for example a connector or
better UCP to allow access of file in a CMS via CMIS.
- Dependencies on external GPL, LGPL libraries.
- Rarely used features only important for a minority of our users. I
think we want to minimize the default memory footprint where possible
and making these kind of features available as extensions can make
sense. But it shows also that it can make sense to have extensions
hosted in our repo as well ;-)
- ...
What do others think about it.
Juergen
Re: [DISCUSS]: What should be part of AOO by default or what belongs
more into a broader eco-system around AOO
Posted by Kevin Grignon <ke...@gmail.com>.
Hello All,
Great topic. I too belong to the "less is more" school. Great in theory,
harder to realize with a moving ship ;)
Re: connectors
- this is a great way to extend the core
- perhaps we could create a stronger development eco-system for extensions
- perhaps we could make the extension more consumable and discoverable for
end users
Re: smaller footprint
- this is also great
- perhaps the core becomes so light that it can be the base for full on
custom applications
- I assume this is a core theme in Future AOO? Hope so
- build a full eco-system like Firefox, or Evernote
- the default install for AOO could include the core, and some common
extensions
- then we make it easy for people to manage extensions
- perhaps we explore ways for people to discover and access extension to
extend the core in the context of a task
ex: I'm doing some advanced publishing, and I trigger a one-click
installation of an extension from within an AOO view or dialog related to
formating content -- on demand capabilities
- more broadly, we could provide a better experience to enable or disable
extensions on demand
Thoughts?
Oh ya, I wanted to mention that UX is in the process of deploying a task
prioritization survey<http://wiki.openoffice.org/wiki/AOO_Survey_Templates_-_Task_Prioritization>,
the results of which can feed into the conversation.
Regards,
Kevin
On Fri, Sep 21, 2012 at 3:55 PM, Shenfeng Liu <li...@gmail.com> wrote:
> 2012/9/13 Andrea Pescetti <pe...@apache.org>
>
> > On 11/09/2012 Rob Weir wrote:
> >
> >> On Sep 11, 2012, at 12:27 AM, "Jürgen Schmidt" wrote:
> >>
> >>> Things that comes to my mind where I would always prefer an extension
> >>> solution:
> >>> - Connectors to some non free, non open source software based on
> >>> proprietary API's. ...
> >>>
> >>> - Dependencies on external GPL, LGPL libraries.
> >>> - Rarely used features ...
> >>>
> >> I think those are reasonable guidelines. Amother category is a
> >> "standard extension" that is under ALv2 and is part of a release.
> >>
> >
> > I agree, these components should be packaged as extensions.
> >
> >
> > We should probably think of what install enhancements we can make to
> >> better facilitate bundling of extensions. To the developer and user,
> >> extension + easy install integration should feel the same as adding a
> >> feature to the core.
> >>
> >
> > The main problem is that the ecosystem around OpenOffice is completely
> > unknown to most end users. It would be a huge leap forward to use the
> > bottom-right part of the Start Centre to promote this ecosystem
> > (Extensions, Templates, everything that makes sense) by displaying a
> couple
> > lines of dynamic content retrieved from sources we control. Examples of
> > content we could broadcast there:
> > - "Add a grammar checker to OpenOffice: [link to LanguageTool/LightProof
> > on the Extensions site]"
> > - "Download a CV template for OpenOffice: [link to a template on the
> > Templates site]"
> > - "Add clipart to OpenOffice: [relevant link]"
> > - "Tip of the day: using styles in OpenOffice [link to wiki page]"
> >
> > Instead of promoting certain items, I think generally we should make the
> Search function more visible to users. Just like I don't know what's in App
> Stores, I just try a search and see what I can get.
> The current 3 small icons at the bottom-left of the welcome page for
> templet/extension/website are too far to get users' attention, even though
> the web pages they link to are very cool. We can redesign it will more
> visible icons and sentences, even search dialog on the welcome page. Of
> course, Quickstarter is another good place.
>
> - Simon
>
>
>
> > This shouldn't be hard to do and it would allow us to make users aware of
> > the ecosystem around OpenOffice, which in turn means we can be confident
> > that users will try to find functionality in Extensions if they don't
> have
> > it readily available in OpenOffice.
> >
> > Regards,
> > Andrea.
> >
>
Re: [DISCUSS]: What should be part of AOO by default or what belongs
more into a broader eco-system around AOO
Posted by Shenfeng Liu <li...@gmail.com>.
2012/9/13 Andrea Pescetti <pe...@apache.org>
> On 11/09/2012 Rob Weir wrote:
>
>> On Sep 11, 2012, at 12:27 AM, "Jürgen Schmidt" wrote:
>>
>>> Things that comes to my mind where I would always prefer an extension
>>> solution:
>>> - Connectors to some non free, non open source software based on
>>> proprietary API's. ...
>>>
>>> - Dependencies on external GPL, LGPL libraries.
>>> - Rarely used features ...
>>>
>> I think those are reasonable guidelines. Amother category is a
>> "standard extension" that is under ALv2 and is part of a release.
>>
>
> I agree, these components should be packaged as extensions.
>
>
> We should probably think of what install enhancements we can make to
>> better facilitate bundling of extensions. To the developer and user,
>> extension + easy install integration should feel the same as adding a
>> feature to the core.
>>
>
> The main problem is that the ecosystem around OpenOffice is completely
> unknown to most end users. It would be a huge leap forward to use the
> bottom-right part of the Start Centre to promote this ecosystem
> (Extensions, Templates, everything that makes sense) by displaying a couple
> lines of dynamic content retrieved from sources we control. Examples of
> content we could broadcast there:
> - "Add a grammar checker to OpenOffice: [link to LanguageTool/LightProof
> on the Extensions site]"
> - "Download a CV template for OpenOffice: [link to a template on the
> Templates site]"
> - "Add clipart to OpenOffice: [relevant link]"
> - "Tip of the day: using styles in OpenOffice [link to wiki page]"
>
> Instead of promoting certain items, I think generally we should make the
Search function more visible to users. Just like I don't know what's in App
Stores, I just try a search and see what I can get.
The current 3 small icons at the bottom-left of the welcome page for
templet/extension/website are too far to get users' attention, even though
the web pages they link to are very cool. We can redesign it will more
visible icons and sentences, even search dialog on the welcome page. Of
course, Quickstarter is another good place.
- Simon
> This shouldn't be hard to do and it would allow us to make users aware of
> the ecosystem around OpenOffice, which in turn means we can be confident
> that users will try to find functionality in Extensions if they don't have
> it readily available in OpenOffice.
>
> Regards,
> Andrea.
>
Re: [DISCUSS]: What should be part of AOO by default or what belongs
more into a broader eco-system around AOO
Posted by Andrea Pescetti <pe...@apache.org>.
On 11/09/2012 Rob Weir wrote:
> On Sep 11, 2012, at 12:27 AM, "Jürgen Schmidt" wrote:
>> Things that comes to my mind where I would always prefer an extension
>> solution:
>> - Connectors to some non free, non open source software based on
>> proprietary API's. ...
>> - Dependencies on external GPL, LGPL libraries.
>> - Rarely used features ...
> I think those are reasonable guidelines. Amother category is a
> "standard extension" that is under ALv2 and is part of a release.
I agree, these components should be packaged as extensions.
> We should probably think of what install enhancements we can make to
> better facilitate bundling of extensions. To the developer and user,
> extension + easy install integration should feel the same as adding a
> feature to the core.
The main problem is that the ecosystem around OpenOffice is completely
unknown to most end users. It would be a huge leap forward to use the
bottom-right part of the Start Centre to promote this ecosystem
(Extensions, Templates, everything that makes sense) by displaying a
couple lines of dynamic content retrieved from sources we control.
Examples of content we could broadcast there:
- "Add a grammar checker to OpenOffice: [link to LanguageTool/LightProof
on the Extensions site]"
- "Download a CV template for OpenOffice: [link to a template on the
Templates site]"
- "Add clipart to OpenOffice: [relevant link]"
- "Tip of the day: using styles in OpenOffice [link to wiki page]"
This shouldn't be hard to do and it would allow us to make users aware
of the ecosystem around OpenOffice, which in turn means we can be
confident that users will try to find functionality in Extensions if
they don't have it readily available in OpenOffice.
Regards,
Andrea.
Re: [DISCUSS]: What should be part of AOO by default or what belongs
more into a broader eco-system around AOO
Posted by Rob Weir <ra...@gmail.com>.
On Sep 11, 2012, at 12:27 AM, "Jürgen Schmidt" <jo...@gmail.com> wrote:
> Hi,
>
> based on an enquiry for some partnership I think it make sense to
> discuss a general question. Which features, improvements, enhancements
> should be part of AOO by default or which belongs more in a broader
> eco-system around AOO and should be better provided as an extension.
> Means we provide support on basis of technical collaboration to achieve
> the realization of such an extension but we prefer probably the
> realization (hosting) outside of the project to avoid confusion or to
> benefit some parties over others.
>
> There are more things that should be taken into account and I would like
> to hear other opinions on this as well.
>
> Things that comes to my mind where I would always prefer an extension
> solution:
>
> - Connectors to some non free, non open source software based on
> proprietary API's. It can be different when a solution is based on open
> standards and is of more general use like for example a connector or
> better UCP to allow access of file in a CMS via CMIS.
>
> - Dependencies on external GPL, LGPL libraries.
>
> - Rarely used features only important for a minority of our users. I
> think we want to minimize the default memory footprint where possible
> and making these kind of features available as extensions can make
> sense. But it shows also that it can make sense to have extensions
> hosted in our repo as well ;-)
>
> - ...
>
> What do others think about it.
>
I think those are reasonable guidelines. Amother category is a
"standard extension" that is under ALv2 and is part of a release.
There are a similar set of considerations for the code author. For
example an extension may be 100% proprietary but a core code change is
always open source. So there are trade-off's depending on business
model.
We should probably think of what install enhancements we can make to
better facilitate bundling of extensions. To the developer and user,
extension + easy install integration should feel the same as adding a
feature to the core.
Maybe EuroOffice is a good use-case here? They do a lot with bundled
extensions.
-Rob
> Juergen
>
>
>
Re: [DISCUSS]: What should be part of AOO by default or what belongs
more into a broader eco-system around AOO
Posted by Kay Schenk <ka...@gmail.com>.
On 09/11/2012 03:26 AM, Jürgen Schmidt wrote:
> Hi,
>
> based on an enquiry for some partnership I think it make sense to
> discuss a general question. Which features, improvements, enhancements
> should be part of AOO by default or which belongs more in a broader
> eco-system around AOO and should be better provided as an extension.
> Means we provide support on basis of technical collaboration to achieve
> the realization of such an extension but we prefer probably the
> realization (hosting) outside of the project to avoid confusion or to
> benefit some parties over others.
>
> There are more things that should be taken into account and I would like
> to hear other opinions on this as well.
>
> Things that comes to my mind where I would always prefer an extension
> solution:
>
> - Connectors to some non free, non open source software based on
> proprietary API's. It can be different when a solution is based on open
> standards and is of more general use like for example a connector or
> better UCP to allow access of file in a CMS via CMIS.
>
> - Dependencies on external GPL, LGPL libraries.
>
> - Rarely used features only important for a minority of our users. I
> think we want to minimize the default memory footprint where possible
> and making these kind of features available as extensions can make
> sense. But it shows also that it can make sense to have extensions
> hosted in our repo as well ;-)
>
> - ...
>
> What do others think about it.
>
> Juergen
>
>
>
I'm pretty much in the "less is more" camp by default with everything in
my life, so I would probably agree with your assessment here. We don't
want to contribute to "bloat". So...
item #3, definite agreement
items #1 and #2, could you give us some examples of what you mean here?
What are we doing now? What would be eliminated?
--
------------------------------------------------------------------------
MzK
"We never sit anything out. We are cups, constantly and quietly
being filled. The trick is, knowing how to tip ourselves over and
let the beautiful stuff out."
-- Ray Bradbury, "Zen in the Art of Writing"