That was pretty funny I have to admit. You should start working on some new material though.
> On Nov 26, 2013, at 5:08 PM, Emmanuel Sowah <eso...@gmail.com> wrote: > > Dude, > > Glad you've finally found out yourself that following and coding Tapestry > won't pay the bills. It's a failed framework and nobody is using it for > serious work. > If you really want to earn serious cash that would pay the bills, take a > serious look at other serious frameworks like Apache Wicket. Howard is > already happily coding Wicket on his clients' projects. Else he would have > gone bankrupt by now. > > Thiago, be wise and quit the sinking (Howard Lewis) Ship, as Jesse Kuhnert did > a few years ago. He also couldn't pay his bills by just coding Tapestry. He > then left for other compelling and serious web framework. Life is short, > Thiago. So don't waste time. Stop letting Howard use you like a slave. > > Cheers > > > On Mon, Nov 25, 2013 at 10:08 PM, Thiago H de Paula Figueiredo < > thiag...@gmail.com> wrote: > >> Hi! >> >> I've just went live with an IndieGogo campaign so I can work a whole month >> in Tapestry itself and nothing else fixing bugs, implementing new stuff and >> working on the documentation. >> >> Here's the link: http://www.indiegogo.com/projects/a-month-of-apache- >> tapestry-5. >> >> Any questions, just ask. :) But I'll answer another one right now: >> regardless of the campaign succeeding or not, I'll continue posting stuff >> in the mailing list and doing my occasional code contributions the same way >> and I've been doing until now. In other words, nothing changes. >> >> Here's the campaign text, just in case, with all the details: >> >> Introduction >> >> Disclaimers: This campaign is done by me, Thiago, as an independent >> individual, not by the Apache Software Foundation or the Apache Tapestry >> project. I'm not representing the Foundation in any way in this campaign >> nor Apache endorses it. The Foundation has a policy of not paying for >> development work. All its members are voluntary, me included. Any code I'll >> write or change will pass the usual Tapestry team approval process. If this >> campaign isn't funded, I'll continue participating in the Tapestry project >> in the same way as always. >> >> I'm Thiago H. de Paula Figueiredo, an Apache Tapestry 5 committer and PMC >> (Project Management Committee) member. I've posted more than 5700 times in >> the user mailing lists. Apache Tapestry is an open-source, Java Web >> framework built and supported by a team of voluntary members who work on it >> for free and by love. >> >> I dream about the idea of being able to work on Apache Tapestry itself, >> on its codebase and documentation, not just in my free time. I'm very >> passionate about this framework. I envy the people who are paid to work on >> open source projects, so they can spend lots of time in the projects they >> love. I wish I could do the same, even if it was for a short period of >> time. I love open source, I love Apache Tapestry, I love to help people to >> solve their problems, know the framework better and code happier. That's >> what this campaign is about. >> >> Right now, I'm in a period between gigs, so I have a free schedule to >> work on it, and then I have an opportunity. But this free time cannot be >> free, because I, as you and everyone else, have bills to pay. So I thought >> it would be a perfect time to run a fixed-funding IndieGogo campaign to >> have me working exclusively on the Apache Tapestry codebase for a whole >> month, 160 hours on the clock, fixing some stuff, build other stuff and >> hopefully speeding up the 5.4 release. I'd work on the documentation too. >> >> Notice that, in terms of dollar per worked hour, it is signicantly lower >> than at my last gig. This campaign isn't about money, is about being able >> to work in what I love. >> What will be done? >> >> The actual issues to be worked will be discussed among the backers, but >> I've took a long look at the Apache Tapestry issue tracker (JIRA), starting >> for the most voted issues, checked which ones I could successfully fix or >> implement, then I came up with the following initial (not final) list. The >> order in which the issues will be tackled will also be discussed among the >> backers. >> >> Issue >> Description >> >> TAP5-2029 >> Copy annotations from service implementation to proxy >> >> TAP5-2235 >> Implement JCache (JSR 107) support in Tapestry-IoC >> >> TAP5-938 >> Expose ability to render a portion of a page (a Block, Component, etc.) >> without using internal services >> >> TAP5-244 >> Let Grid show column headings when no data >> >> TAP5-1515 >> Support for external assets >> >> TAP5-1470 >> Group CSS together to avoid IE's restriction of 31 external css files >> >> TAP5-245 >> Better documentation on development environment. >> >> TAP5-627 >> Allow injection of named spring beans >> >> TAP5-1403 >> Add support for Arrays in request parameters >> >> TAP5-1863 >> Rendering components in Alerts >> >> TAP5-1659 >> PageLink: page parameter should accept page-classes and page-instances >> >> TAP5-1941 >> Alerts component should check for XHR request in "dismiss" event handler >> >> TAP5-1718 >> Tapestry-beanvalidator isn't validating nested DTO objects / Doesn't mark >> the invalid fields in the UI >> >> TAP5-2130 >> Services interfaces that inherit from "Runnable" cause @Startup methods >> being called twice >> >> TAP5-2192 >> Add support for distributed documentation >> >> TAP5-2187 >> CSS relative URL rewriting isn't lenient enough >> >> TAP5-2185 >> Problem with the asset checksums and relative paths based on them >> >> TAP5-1998 >> DateField does not validate dates properly (Tapestry DateField converts >> invalid dates to valid ones) >> >> TAP5-2168 >> Asset Not Found messages are prompting to put assets into wrong location >> >> TAP5-1611 >> out-of-the-box way in Tapestry for replacing components >> >> Perks >> >> All perks include the addition of your name and URL in a thank-you page >> in my personal blog (http://machina.com.br). >> $20: a thank you >> Did you ever asked something in the Tapestry mailing list and got a good >> answer for me? Did you ever searched the Internet for Tapestry questions >> and found the solution in a post of mine? This is a way of saying "thank >> you". >> $50: a bigger thank you >> If I ever posted something that prevented you of wasting hours on a >> problem in your project using Apache Tapestry, you can give a bigger "thank >> you". >> $100: one hour of support >> You get one hour of support through Google Hangout or Skype. Any code I >> write during this period belongs to you. >> $180: two hours of support >> You get two hours of support through Google Hangout or Skype. Any code I >> write during this period belongs to you. >> $700: eight hours of support >> You get eight hours of support through Google Hangout or Skype. Any code >> I write during this period belongs to you. >> $500: you in my e-mail signature >> You choose a line to be added in my e-mail signature when I post in the >> Tapestry mailing lists. It'll stay there for one month. I average almost 11 >> posts per week. In case more than one backer picks this perk, it'll be >> first come, first served. Check with me at thiagohp at gmail dot com before >> picking this perk. >> >> Why back this campaign? >> >> A way of saying "thank you" for my efforts for the Tapestry project >> Influence what I'm going to do next (but not the Apache Project itself) >> Having your pet issue taken care more quickly >> Having your or your company name and URL in a thank you page in my >> personal blog at http://machina.com.br. Larger contributions will come >> first and in a larger font size. >> There are a perks which give you one hour or more hours of support >> through Google Hangout or Skype. >> There's another perk which allows you to add a line of your choice in my >> personal e-mail signature for a given period of time. >> >> Risks >> >> I've made an estimate of the above tasks and I do think I can finish them >> all in the 160 hours of work for this campaign. Of course, things can turn >> out to be more complex and time-consuming than I estimated, but, no matter >> what, if this campaign is funded, I'll spend 160 hours working on the >> Tapestry codebase and documentation, not including the time I already spend >> in the mailing lists. >> >> Another risk would be me getting a good job offer before I finish the 160 >> hours. This can delay my work, but I'll guarantee that, having this >> campaign reach its goal, I'll spend 160 hours working on the Tapestry >> codebase and documentation, not including the time I already spend in the >> mailing lists. >> What if the campaign is not funded? >> >> In this case, nothing changes, everything goes as if the campaign never >> happened. I'll continue participating on the Apache Tapestry in my free >> time in the exact same way I've been doing in the last 6 years: lots of >> messages on the mailing lists and some code contributions. >> Deadline >> >> My initial plan is to work the 160 hours in the 30 days after the >> confirmation of the funding. Even if the initial plan falls apart due to an >> eventual outstanding job offer, my ultimate deadline will be 7 months after >> I get the confirmation this campaign if funded. This deadline was >> calculated considering I'd work 40 hours per week in the eventual job I'd >> get and 5.7 hours per week on Tapestry. >> >> -- >> Thiago H. de Paula Figueiredo >> Tapestry, Java and Hibernate consultant and developer >> http://machina.com.br >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
