Re: [VOTE] Accept Freemarker into Apache Incubator
+1 (binding) Siegfried Goeschl On 19 Jun 2015, at 09:15, Jacopo Cappellato jaco...@apache.org wrote: Following the discussion in the thread [1], I would like to call a VOTE to accept Freemarker as a new Apache Incubator project. The proposal is available on the wiki at [2] and is also attached to this mail. The VOTE is open for at least the next 72 hours: [ ] +1 accept Freemarker into the Apache Incubator [ ] ±0 Abstain [ ] -1 because... Thank you, Jacopo Cappellato 1. http://mail-archives.apache.org/mod_mbox/incubator-general/201505.mbox/%3cccefe3ed-66c4-4766-a3d2-6d8bda855...@gmail.com%3e 2. https://wiki.apache.org/incubator/FreemarkerProposal == Freemarker Apache Incubator Proposal Abstract Freemarker is a template engine, i.e., a generic tool to generate text output based on templates. Freemarker is implemented in Java as a class library for programmers. Freemarker is a mature, widely used template engine. We propose to make Freemarker a top level project of the Apache Software Foundation, primarily so that it can build a stronger developer community, which provides more safety, stability and support to the large user base, and also helps evolving the engine and its integration with other projects (many of which are Apache projects). Proposal Freemarker is a template engine; a generic tool that generates text output (HTML web pages, e-mails, configuration files, source code, etc.) based on templates and changing data. It's not an application for end-users in itself, but a Java library, a component that programmers can embed into their products. Freemarker was originally created for generating HTML Web pages, particularly in servlet-based applications following the MVC pattern. It’s not bound to servlets or HTML, however. The Freemarker Template Language (FTL) is not a full-blown programming language like PHP. It’s a simple, specialized language (although among template languages it’s quite flexible). You meant to prepare the data to display in a real programming language, like issue database queries and do business calculations, and then the template displays that already prepared data. Freemarker 1.x was initially released under the LGPL license. Later, by community consensus, we have switched over to a BSD-style license. As of Freemarker 2.2pre1 (2003), the original author, Benjamin Geer, has relinquished the copyright in behalf of Visigoth Software Society, a nonprofit organization started by Jonathan Revusky. With Freemarker 2.3.21 (2014) the license has changed to Apache License, Version 2.0, and the owner has changed from Visigoth Software Society to three of the Freemarker 2.x developers, Attila Szegedi, Daniel Dekany, and Jonathan Revusky. Apache License, Version 2.0, is the current license. Freemarker is a mature, widely used template engine. While it continues to have a large user base, the active developer community has become rather small at this point, and we think that the Apache Way governance model and being part of the ASF (together with other projects that are already using Freemarker) would help to bring new life and energy to the project to better support the maintenance and improvements of the Freemarker codebase. A larger community may also help to improve tooling (such as IDE plugins) and integration with popular frameworks (such as Spring MVC, Struts, etc.), which could foster the adoption of Freemarker. Last but not least, being under the Apache umbrella would put the project into a more trustworthy legal context, which also helps adoption, particularly among bigger corporate users. We believe that Freemarker should become a Top Level Project as opposed to a subproject because it has a long history and already a large feature set, codebase and documentation and there is a lot of room for innovation and improvement that would involve more community management; governance and autonomy to make its own direction and manage its own community may be important long term factors for the success of the project. Background A template engine is a template language with the basic infrastructure around it (configuring, caching, etc.). A template language is a language specialized on generating text based on changing data. Template languages like Freemarker Template Language are by design much simpler than general purpose languages, while providing convenient specialized language devices for tasks that are frequent during text generation. Template engines, like Freemarker, play an important role in applications that leverage the MVC (Model View Controller) pattern; for example, several web applications and web application framework implement the MVC pattern in the user interface layer: the appearance of a page can be changed without programmers having to change
Re: [DISCUSS] Freemarker Incubation proposal
Hi Daniel, regarding “lower bar for project sexiness and buzzwordyness” - another options would be using an existing ASF umbrella project, e.g. Apache Commons. There you find a lot “unsexy but heavily used stuff” … ;-) Cheers, Siegfried Goeschl On 22 May 2015, at 19:31, Daniel Dekany ddek...@freemail.hu wrote: Technically (i.e., in source code), I don't think Velocity and Freemarker can share much. It seems that they kind of share fate though. Apparently, everyone has something more important to contribute to. And that's fine, I say, because what put these template engines into the spotlight 15(?) years ago was Web MVC, and legacy JSP's deficiencies to server that paradigm. It was a hot topic back then. But nowadays, just like in the case of Velocity (apparently), finding guys who want to hack this project for free after coding all day at the workplace, and instead of being with their families and all that, is, well... challenging. And it seems companies don't care to invest either by putting paid developers on it. (Certainly the same companies wouldn't be too happy if Freemarker is suddenly EOL-ed, though.) I guess there's some kind lower bar in project sexiness and buzzwordyness under which life just stops when it comes to contributions. Those same properties aren't needed for the project being heavily used though. So that's where we stand. But does it mean these projects should die? I don't think so. Does it mean that these projects are not for Apache? I don't know that, you tell me! Surely I don't want FM to go into incubation if failure is the most probable outcome. Can the requirements for getting out from incubation successfully be quantified? For the kind of project like this? -- Thanks, Daniel Dekany Friday, May 22, 2015, 2:44:03 AM, Ralph Goers wrote: I used to use Apache Velocity. However, it hasn’t had a release since 2010 and the overall project activity has been minimal for years. As a consequence of that, and a feature that was missing, I recently switched to using Freemarker for some templating work I needed to do. The only reason I mention Velocity is I am wondering what relationship these two projects should have, if any. I am also concerned that if interest in development of Freemarker is decreasing is it going to suffer the same fate? I guess what I am wondering is if there is some way these two communities and/or technologies could combine? FWIW, I’d be happy to mentor this project. If I had the time I know I’d want to commit, but that has been in extremely short supply of late. Ralph On May 21, 2015, at 4:38 PM, Marvin Humphrey mar...@rectangular.com wrote: On Thu, May 21, 2015 at 7:11 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Thu, May 21, 2015 at 3:38 PM, Sergio Fernández wik...@apache.org wrote: ...If you'd need any other mentor, I'm happy to help there (I'm Incubator PMC and ASF Member)... Currently I see three mentors and two committers at https://wiki.apache.org/incubator/FreemarkerProposal, I'm not involved in that podling but it looks to me that additional committers might be more useful than more mentors. 4 Mentors is a good number, though! It's true that there aren't many initial committers, but the proposal addresses this issue at length. https://wiki.apache.org/incubator/FreemarkerProposal#Known_Risks While it continues to have a large user base, the active developer community has become rather small at this point, and we think that the Apache Way governance model and being part of the ASF (together with other projects that are already using Freemarker) would help to bring new life and energy to the project to better support the maintenance and improvements of the Freemarker codebase. I think this is a reasonable plan and definitely worth a shot at incubating. The Incubator has a mixed history with podlings that start small, but Freemarker has an advantage over many of those because it begins with a large user base and wide adoption. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Please add me to the ContributorsGroup for wiki.apache.org
Hi folks, I'm a new mentor of JSPWiki but unable to to make any changes (everything in an InmutablePage) - my login name is SiegfriedGoeschl Thanks in advance Siegfried Goeschl On 10.01.13 17:12, Marvin Humphrey wrote: On Thu, Jan 10, 2013 at 8:05 AM, Craig L Russell craig.russ...@oracle.com wrote: I've reviewed the report and hereby sign off on the report. The wiki page is marked as immutable. Is it just me? What's the username you use to log into http://wiki.apache.org/incubator? I suspect we need to add you to the ContributorsGroup, because I don't see anything resembling your name in either there or Administrators. See the boxed explanation at the top of the main wiki page. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: PPMC versus commiter
Hi folks, we are a bunch of people with a bunch of different opinions but at the end of the day we have a vote - I suggest that we restart the vote along the lines * Glen Mazza as new JSPWiki committer * Glean Mazza as new PPMC member Cheers, Siegfried Goeschl On 19.12.12 20:06, Andrea Pescetti wrote: On 19/12/2012 Benson Margulies wrote: With all respect, I don't see the OO podling as typical. It's sheer size put it in a different category Indeed. In addition to what others already wrote, it should be noted that some of the OpenOffice committers only help with managing and checking in translations into a specific language, and are uninterested in the project governance at large. Regards, Andrea. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release JSPWiki version 2.9.0-incubating
Hi folks, this might be a duplicate email but I can't find my vote on the list [X] +1 approve, release Apache JSPWiki 2.9.0-incubating [ ] +0 no opinion [ ] -1 disapprove (and giving a reason) Cheers, Siegfried Goeschl On 14.11.12 02:03, Florian Holeczek wrote: Hi all, I'd like to start a vote on an incubator release for Apache JSPWiki, version 2.9.0-incubating. Apache JSPWiki (incubating) is a leading open source WikiWiki engine, feature-rich and built around standard J2EE components (Java, servlets, JSP). A vote was held on the developer mailing list [1] and passed with 9 +1s [2], two of them from our mentors. This release candidate fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12319521 The tag to be voted upon: https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating Source and binary files: http://people.apache.org/~florianh/jspwiki-2.9.0-incubating/ Checksums: JSPWiki-2.9.0-incubating-src.zip MD5:287e75857b03b41dca769211591c6144 SHA1: 74b24e526177b7ddf5394b4b96b67bb9081628a4 SHA512: 9a080ed994e4308e4ff6386f6e5e88e42d27fc8a8abe37d2874d3c8477fe097037017fffdd03430cdb0ca7a73efba91bf58e70c1943e08c9565170809daa953a JSPWiki-2.9.0-incubating-bin.zip MD5:7e774dc46c112ca895aad60fb607dc60 SHA1: e529eb02d13f4061534d85dd0e78d67c5dfe29a5 SHA512: 575eae72390178005bf7cf57332af9a1da85515d6fc10cf9c8b3548f50743c0e57c0c6f46bc99b70cd1328ef083fb4a4fe9f3867e9ec7c7e4a640b845a2e2ee4 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS For convenience, this directory includes a binary distribution and a RAT report on the cited tag. You can manually generate the RAT report from a clean source by running the rat-report Ant target. Please vote: [ ] +1 approve, release Apache JSPWiki 2.9.0-incubating [ ] +0 no opinion [ ] -1 disapprove (and giving a reason) The vote will be open for at least 72 hours. Best regards Florian Holeczek [1] http://markmail.org/message/gksvnjnru2nhhenf [2] http://markmail.org/message/mht24dwvpmm7xgft - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release JSPWiki version 2.9.0-incubating
Hi folks, this might be a duplicate email but I can't find my vote on the list [X] +1 approve, release Apache JSPWiki 2.9.0-incubating [ ] +0 no opinion [ ] -1 disapprove (and giving a reason) Cheers, Siegfried Goeschl PS: More votes and/or feedback would be welcome ... On 14.11.12 02:03, Florian Holeczek wrote: Hi all, I'd like to start a vote on an incubator release for Apache JSPWiki, version 2.9.0-incubating. Apache JSPWiki (incubating) is a leading open source WikiWiki engine, feature-rich and built around standard J2EE components (Java, servlets, JSP). A vote was held on the developer mailing list [1] and passed with 9 +1s [2], two of them from our mentors. This release candidate fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12319521 The tag to be voted upon: https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating Source and binary files: http://people.apache.org/~florianh/jspwiki-2.9.0-incubating/ Checksums: JSPWiki-2.9.0-incubating-src.zip MD5:287e75857b03b41dca769211591c6144 SHA1: 74b24e526177b7ddf5394b4b96b67bb9081628a4 SHA512: 9a080ed994e4308e4ff6386f6e5e88e42d27fc8a8abe37d2874d3c8477fe097037017fffdd03430cdb0ca7a73efba91bf58e70c1943e08c9565170809daa953a JSPWiki-2.9.0-incubating-bin.zip MD5:7e774dc46c112ca895aad60fb607dc60 SHA1: e529eb02d13f4061534d85dd0e78d67c5dfe29a5 SHA512: 575eae72390178005bf7cf57332af9a1da85515d6fc10cf9c8b3548f50743c0e57c0c6f46bc99b70cd1328ef083fb4a4fe9f3867e9ec7c7e4a640b845a2e2ee4 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS For convenience, this directory includes a binary distribution and a RAT report on the cited tag. You can manually generate the RAT report from a clean source by running the rat-report Ant target. Please vote: [ ] +1 approve, release Apache JSPWiki 2.9.0-incubating [ ] +0 no opinion [ ] -1 disapprove (and giving a reason) The vote will be open for at least 72 hours. Best regards Florian Holeczek [1] http://markmail.org/message/gksvnjnru2nhhenf [2] http://markmail.org/message/mht24dwvpmm7xgft - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Volunteering as JSPWiki Mentor - WAS Re: JSPWiki status (Was: jspwiki)
Hi folks, I actually wanted to go emeritus but I'm a f** idiot and therefore would like to help here and volunteer as JSPWiki Mentor ... :-) I'm a bit familiar with JSPWiki since a maintain a JSPWiki On A Stick distribution and we use JSPWiki in my company on a daily base. So I have a personal interest to see the project leaving the incubator. What formal steps are required? Thanks in advance Siegfried Goeschl PS: Please note that over the weekend I'm retiring from most of my other Apache projects roles officially so don't get confused On 13.10.12 17:34, Craig L Russell wrote: On Oct 13, 2012, at 8:19 AM, Craig L Russell wrote: Hi Jukka, On Oct 13, 2012, at 7:49 AM, Jukka Zitting wrote: Hi, On Tue, Oct 9, 2012 at 1:05 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: JSPWiki has been troubled for quite some time. Following up on this and since JSPWiki is by far our oldest podling, I felt it appropriate to summarize its status and outlook from the IPMC perspective in this months board report. Here's my summary: JSPWiki is our oldest podling with over five years in the Incubator. Activity in JSPWiki was very low for a few years and they've yet to create their first Apache release. Earlier this year they discussed leaving the Incubator and the ASF since they clearly weren't making much progress. That discussion led to some revival of activity and the decision to continue in the Incubator. Unfortunately the podling no longer has enough active mentors, which has led to some trouble with premature attempts at cutting releases or graduating. Despite these troubles the podling is making progress, and with sufficient help from the IPMC they might well become ready to graduate within a few quarters. JSPWiki committers/mentors, does this sound like an accurate summary? Sounds fair enough. I'm still actively mentoring the project but could it use some more mentors. Correction: It could use some more mentors. The project is in the middle of cutting their first release, and we all know that the first time is the hardest. The biggest issue regarding the release was the decision to *not* release the 3.0 code base that had been the focus of previous efforts. If everyone stays focused, I believe that the project can graduate within a few months after release. Craig BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] real-time communications
Hi folks, could you stop believing in a conspiracy taking place at the Apache Isis incubator project where a bunch of Isis member plus a few obscure mentors are trying to subvert the Apache Software Foundation by having a Skype session?! Get real - some of the concerns are justified and well understood but this is it as far as I'm concerned. But if Dan Haywood organizes a Skype meeting to introduce the committers and explains the Isis architectures than this is a good thing and I'm still supporting it. And as mentioned before - feel free to participate at Apache Isis to have your own opinion instead of showing signs of knee-jerk repulsion. Cheers, Siegfried Goeschl Apache Isis Mentor On 11/24/10 9:06 PM, Upayavira wrote: There's something we need to watch out for here about how the incubator works. The incubator is a place for podling members to learn, and learning is something *they* do. Our part is to provide encouragement and guidance as appropriate, and to allow podlings to make mistakes. That is an important part of learning. I sometimes feel we can be a bit to heavy handed on this list. Sure, give folks the benefit of our experience. But there's nothing like someone shouting at you for feeling excluded from a decision to make you realise that that conference call was not a good idea. In the end, the point of judgement is at the point of attempting graduation. Before that, we need to give podlings the space to learn, and that involves giving them the space to push the bounds of our community taboos (realtime comms, svn vs git, etc, etc). That's how folks really learn stuff, not just by being told something again and again. Upayavira On Wed, 24 Nov 2010 13:13 -0500, Noel J. Bergmann...@devtech.com wrote: The premise of this discussion is that running Apache projects are *permitted* to engage in real-time communications, so long as they take due care to avoid community problems of exclusion and closed decision making. Did you see Greg's e-mail? Just bring a summary of discussion points back to the list, along with any recommendations. The list can then sort through it and make decisions. Decisions are not made except on the mailing lists. If it starts to seem that people are being excluded from being an effective part of a decision process, curtail or modify the back-channel communications. We all want strong communities that are inclusive and open. We all recognize that real-time communications pose risks to that. +1 FWIW, ApacheDS and Geronimo had (possibly still have) *very* active IRC channels (logged) where people talked in real-time, just as they might at a Hack-a-Thon. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] real-time communications
Hi folks, could you stop believing in a conspiracy taking place at the Apache Isis incubator project where a bunch of Isis member plus a few obscure mentors are trying to subvert the Apache Software Foundation by having a Skype session?! Get real - some of the concerns are justified and well understood but this is it as far as I'm concerned. But if Dan Haywood organizes a Skype meeting to introduce the committers and explains the Isis architectures than this is a good thing and I'm still supporting it. And as mentioned before - feel free to participate at Apache Isis to have your own opinion instead of showing signs of knee-jerk repulsion. Cheers, Siegfried Goeschl Apache Isis Mentor On 11/24/10 9:06 PM, Upayavira wrote: There's something we need to watch out for here about how the incubator works. The incubator is a place for podling members to learn, and learning is something *they* do. Our part is to provide encouragement and guidance as appropriate, and to allow podlings to make mistakes. That is an important part of learning. I sometimes feel we can be a bit to heavy handed on this list. Sure, give folks the benefit of our experience. But there's nothing like someone shouting at you for feeling excluded from a decision to make you realise that that conference call was not a good idea. In the end, the point of judgement is at the point of attempting graduation. Before that, we need to give podlings the space to learn, and that involves giving them the space to push the bounds of our community taboos (realtime comms, svn vs git, etc, etc). That's how folks really learn stuff, not just by being told something again and again. Upayavira On Wed, 24 Nov 2010 13:13 -0500, Noel J. Bergmann...@devtech.com wrote: The premise of this discussion is that running Apache projects are *permitted* to engage in real-time communications, so long as they take due care to avoid community problems of exclusion and closed decision making. Did you see Greg's e-mail? Just bring a summary of discussion points back to the list, along with any recommendations. The list can then sort through it and make decisions. Decisions are not made except on the mailing lists. If it starts to seem that people are being excluded from being an effective part of a decision process, curtail or modify the back-channel communications. We all want strong communities that are inclusive and open. We all recognize that real-time communications pose risks to that. +1 FWIW, ApacheDS and Geronimo had (possibly still have) *very* active IRC channels (logged) where people talked in real-time, just as they might at a Hack-a-Thon. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Fwd: [ISIS] Re: Conference call
Hi folks, forwarding my comment regarding the Skype discussion on gene...@incubation to keep you in the loop ... :-) Cheers, Siegfried Goeschl Original Message Subject: [ISIS] Re: Conference call Date: Fri, 19 Nov 2010 23:41:01 +0100 From: Siegfried Goeschl siegfried.goes...@it20one.at Reply-To: general@incubator.apache.org, siegfried.goes...@it20one.at Organization: IT20one GmbH To: general@incubator.apache.org Hi folks, open source projects are done by individuals. And individuals like to communicate during long lonely nights in front of the keyboard. And meeting the other ISIS developers is difficult since the are spread around the globe. So if the ISIS developer/users/mentors/community decide to run a regular Skype meeting to meet each other electronically assuming +) that the meeting is announced on the dev list +) that we not exclude any interested party (apart from troll feeding) +) that no official statement/vote is circumvented than I don't see any good reason why someone could complain about it and/or impose rules how to organize such a come together. Speaking as one of the participants +) I was impressed by Dan's energy to organize the meeting +) I was delighted that we were a dozen developers on Skype *) I was glad to answer a few questions about the ASF (despite being seriously distracted by my two daughters on my lap) Cheers, Siegfried Goeschl Apache ISIS Mentor On 11/19/10 10:52 PM, Craig L Russell wrote: On Nov 19, 2010, at 11:04 AM, Greg Stein wrote: A full transcription shouldn't be necessary. I agree. Transcript is too strong for what I think needs to be done, which is... Just bring a summary of discussion points back to the list, along with any recommendations. The list can then sort through it and make decisions. What you said. Not a transcript but a list of topics and discussion points which continue on list. Craig We have off-list discussions all the time (IM, IRC, in-person). We don't transcribe those. We just bring the discussion onto the list for wrapping it up with everybody present. Skype concalls are no different than these other forums. Cheers, -g On Fri, Nov 19, 2010 at 13:18, Craig L Russell craig.russ...@oracle.com wrote: My $0.02: The business of Apache is conducted on email. It's fine to have a periodic conference call among interested project participants, as long as (my list, not normative): no project or community member is excluded (e.g. by posting the call information only to a private list) no decisions are made during the call all topics discussed are subsequently posted via email to the project members Having an audio transcript is interesting but doesn't pass my email test. So I'd have to say that someone needs to transcribe the audio into email. Craig On Nov 19, 2010, at 9:29 AM, James Carman wrote: I don't know about this. Whatever we do has to be trackable and open, so I don't know about this Skype stuff. Requiring folks to watch a video or listen to an audio recording rather than reading a transcript is probably not a good idea. I'm copying the general list to see what others have to say. On Fri, Nov 19, 2010 at 10:20 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Good idea +1 on the Skype monthly meeting. On Fri, Nov 19, 2010 at 11:14 AM, Alexander Krasnukhin the.malk...@gmail.com wrote: At least it makes me feel ISIS is really going somewhere. I don't know how to explain this. E.g. there are some real ALIVE people involved :). Monthly is good. On Fri, Nov 19, 2010 at 12:05 PM, Mike Burton mi...@mycosystems.co.ukwrote: Yes very useful interesting and enjoyable, thanks for organising it. Yes monthly similar would be good. Mike On 19 Nov 2010, at 10:49, Dan Haywood dkhayw...@gmail.com wrote: First off, thanks to all for attending, and I really enjoyed the opportunity. Hope it was useful. It was nice, actually, to read the transcript on the Skype IM call afterwards (I didn't get the oppo to do that while I was demo'ing). Second, my apols that I didn't have the demo working. Of course, after the call finished I figured out the problem in about 2 minutes. At any rate, the details on running the demo for yourselves are on the SmokeTest page on the wiki [1]. Third, per a recording, like Kevin I also recorded the call using CallGraph, though mine seems to have recorded ok. It's about 92Mb, recorded it in stereo, and what Skype did is distribute the voices across the spectrum, which I think is quite nice. Anyway, I've just uploaded it to my dropbox account and I'll post the URL on isis-private. (If you aren't subscribed there, contact me directly). Lastly, it'd be nice to do a similar call like that now and again. We could perhaps set one up every month, attendance purely optional. Thoughts? Cheers Dan [1] https://cwiki.apache.org/ISIS/smoketest.html ~~ On 18/11/2010 20:08, Kevin Meyer - KMZ wrote: Hi Dan, Thanks for organizing the call. I
Re: [IP-CLEARANCE] Bushel Donation to Apache Ant
+1 Siegfried Goeschl On 11/15/10 1:14 PM, Stefan Bodewig wrote: Hi all, the people behind the Bushel project at Google Code[1] which provides limited OSGi support to Apache Ivy want to donate their codebase for integration into Ivy. The code can be found at JIRA issue IVY-1241[2], all three authors (one of them is Ant PMC member Nicolas Lalevée) signed software grants and the Ant PMC voted to accept the donation. The form is already online at http://incubator.apache.org/ip-clearance/bushel.html but I forgot to add it to the index (done now, should become world-visible soonish). 72hrs waiting period for -1s start now. Thanks Stefan [1] http://code.google.com/p/bushel/ [2] https://issues.apache.org/jira/browse/IVY-1241 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Isis
Hi Dan, +1 (non-binding) Cheers, Siegfried Goeschl On 24.08.10 19:12, Dan Haywood wrote: I'd like to formally propose a new project for the incubator, Apache Isis. If accepted, Isis will combine the existing open source Naked Objects framework with a collection of sister projects, providing an extensible Java-based framework for rapidly developing domain-driven applications. I floated the idea of Isis on this mailing list about a month or so ago, and we got some positive feedback and a couple of expressions of interest in contributing. Since then, we've put together a proposal (also copied in below) onto the incubator wiki. The proposal is at: http://wiki.apache.org/incubator/IsisProposal. The current codebase is at: http://nakedobjects.org, with sister projects hosted at: http://starobjects.org We currently have two mentors, but require more, and we still need a champion. I'm hoping that this post will generate some further interest to develop the proposal further. All being well we hope to put this proposal to a vote in a week or two's time. Thanks for reading, looking forward to your feedback. Dan Haywood ~~~ = Isis Proposal = The following presents the proposal for creating a new project within the Apache Software Foundation called Isis. == Abstract == Isis will be an extensible standards-based framework to rapidly develop and enterprise level deploy domain-driven (DDD) applications. == Proposal == The Isis project will bring together a collection of open source projects that collectively support the rapid development of domain-driven applications. The heart of Isis is the Naked Objects Framework, an established open source project that has been around since 2002. In addition, it will incorporate a number of sister projects that build on Naked Objects' pluggable architecture and which extend the reach of Naked Objects in several key areas. In addition, the project will be reorganising the existing projects to logically separate out the components into [[http://docs.jboss.org/weld/reference/1.0.1-Final/en-US/html/|JSR-299]] beans. We believe that the JSR-299 programming model is likely to become widely used for enterprise Java applications; adopting it should make it easier for new contributors to understand how the framework fits together and therefore to develop their own extensions. In turn, we hope this will further extend the reach of the framework to other complementary open source frameworks (either within Apache or outside of it). == Background == Naked Objects is an open source Java framework that was originally developed to explore the idea of enterprise systems that treat the user as a problem solver, not a process follower. Conceived by Richard Pawson, the first version of the framework was written by Robert Matthews (2002). Richard and Rob also wrote a book, Naked Objects (Wiley, 2002), to explain the idea. More generally, Naked Objects is an implementation of the naked objects architectural pattern. In its purest form, all the developer has to do is develop their domain model as pojos; Naked Objects then provides: a object-oriented user interface by rendering those pojos; persistence by extracting the content of the pojos; security by wrapping access to the pojos; remoting by turning local calls into remote ones; and localisation by adapting all the names used in the metamodel. All of this is done reflectively at runtime so that the developer can concentrate on the most important aspect - the application itself. You can think of Naked Objects' OOUI generation as analogous to Hibernate and other ORMs, but rather than reflecting the pojo into the persistence layer, they are reflected into the presentation layer. A number of other open source frameworks cite it as their inspiration, including [[http://jmatter.org|JMatter]], [[http://openxava.org|OpenXava]], and [[http://www.trailsframework.org|Trails]]. Over this time Naked Objects has attracted a fair degree of attention among the early adopter crowd, generally splitting opinion as either a very good idea or a very bad one. A common misconception is that naked objects is only appropriate for simple CRUD based applications. While developing CRUD applications is indeed trivial, an important innovation is that the UI generated by NO also renders the pojo's commands/behaviors (we call them actions). Simply stated: any public method that does not represent a property or collection is rendered so it can be invoked, eg with a button, a menu item or a hyperlink. We characterize entities with such behaviors as behaviorally complete. It's OO as your mother taught it to you. At the same time that we have been developing our ideas on the naked objects, there has been a resurgent interest in object modelling at the enterprise level, specifically as described by Eric Evans' book, [[http://domaindrivendesign.org/books|Domain Driven Design]]. Recognizing that there's a lot
Re: Future of RAT
Hi Jochen, not sure if Commons is the right place sine RAT has a very spezialized scope or to state it differently I would not look for RAT in Commons. What about Maven TLP? Cheers, Siegfried Goeschl On 10.08.10 12:40, Jochen Wiedmann wrote: Hi, having just published a release of Apache RAT with the -incubating label, I'd though it is time to discuss the future of RAT. RAT is an incubator project since 18 months. It is not an overly busy project: The occasional feature request, which is handled, a bug report from time to time, and so on. OTOH, it definitely lives: People are interested and, what's more, it is very widely adopted by all Java projects I am aware of and perhaps even by a few non-Java projects. If there will ever be a migration to a new license like ASL 3 or a another change of the header policy, then RAT will likely play a very important part in the process. Even now, the RAT report is carefully studied as part of every release vote. (Funnily, RAT is very rarely used to inspect itself, because so far I didn't find a possibility to run a previous version of the RAT Maven plugin as part of a build. In fact, RAT is the only project I am aware of, which doesn't publish a RAT report. :-) IMO, RAT could very well leave the incubator. It's 10 or so committers [1] are all part of an organization called ASF since years, so you might question the diversity, but I don't believe anyone will actually do that. ;-) The source code has been developed under ASL and by Apache committers right from the start, so licensing was never an issue. The question is: What's the target? RAT is way too small for an independent project. And I cannot imagine anybody of the current committers writing board reports. To me, a Rat TLP is no option. So we have the second possibility: Put it under the hat of another TLP. The only one that comes to my mind is the Apache Commons project. But Commons would be an excellent choice: Most, or even all of the RAT committers are Commons committers as well. Commons was one of the drivers for integration of RAT into every release build. I admit that I wouldn't like to change the package name or the Maven group ID again, but either Commons developers could accept that exception from the rule or I'd force myself to do the required changes. WDYT? Jochen [1] http://incubator.apache.org/rat/team-list.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANN] Apache Shiro 1.0.0-incubating Released!
Hi folks, congratulation for getting the release out of the door ... :-) ... and shiro folks (aka JSecurity) did an excellent job. Regarding the no-frills step-by-step, no room-for-error release +) it is difficult to write +) different projects have different tools to release (manual, Ant, Maven) making the stuff even more difficult Maybe more stuff can be done to streamline your release process using M2 - maybe I can lend you a hand Cheers, Siegfried Goeschl On 01.06.10 22:26, Les Hazlewood wrote: The download page links to reposity.apache.org. However repository.apache.org is not to be used for direct publication to end users, it is for publishing to the main maven repo. This wasn't clear on the apache infrastructure page - it states that repository.apache.org is part of the distribution infrastructure. Now that we've been notified that this is not the case, we'll fix it as soon as possible. Thanks! Also, the downloads page does not have a link to the KEYS file. Nor does it have any documentation on how to use the sigs and hashes. We'll fix that. The downloads page should only link to the ASF mirrors, see for example: http://incubator.apache.org/photark/photark-downloads.html Also, there is no DISCLAIMER in any of the archive files. AIUI, Incubator releases MUST contain a disclaimer: The branding link only specifies that podling websites must display that disclaimer. That exact disclaimer is the very first paragraph on the download page. AIUI, there is no mandate that a DISCLAIMER file must be included in the actual packaged distribution. Otherwise we assume the release would have been voted against. On a side note, we're doing our best to adhere to all requirements, and we're happy to do so. But it has been *incredibly* time consuming and frustrating to try to interpret what should be step-by-step courses of action to adhere to these requirements. Why isn't there a no-frills step-by-step, no room-for-error release checklist that podlings can follow to guarantee that all required criteria are met? It seems like such a checklist would be of the highest priority for the Incubator to ensure that personal interpretation is minimized or eliminated from the release process. This release management page [1] is incredibly long and full of policy and reasoning, which is all well and good if one wants to understand *why* these policies exist, but podlings really need a step-by-step *how-to* guide that references the 'why' document so we can service our communities as efficiently as possible. The 'why' guide is fantastic to read at our leisure, but the 'how' document would be far more useful to podlings when release time comes. My .02, Les [1] http://incubator.apache.org/guides/releasemanagement.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Starting a new incubation
Hi Alexander, could you provide some more technical background information +) how does it compare to RMI, JSON or Hessian (http://hessian.caucho.com/) Siegfried Goeschl Alexander Veit wrote: Dear all, I would like to start an incubator project at the Apache Software Foundation with a Java library (let's call it Jaffre) I've written. Jaffre is a lightweight RPC library for the Java platform. It is designed to be simple, extensible, robust, and efficient with no required dependencies other than a JRE. Currently it supports transport over insecure or encrypted TCP channels. It supports sessions and can be customized so that calls are performed as a particular session dependent subject. Implementing a service is as simple as defining a service interface, implementing it in a pojo, and registering that pojo as a service endpoint. The service is exposed to clients through one ore more connectors. Clients call the service through proxy classes. As far as I understood the Apache guides and this mailing list, the first requirement to start an incubation is to find a champion. If this is correct, I would herewith like to announce the search for a champion. If I'm wrong, I would appreciate any advice how to proceed. Regards, Alexander Veit - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Champion needed for new workflow project proposal
Hi Sasa, the very first question is - why are moving from ObjectWeb since it is well-known and respected community? Cheers, Siegfried Goeschl sasaboy wrote: Hi, some weeks ago, I've posted a question on this mailing list on how to start new project on Apache. After reading posts on mailing lists, apache documentation, etc. ... it seems first we need a champion for the project proposal. Once again about the project: Enhydra Shark workflow engine is a project currently hosted on ObjectWeb (http://shark.objectweb.org/) It is the most popular open-source java workflow engine completely based on WfMC standards. It uses XPDL1.0 as its native workflow process definition language. It can be embedded into other Java applications (Swing, Console, ...) or can be used as a server through WebService, EJB, CORBA, ... Shark's modular, plug-in architecture makes shark suitable for integration into different kind of projects. It is a mature project started 5years ago, has a significant community and more than 10 downloads on ObjectWeb and almost 1 posts on mailing list. It is widely used all around the world in production, typically integrated into different kind of applications, from DocumentManagement and government applications up to applications for special purposes like bank services, HR, Help desk, ... and in many, many others If you would be willing to act as a champion on Shark's behalf, please let us know. Thanks in advance, Sasa. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Champion needed for new workflow project proposal
Hi Sasa, +) sorry but I could find no link to the proposal - could you repost the link? +) I worked for Together Teamlösungen many moons ago so I'm aware of Enhydra Shark (but no affiliation for the time being) So without knowing the proposal I think it is a successful open source project but moving to LGPL for a mature project is a serious issue ... Cheers, Siegfried Goeschl sasaboy wrote: Hi, well, we already wrote this in proposal, but here it is: * The legal umbrella. There are no outstanding legal issues with Shark, but the protection that Apache affords is valuable for Shark developers and users. * Resolve current potential licensing issues that are addressed in the Apache 2.0 license, but not in the LGPL license. * Increase public awareness of Shark and of the application of Apache licensing. * Help to attract clients who would feel more comfortable with the licensing coming through a well known and established organization like Apache * To get more people involved in the further development of software Greetings, Sasa. Siegfried Goeschl wrote: Hi Sasa, the very first question is - why are moving from ObjectWeb since it is well-known and respected community? Cheers, Siegfried Goeschl sasaboy wrote: Hi, some weeks ago, I've posted a question on this mailing list on how to start new project on Apache. After reading posts on mailing lists, apache documentation, etc. ... it seems first we need a champion for the project proposal. Once again about the project: Enhydra Shark workflow engine is a project currently hosted on ObjectWeb (http://shark.objectweb.org/) It is the most popular open-source java workflow engine completely based on WfMC standards. It uses XPDL1.0 as its native workflow process definition language. It can be embedded into other Java applications (Swing, Console, ...) or can be used as a server through WebService, EJB, CORBA, ... Shark's modular, plug-in architecture makes shark suitable for integration into different kind of projects. It is a mature project started 5years ago, has a significant community and more than 10 downloads on ObjectWeb and almost 1 posts on mailing list. It is widely used all around the world in production, typically integrated into different kind of applications, from DocumentManagement and government applications up to applications for special purposes like bank services, HR, Help desk, ... and in many, many others If you would be willing to act as a champion on Shark's behalf, please let us know. Thanks in advance, Sasa. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Champion needed for new workflow project proposal
Hi Sasa, I'm following apache.incubator not very closely but looking at http://incubator.apache.org/guides/proposal.html#template-ip; you need a CLA for all contributions (and probable patches). And this seems difficult for a mature project where many people contributed stuff under LGPL - but a lot of folks here are more fluent with the intellectual property legalese. Cheers, Siegfried Goeschl sasaboy wrote: Hi, ObjectWeb allows Apache licensed projects but one of our reasons is also to be recognized as Apache project, which will of course provide us with much more visibility than beeing ObjectWeb project :-) plus to get more developers, ideas, community, etc I didn't provide a link for the proposal yet since I understood that first I need a champion to agree on a proposal etc... Moving from LGPL to Apache shouldn't be so hard since for the beginning we only want to move the core of the engine to Apache ... Greetings, Sasa. sasaboy wrote: Hi, some weeks ago, I've posted a question on this mailing list on how to start new project on Apache. After reading posts on mailing lists, apache documentation, etc. ... it seems first we need a champion for the project proposal. Once again about the project: Enhydra Shark workflow engine is a project currently hosted on ObjectWeb (http://shark.objectweb.org/) It is the most popular open-source java workflow engine completely based on WfMC standards. It uses XPDL1.0 as its native workflow process definition language. It can be embedded into other Java applications (Swing, Console, ...) or can be used as a server through WebService, EJB, CORBA, ... Shark's modular, plug-in architecture makes shark suitable for integration into different kind of projects. It is a mature project started 5years ago, has a significant community and more than 10 downloads on ObjectWeb and almost 1 posts on mailing list. It is widely used all around the world in production, typically integrated into different kind of applications, from DocumentManagement and government applications up to applications for special purposes like bank services, HR, Help desk, ... and in many, many others If you would be willing to act as a champion on Shark's behalf, please let us know. Thanks in advance, Sasa. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Some advice needed on JSPWiki package names
Hi Janne, one of my favorite quotes - The problem with quick and dirty is that dirty remains long after quick has been forgotten +) when do you expect a JSPWiki 3.0 release to hit the public - I think it will be a while ... +) even when JSPWiki 3.0 is available only a few people will use it in production - and they will experience a lot of more problem than this Jasper bug looking at the current refactoring +) Jetty on JDK 1.5 onwards is probably not affected since it does not use Jasper out-of-the-box +) following my line of work with Wiki On A Stick - provide a ready to use distribution in addition to a plain war file so a lot of people won't be aware of the problem So I think +) it's a funny and annoying problem +) stay clear of any dirty hack +) comment this issue and the workarounds Cheers, Siegfried Goeschl PS: I'm not an incubator PMC Janne Jalkanen wrote: Hi ho folks! We were preparing for a massive rename from our old jspwiki name space to the org.apache.jspwiki.* -package to prepare for our first Apache release when we hit a major snag. Turns out that Jasper JSP compiler has a bug in it, and it thinks all classes with their FQN starting with org.apache.jsp are it's own, instead of org.apache.jsp. (note the trailing period). We are tracking this issue at https://issues.apache.org/jira/browse/JSPWIKI-465 Now, Jasper has this fixed in the trunk, but since it's used rather widely in other servlet containers, it means that very few servlet containers will be able to run JSPWiki for quite a while. We've got some fairly hackish ways around this (which cause pain), so the question to Incubator folks is - can we use a different package name than org.apache.jspwiki for our project, or does it require a full rename of the project itself? For example, org.apache.x.jspwiki where x can range from being a literal x to something else? We'd hate to lose the JSPWiki brand (due to four missing characters in an another project!) because we've existed for over seven years and have an established name. In addition, figuring out a new name for a project is always a real pain... Any ideas/advice from more experienced people? Any other options than those listed at JSPWIKI-465? /Janne - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Click for Incubation
Hi folks, Had a look at Click and really like it ... :-) .. therefore [X] +1 Accept Click for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason: If you need to tackle a Maven build I can lend a hand ... :-) Cheers, Siegfried Goeschl Henning Schmiedehausen wrote: This vote will run until Monday, July 21st, 2008. [ ] +1 Accept Click for incubation [ ] 0 Don't care [ ] -1 Reject for the following reason: = Click Proposal = This proposal specifies the migration of Click web application framework to the Apache Software Foundation as a Top Level Project. http://click.sourceforge.net/ == Rationale == Click is a modern J2EE web application framework released under the Apache License 2.0. It takes a component and page orientated approach to web applications with its main goals being ease of use and low barrier to entry. A major difference between Click and other component oriented frameworks, is that Click is stateless by design, although stateful pages are supported. It is an optimal framework, always trading off bloating features to its main goals of simplicity. Another important focus of the project has been to provide high quality documentation and examples to get people started as quickly as possible. We see Click becoming an Apache project as a logical step in its evolution. Becoming part of the Apache community will increase visibility and expose the framework to a larger community of developers. === Current Status === == Meritocracy == Click was developed by Malcolm Edgar in 2003 publicly released in March 2005. Since then there have been contributions from a number of developers across the world. New contributors are encouraged to provide patches, and later commit privileges are assigned to them. In 2008 Bob Schellink joined Malcolm Edgar as a joint lead on the project after contributing to the project for a number of years. == Community == Click is a small but growing community of users and developers. Its two mailing lists receive around 200 messages per month. == Core Developers == * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe == Alignment == Click has already built up relationships with existing Apache projects especially Velocity and Cayenne. Using Velocity as its default rendering engine, Click has formed a close relationship with the Velocity community. Click also supports good integration with the Apache Cayenne ORM framework. == Known Risks == * Orphaned Software: Click has a healthy community of users and developers and has a very low risk of becoming orphaned. Experience With Open Source: Click was started as an open source project in 2005 and has remained so for 3 years. * Homogeneous Developers: The community is very diverse with users and developers from all over the world. * Reliance on salaried developers: None of the Click developers are compensated for their contributions. It is a complete voluntary project. * Relationships with Other Apache Products: As mentioned in the Alignment section, Click has formed close relationships with Velocity and Cayenne. Other Apache products used include commons-* and log4j. * An Excessive Fascination with the Apache Brand: Although it is true that the Apache Brand will increase visibility of the framework, we are more interested in building stronger relationships and influence Apache projects such as Velocity. == Scope of the project == Currently Click consists of the following parts: the core framework, an extras package for non core controls, an examples project and a quick start project. There is also an Eclipse plugin called ClickIDE. == Initial Source == Click sources is available from http://sourceforge.net/projects/click == External Dependencies == There are some concerns over incompatible licensed libraries Click depends on. * calendar.js is released under a LGPL licensed library from http://www.dynarch.com/projects/calendar/ * Hibernate is released under a LGPL licensed library from http://www.hibernate.org/ * HSQLDB is released under the license specified here: http://hsqldb.org/web/hsqlLicense.html == Required Resources == == Mailing lists == Create new mailing lists * click-dev * click-private == Subversion Directory == Migrate the current subversion code from sourceforge to Apache * https://svn.apache.org/repos/asf/incubator/click == Issue Tracking == * Need to create a new JIRA project called CLICK for the Click framework * Migrate the current JIRA issue tracker from http://www.avoka.com/jira/ == Other Resources == Need to create a new Confluence Wiki * CLICK == Initial Committers == The initial committers for the project should include: * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe * Henning Schmiedehausen * Will Glass-Husain * Ted Husted * Andrus Adamchik == Sponsors == === Champion === * Henning
Re: [PROPOSAL] Click
Cool, page rendering based on Velocity ... :-) ... good to have a break from JSPs Siegfried Goeschl Henning Schmiedehausen wrote: Please see also http://wiki.apache.org/incubator/ClickProposal Comments until July 9th, if nothing blocking comes up, I'll CfV on July 10th. --- cut --- = Click Proposal = This proposal specifies the migration of Click web application framework to the Apache Software Foundation as a Top Level Project. http://click.sourceforge.net/ == Rationale == Click is a modern J2EE web application framework released under the Apache License 2.0. It takes a component and page orientated approach to web applications with its main goals being ease of use and low barrier to entry. A major difference between Click and other component oriented frameworks, is that Click is stateless by design, although stateful pages are supported. It is an optimal framework, always trading off bloating features to its main goals of simplicity. Another important focus of the project has been to provide high quality documentation and examples to get people started as quickly as possible. We see Click becoming an Apache project as a logical step in its evolution. Becoming part of the Apache community will increase visibility and expose the framework to a larger community of developers. === Current Status === == Meritocracy == Click was developed by Malcolm Edgar in 2003 publicly released in March 2005. Since then there have been contributions from a number of developers across the world. New contributors are encouraged to provide patches, and later commit privileges are assigned to them. In 2008 Bob Schellink joined Malcolm Edgar as a joint lead on the project after contributing to the project for a number of years. == Community == Click is a small but growing community of users and developers. Its two mailing lists receive around 200 messages per month. == Core Developers == * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe == Alignment == Click has already built up relationships with existing Apache projects especially Velocity and Cayenne. Using Velocity as its default rendering engine, Click has formed a close relationship with the Velocity community. Click also supports good integration with the Apache Cayenne ORM framework. == Known Risks == * Orphaned Software: Click has a healthy community of users and developers and has a very low risk of becoming orphaned. Experience With Open Source: Click was started as an open source project in 2005 and has remained so for 3 years. * Homogeneous Developers: The community is very diverse with users and developers from all over the world. * Reliance on salaried developers: None of the Click developers are compensated for their contributions. It is a complete voluntary project. * Relationships with Other Apache Products: As mentioned in the Alignment section, Click has formed close relationships with Velocity and Cayenne. Other Apache products used include commons-* and log4j. * An Excessive Fascination with the Apache Brand: Although it is true that the Apache Brand will increase visibility of the framework, we are more interested in building stronger relationships and influence Apache projects such as Velocity. == Scope of the project == Currently Click consists of the following parts: the core framework, an extras package for non core controls, an examples project and a quick start project. There is also an Eclipse plugin called ClickIDE. == Initial Source == Click sources is available from http://sourceforge.net/projects/click == External Dependencies == There are some concerns over incompatible licensed libraries Click depends on. * calendar.js is released under a LGPL licensed library from http://www.dynarch.com/projects/calendar/ * Hibernate is released under a LGPL licensed library from http://www.hibernate.org/ * HSQLDB is released under the license specified here: http://hsqldb.org/web/hsqlLicense.html == Required Resources == == Mailing lists == Create new mailing lists * click-private * click-dev * click-user == Subversion Directory == Migrate the current subversion code from sourceforge to Apache * https://svn.apache.org/repos/asf/incubator/click == Issue Tracking == * Need to create a new JIRA project called CLICK for the Click framework * Migrate the current JIRA issue tracker from http://www.avoka.com/jira/ == Other Resources == Need to create a new Confluence Wiki * CLICK == Initial Committers == The initial committers for the project should include: * Malcolm Edgar * Bob Schellink * Naoki Takezoe * Ahmed Mohombe * Henning Schmiedehausen * Will Glass-Husain * Ted Husted == Sponsors == === Champion === * Henning Schmiedehausen === Nominated Mentors === * Will Glass-Husain * Ted Husted === Sponsoring Entity === * Velocity --- cut
[Fwd: [jsecurity-dev] Looking around at JSecurity ....]
FYI Original Message Subject:[jsecurity-dev] Looking around at JSecurity Date: Thu, 08 May 2008 21:14:24 +0200 From: Siegfried Goeschl [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED], general@incubator.apache.org Hi folks, a few thoughts along the line while looking at the project 1) would it be possible to integrate non-Java application for SSO, e.g. using agents communicating to a central server or is this not the scope of the project (i.e. Java only) - might be a stupid question but I miss the big picture here 2) you expose strong cryptography based on Blowfish - please note that in Apache land this requires an ECCN code (for the brave and fearless see http://www.apache.org/dev/crypto.html) - you might consider exposing weak cryptography (up to 56 bit) to avoid the legal work ... :) 3) You are using retroweaver to support JDK 1.4 - are there two deliverables (one for 1.4 and 1.5) or only the backported one? Cheers, Siegfried Goeschl - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JSecurity Champion Recruitment
Hi Les, quick response before hitting instead of missing the bed +) I'm in the lucky position to toy around with SSO the next few weeks so I have a look a JSecurity before fighting JOSSO, CAS and openSSO +) The project looks good and I look forward to evaluate it +) Depending on the outcome of the evaluation (read if I can integrate it into my current project) I might be able to join your community ... :-) Cheers, Siegfried Goeschl Les Hazlewood wrote: Hello all, I've been a lurker for a while, attempting to get an overall feel for the incubator process, and this is my first foray into (hopefully) making things a reality for our project, JSecurity. JSecurity (http://www.jsecurity.org/) is a powerful and flexible open-source Java security framework that cleanly handles authentication, authorization, enterprise session management and cryptography. Our mission is to provide the most robust and comprehensive Java security framework available while also being very easy to understand and extremely simple to use. The JSecurity development team has discussed at length about what it means to become an Apache project and what it would mean for our team and the future direction of the project. After having read the incubator processes and policies at length, we are now prepared to engage with the ASF. This is our formal attempt at recruiting a Champion in the hopes of acquiring guidance into the proposal phase, understanding the ASF in more detail and maybe eventually becoming a podling. Mission Statement project origins: http://www.jsecurity.org/about High level features overview: http://www.jsecurity.org/features Community support - forums, mailing lists, jira: http://www.jsecurity.org/support JSecurity is Apache 2.0 licensed. Thank you for any feedback and recommendations. We look forward to your responses. Best regards, Les Hazlewood JSecurity lead project founder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] PDFBox proposal
Hi folks, for creating PDF you have many options and I'm not sure if creating PDF using a programmatic API is the best appraoch. But where PDFBox really shines is the fact that you can extract the textual content of a PDF document thereby making it accessible for fulltext search within the WIKI. Therefore I used a combination of PDFBox and iText for a PDF handling service Cheers, Siegfried Goeschl Janne Jalkanen wrote: How? Just curious. We don't have built-in PDF generation from pages, which is one of the more requested features. Apparently many companies like the ability to create documentation on a wiki, and then dumping it to a PDF for shipping. /Janne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Request for Comments - Pnuts as Incubator Project?!]
Hi Paul, IMO opinion the core language is pretty much stable - supports compilation to Java classes, JSR-223 (Java 6.0) runs with security manager and JWS, has good documentation, provides system for extension modules ... I see improvements for the optional pnuts modules, e.g. the optional modules I used where not feature complete but this is expected. Cheers, Siegfried Gooeschl Paul Fremantle wrote: I don't know enough about the pnuts community to know if it will make a good incubation project, but thanks for bringing it to my attention - looks like a neat language! And if it does come here I'll certainly join the discussions. One question I have is how much of pnuts is done and how much is still to do? That's always an interesting aspect for a incubator project. Paul On 5/10/07, Niclas Hedhman [EMAIL PROTECTED] wrote: On 5/9/07, Siegfried Goeschl [EMAIL PROTECTED] wrote: Your feedback would help me a lot convincing the pnuts community to move over to Apache. I couldn't care less, but if there are genuine interest from Apache folks, I'll support the idea of putting it into incubation. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Request for Comments - Pnuts as Incubator Project?!]
Hi Eelco, thanks for encouragement ... :-) Cheers, Siegfried Goeschl Eelco Hillenius wrote: Big +1 for me. It's a very useful scripting language that is easy to extend, easy to integrate with Java, easy to debug and is very fast. I've used it in two real-life projects so (though for simple things) and it always worked great for me. Eelco On 5/9/07, Siegfried Goeschl [EMAIL PROTECTED] wrote: As Yoav Shapira pointed out this is the right place to go ... :-) Siegfried Goeschl Original Message Subject: Request for Comments - Pnuts as Incubator Project?! Date: Wed, 09 May 2007 11:55:06 +0200 From: Siegfried Goeschl [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Organization: IT20one GmbH To: [EMAIL PROTECTED] Hi folks, since I'm basically an ASF newbie I would like to ask for some feedback if you would think pnuts as suitable candidate for an incubator project. Your feedback would help me a lot convincing the pnuts community to move over to Apache. Cheers, Siegfried Goeschl What is pnuts? === pnuts is a JVM based scripting language comparable to Groovy with excellent documentation, a much too small community, absolutely no hype and mainly written by Toyokazu Tomatsu. A quick overview of the language can be found here http://pnuts.org/snapshot/latest/doc/faq.html https://pnuts.dev.java.net/files/documents/153/57430/pnuts-1.2.1-doc.zip http://pnuts.org/articles/pnutsQuickstart.html http://pnuts.org/articles/pnutsHighlights.html https://opensvn.csie.org/traccgi/Pnuts/wiki/PnutsInThePress Why I like pnuts ... === I have a special interest in JVM based scripting languages since the have two very useful aspects. You can write a script using your favourite libraries such as commons-email or Velocity and you can embedd such a scripting language into your java application. So over the years I worked with many JVM-based scripting languages such as JavaScript, Bean Shell, Groovy, JACL and of course pnuts. IMO pnuts makes a good compromise regarding scripting power, extensibility, performance, memory consumption and user experience. And it has an awesome documentation and mature implementation ... What can be improved ... === +) pnuts is perfectly hidden within java.net +) do some better marketing to make pnuts more visible in the public +) expand the community and developer base +) of course changing the licence from SPL to Apache - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Fwd: Request for Comments - Pnuts as Incubator Project?!]
As Yoav Shapira pointed out this is the right place to go ... :-) Siegfried Goeschl Original Message Subject: Request for Comments - Pnuts as Incubator Project?! Date: Wed, 09 May 2007 11:55:06 +0200 From: Siegfried Goeschl [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Organization: IT20one GmbH To: [EMAIL PROTECTED] Hi folks, since I'm basically an ASF newbie I would like to ask for some feedback if you would think pnuts as suitable candidate for an incubator project. Your feedback would help me a lot convincing the pnuts community to move over to Apache. Cheers, Siegfried Goeschl What is pnuts? === pnuts is a JVM based scripting language comparable to Groovy with excellent documentation, a much too small community, absolutely no hype and mainly written by Toyokazu Tomatsu. A quick overview of the language can be found here http://pnuts.org/snapshot/latest/doc/faq.html https://pnuts.dev.java.net/files/documents/153/57430/pnuts-1.2.1-doc.zip http://pnuts.org/articles/pnutsQuickstart.html http://pnuts.org/articles/pnutsHighlights.html https://opensvn.csie.org/traccgi/Pnuts/wiki/PnutsInThePress Why I like pnuts ... === I have a special interest in JVM based scripting languages since the have two very useful aspects. You can write a script using your favourite libraries such as commons-email or Velocity and you can embedd such a scripting language into your java application. So over the years I worked with many JVM-based scripting languages such as JavaScript, Bean Shell, Groovy, JACL and of course pnuts. IMO pnuts makes a good compromise regarding scripting power, extensibility, performance, memory consumption and user experience. And it has an awesome documentation and mature implementation ... What can be improved ... === +) pnuts is perfectly hidden within java.net +) do some better marketing to make pnuts more visible in the public +) expand the community and developer base +) of course changing the licence from SPL to Apache - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
