On 03/26/2016 05:58 PM, Dennis E. Hamilton wrote:
-----Original Message-----
From: Andrea Pescetti [mailto:pesce...@apache.org]
Sent: Saturday, March 26, 2016 10:38
To: dev@openoffice.apache.org
Subject: Re: Releasing the Apache OpenOffice API plugin for NetBeans
On 20/03/2016 Patricia Shanahan wrote:
The issue is whether it is ASF distributed software, for which ASF
trademarks can appropriately be used. I think it is and should
continue
to be ASF distributed software.
[ ... ]
2) We go for the full release vote, but this is a serious process, much
more than what is needed for this tool. If one really wants to do it
right, you need a release manager, binding votes, sources in dist/, GPG
signing the way the ASF wants it, old sources preserved in the ASF
archives...
[orcmid]
I'm puzzled about one thing.
There are small Apache projects. I suspect there are more small ones than
large ones.
Yet, making releases does not seem to be that burdensome to those projects.
They have it work and they satisfy the Apache requirements for releases and the
integrity of Apache-released code.
I think the biggest issue with these devtools in general for the project
is that it's not AOO core code. Almost all of us use AOO or we wouldn't
be here. Only a few use this NetBeans tool and fewer still (me) use the
newer tools I have been working on for Gradle and Groovy which I hope
will change once people see value in them.
I have no issue going through the release process with these tools as
long as enough people don't mind the verification process.
The UNO Tools work strikes me as a commendable way of spinning out useful
releases on the same cadence as small projects manage. (It is also a small
case that sort of demonstrates the process and how it is achievable.)
Agreed.
Now it is a bit of a problem that this has been a one-committer effort, and it
would be great if supported by more contributors. Having some community
building around this component of AOO would be valuable.
Actually there have been solid contributions by others as far as the
NetBeans plugin is concerned. The most resent being the Japanese message
bundles for AOO branding which is the purpose of this release
discussion. Spanish and Italian contributions have also been made.
With that, the release process should become systematic and sustainability
would also be addressed.
Isn't that worth looking into?
I think there is a strong case for these tools to be properly released
and will put them forward as I have time.
Providing tools for extension developers only helps our ecosystem. As
more extension developers use the new tools I think more people will
find a way to contribute as I did.
On a similar topic I posted a [DISCUSS] email [1] looking for help
trying out the Groovy UNO API extension and haven't got any takers.
[HELPWANTED] may have been a better subject.
I would like to get a vote ready for that one soon but I was hoping a
few people would test it first if anybody has a few spare cycles :)
[1]
http://mail-archives.apache.org/mod_mbox/openoffice-dev/201603.mbox/%3C56E60EF7.4040304%40apache.org%3E
Thanks,
Carl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
