Nick Glencross <[EMAIL PROTECTED]> writes: > Great. Since it sounds like it's provisionally OK to be incorporated, > I'll give it a little more of a polish and include the necessary headers > and do the other formalities.
Great. > I shall be using the backend over the next few months, and so am happy > to continue to maintain it. Hmmm... The lifetime of qooxdoo is expected to be longer than a few months. :-) Once it's in the tree, people will use it and expect it to be maintained. Realistically, you should be prepared to maintain it for substantially longer than just a few months, and/or until someone else can replace you in that role. We all know this is volunteer work and you may not be able to commit to immediate fixes, but if you can't make some sort of longer-term commitment to maintain it, it's probably better remaining for your private use, not part of the qooxdoo source tree. OTOH, if you _are_ prepared to be maintaining it long-term, that would be fabulous and this additional backend would make a nice addition to the code base! (Feel free to ask on this list if there are others who might be interested in being co-maintainers, if you're concerned about the time commitments. I don't expect it to be a huge time commitment, but there is commitment involved.) Cheers, Derrell ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
