Re: Apache Tiles Wants YOU

> Hello all,
>
> I am sending this message to ensure that everyone who would like to
> help Apache Tiles move forward has the opportunity to help. If you
> have been watching the mailing lists you will have noticed that
> Antonio Petrelli has been doing a lot of work. By "a lot of work" I
> mean Antonio has done all the commits, most of the Jira updates and
> release planning, and the vast majority of mailing list support for
> quite a long time now. While we are immensely grateful for Antonio's
> contributions we would obviously like a larger group of people to
> participate in the development of this framework.
>
> If you are subscribed to this list then you fall into one of two
> categories: Either you are using Tiles on a regular basis for your
> daily work, or you are curious about Tiles. Either way you need to
> know that the future of Tiles depends on you. If you fall into the
> first category and you made the decision to use Tiles then you can
> help validate that decision by making the framework better. If you
> fall into the first category and you did not make the decision and you
> think Tiles sucks then you can fix that by making the framework better
> :-) If you fall into the second category then you can satisfy your
> curiosity by digging into and improving the code.
>
> If you're wondering where to start check out the list of open issues:
>
>     https://issues.apache.org/struts/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?&pid=10160&status=1&status=3&status=4&sorter/field=issuekey&sorter/order=DESC&tempMax=1000
>
> You can see here everything from the Dimensions/Kaolin incubation to
> database-driven Tiles definitions to all sorts of interesting
> enhancements. Please have a look at the list and find things that
> interest you and submit a patch. How do you submit a patch? It's quite
> simple. Here's a quick guide:
>
> 1. Check out the source code.
>
>     svn co https://svn.apache.org/repos/asf/tiles/framework/trunk
>     (or appropriate repo)
>
> 2. Make changes required.
> 3. Use Maven to build and test your code.
> 4. Create a patch.
>
>     svn diff > patchfile.txt
>
> 5. Attach the patch file to the Jira ticket.
>
> If you don't see anything on the list but you have other ideas for
> Tiles we're interested in those too. Open a Jira ticket and do the
> above steps to implement your changes.
>
> If framework code doesn't interest you we could always use
> documentation and/or examples or even snazzy screenshots and icons.
> After you've done this a few times don't be surprised if you see an
> invitation to become a Tiles committer.
>
> If you still feel lost but want to help I will provide personal
> assistance (via email and/or chat) to anyone who wants to step up and
> do more but doesn't know where to start. Feel free to email me
> privately if you need such help and I will absolutely do what I can. I
> think Tiles can grow and succeed, but that necessitates the
> involvement of many people. If you are benefiting from Tiles, please
> step up and do what you can. If you are not benefiting then this is
> your opportunity to become a hero :-)
>
> Thanks,
> Greg
>