Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jogischmidt@gmail.com
 designates 209.85.214.47 as permitted sender)
Message-ID: <5064546B.6000907@gmail.com>
Date: Thu, 27 Sep 2012 15:28:11 +0200
From: =?ISO-8859-1?Q?J=FCrgen_Schmidt?= <jogischmidt@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: [PROPOSAL] Reinvigorate extension authors community
References: 
 <CAP-ksoiVrvh9Leuk_OXrqVKe96S+Y-ok_F-1pBae8OS_6f6bZg@mail.gmail.com>
 <CADHP4mzs=7RXE11PCgS+Y2tnfPFfD2XskHgETc+Mg5C7Lyi=_w@mail.gmail.com>
 <CAO4+hqNts9JNKK-xPo7Cns3GGWP=LY7czSwMnES9+uypQcCv+g@mail.gmail.com>
In-Reply-To: 
 <CAO4+hqNts9JNKK-xPo7Cns3GGWP=LY7czSwMnES9+uypQcCv+g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 9/27/12 3:22 PM, Kevin Grignon wrote:
> KG01 - See comments inline.
> 
> On Thu, Sep 27, 2012 at 2:50 AM, Albino B Neto <bino28@apache.org> wrote:
> 
>> Hi.
>>
>> On Wed, Sep 26, 2012 at 2:34 PM, Rob Weir <robweir@apache.org> wrote:
>>> 1) Create a new mailing list:  ooo-extensions@incubator.apache.org (or
>>> appdev@incubator.apache.org if we prefer).  I'll assert that the
>>> current mailing lists are inadequate for encouraging this community to
>>> thrive.  If they interact on ooo-dev then they are bombarded with 99%
>>> irrelevant posts, and if they gather on ooo-users then this will be
>>> disruptive to the end-user subscribers there.  Extension authors
>>> really are a distinct sub-community of their own.
>>
>> I agree.
>>
>> Demand for emails here on ooo-dev is great, a specific list for
>> API/extension will be better.
>>
>>> 2) Promote the mailing list via the usual means:  website, social
>>> networking, maybe a blog post.
>>>
>>> 3) Try to contact the existing extension authors, to encourage them to
>>> joint the list.  I'd try to do this via SourceForge initially, since
>>> they might already have the means to send them all an email.
>>>
>>> 4) Promote AOO extension development in general, by interviews of
>>> extension authors, blog posts, perhaps even a rotating spot on our
>>> website featuring an "extension of the week" (or day).
>>
> 
> KG01 - I say will integrate the extension experience within the editors.
> Start pages and docked task panes could promote extensions and drive
> traffic to extension marketplace/downloadplace/place where we keep them ;)
> Furthermore, we could create an integrated extension manager that actually
> allows users to browse, select and enable extensions, just like an iTunes
> app store or the Evernote trunk. The goal would be to keep users in the AOO
> tools and bring the extensions to them - on demand. This would scale well
> to support any effort to reduce the footprint and surface advanced
> capabilites via extensions.

That was the initial idea of us when we started with the extension
manager. It's still on a my wish list together with a smoother
integration of the template repository. Easy navigating online
templates, bookmark them, download them for offline usage etc.

And both repo's would be configurable for enterprise internal usage,
means internal repo's and no public ones.

Juergen


> 
> 
>>>
>>> 5) Encourage this community to provide feedback to the project and
>>> help maintain the current app dev and SDK documentation, website and
>>> wiki.
>>
>> Yeah!
>>
>> We need listing more users. (:
>>
>>> I'll need a couple more list moderator volunteers as well.
>>
>> Me.
>>
>> Albino
>>
>