Hi,

We've had a number of questions about how to contribute to OpenLaszlo so I
thought I'd send a quick email out to the list. We try to make the process
as straightforward as we can to encourage all of you to think about
contributing.

In a nutshell, the first step is to sign a contributor's agreement, then
submit a patch. We'll review it and you'll be given feedback and then we'll
include it in the incubator. We'll also create a JIRA bug to track its
inclusion in the incubator. Once it is included, we'll announce the new
contribution on the laszlo-user mailing list so that others can check it out
as well.

Here's the official write up:
http://wiki.openlaszlo.org/index.php?title=Patch_Guidelines

You can find more about the contributor's agreement here:
http://www.openlaszlo.org/cfaq (basically, you assign rights to Laszlo
Systems to include the software as part of OpenLaszlo, and then they assign
all rights to the software back to you - so you could even sell your tools
if you wanted.)

That's pretty much it!

Amy

On Fri, May 27, 2011 at 7:49 PM, Amy Muntz <[email protected]> wrote:

> Hi,
>
> It's been a while since we've sent out an update on what's been going on
> inside the OL project.  Basically, we've been fixing lots of bugs and
> working steadily on features in the trunk branch.
>
> Since it has been a while since we pushed an official release out to the
> community, we are going to do that next week. This will be 4.10.  If you
> look in JIRA, you will see that we have 559 fixes/improvements  since the
> last release in October, 2010.  That's alot of stuff!!!!
>
> And, there are a number of new features - we made canvas attributes
> CSS-able, we added tiling for views for DHTML, views now listen for updates
> to parent font, fontsize, fontstyle and fgcolor values, drawview supports
> scale/rotate/translate for all runtimes, and tooltips have been promoted
> from the incubator, to name a few. We've also made numerous performance
> improvements in the script compiler and improvements to lzo's (or binary
> libraries).
>
> Our goal is to get these fixes out more regularly moving forward. So stay
> tuned for updates and help support the project by getting those bug reports
> in and by helping us implement new features/functionality.
>
> If you have developed a cool OL tool, consider contributing it back to the
> project to support open source software development. Everyone benefits.
>
> Thanks,
> Amy
>

Reply via email to