On Wed, Nov 21, 2012 at 4:23 PM, Robert Barbey <robert.bar...@acrolinx.com> wrote: > Hi everyone, > > as I mentioned earlier on this list, I'm working on a Writer extension in > Java. We're using Maven as a build tool and I wanted to let Maven generate > description.xml and update.xml files based on the information in the POM. > That's why I started writing a Maven plug-in that can do that. > > I convinced my CTO that it would be a good idea to donate this plug-in's > sources once it's completed. I'd like to know what's necessary in terms of > licensing. Is it sufficient to prepend a licensing statement to each source > file or is more involved? Are they any formatting conventions I should know > about? And what about package names? >
So two options: 1) Make your extension be open source at Apache, for distribution within an OpenOffice release 2) Make it open source elsewhere, like on SourceForge, and distribute it on our extensions website: http://extensions.openoffice.org/ Key insight is that for #2 you can have any license you want. Of course, we think the Apache License is a fine license. For #1 we'd want to first have a discussion on the list on what your extension does and whether it makes sense to be part of the project. Regards -Rob > Thanks for your help! > > Best, > Robert >
