Re: The future of java-icalendar
On Sun, 2002-01-27 at 23:17, Peter Donald wrote: Hi, On Mon, 21 Jan 2002 07:38, Jeff Prickett wrote: I would like to name the project Periodicity. I would like to utilize the EJB architecture and support most of the major EJB containers starting with JBoss of course. I would like to use JUnit to write Unit Tests for the project I would highly recomend you have a look at XDoclet stuff (on sourceforge) aswell ... (Im just reading through the docs and it is brilliant). I have begun writing the project guidelines and have started building the project website. I have rewritten the API to take full advantage of Java 2 Enterprise Edition. I have saved the email addresses of most of the people who have emailed me regarding the icalendar project in the last year. I have begun personally responding to email inquiries about icalendar. My questions are this: Would ASF accept my sincere apology and work with me to help make the project viable? I doubt the ASF holds grudges ;) and a fully operationaly ICalendar compliant product would be a very good addition to Jakarta. The problem mainly is that you don't have a community about your product. While it used to be a product at java apache you would effectively be proposing a new project. And accoridng to the guidelines at http://jakarta.apache.org/site/newproject.html you don't yet satisfy them. So what I would suggest you do is propose/add the product to the commons sandbox. When it becomes stable enough you can propose it be moved to commons proper and when you get a large enough community about it you can propose it to be a top-level jakarta project. Would periodicity be an acceptable name for the project? It's up to you but I like it ;) Can I base the iCalendar objects on EJB technologies? You *can* but I suspect it will make your job of attracting a community harder. It would be much more widely useful if it did not require EJB technologies and I suspect iy would thus be much easier to attract more developers. If at all possible I would suggest making it run in non-EJB environments but thats completely up to you ;) +1, proper encapsulation should include EJB functionality for those who desire it while not requiring it for those who do not. There is also a matter of licensing involved there. Is the IBM Public License compatible with Apache license? (Can I use Junit for testing?). Yep - this is fine and plenty of other projects use Junit at Apache (Just remember to put the license into the CVS). Anyways good luck - I hope you decide to stay and hopefully it will get enough exposure and a big enough community to get it off and going ;) -- Cheers, Pete *--* | Computers are useless. They can only give you | |answers. - Pablo Picasso | *--* -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- www.superlinksoftware.com www.sourceforge.net/projects/poi - port of Excel format to java http://developer.java.sun.com/developer/bugParade/bugs/4487555.html - fix java generics! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: The future of java-icalendar
On 1/28/02 6:37 AM, Andrew C. Oliver [EMAIL PROTECTED] wrote: On Sun, 2002-01-27 at 23:17, Peter Donald wrote: Hi, On Mon, 21 Jan 2002 07:38, Jeff Prickett wrote: Can I base the iCalendar objects on EJB technologies? You *can* but I suspect it will make your job of attracting a community harder. It would be much more widely useful if it did not require EJB technologies and I suspect iy would thus be much easier to attract more developers. If at all possible I would suggest making it run in non-EJB environments but thats completely up to you ;) +1, proper encapsulation should include EJB functionality for those who desire it while not requiring it for those who do not. There is also a matter of licensing involved there. What matter of licensing would that be? I can't imagine that you need to talk to sun to *use* EJBs -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Be a giant. Take giant steps. Do giant things... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: The future of java-icalendar
Peter Donald wrote: Hi, On Mon, 21 Jan 2002 07:38, Jeff Prickett wrote: I would like to name the project Periodicity. I would like to utilize the EJB architecture and support most of the major EJB containers starting with JBoss of course. I would like to use JUnit to write Unit Tests for the project I would highly recomend you have a look at XDoclet stuff (on sourceforge) aswell ... (Im just reading through the docs and it is brilliant). I have begun writing the project guidelines and have started building the project website. I have rewritten the API to take full advantage of Java 2 Enterprise Edition. I have saved the email addresses of most of the people who have emailed me regarding the icalendar project in the last year. I have begun personally responding to email inquiries about icalendar. My questions are this: Would ASF accept my sincere apology and work with me to help make the project viable? I doubt the ASF holds grudges ;) and a fully operationaly ICalendar compliant product would be a very good addition to Jakarta. The problem mainly is that you don't have a community about your product. While it used to be a product at java apache you would effectively be proposing a new project. And accoridng to the guidelines at When I quit programming at ASF it wasnt really a decision I made to quit. It was more like things kept keeping me from contributing. After a while I became to self-consicous to try and come back. Then ASF servers were hacked and I could not even logon as all passwords had been changed. http://jakarta.apache.org/site/newproject.html you don't yet satisfy them. So what I would suggest you do is propose/add the product to the commons sandbox. When it becomes stable enough you can propose it be moved to commons proper and when you get a large enough community about it you can propose it to be a top-level jakarta project. I will formally propose that they be added today, later in the day. Would periodicity be an acceptable name for the project? It's up to you but I like it ;) Can I base the iCalendar objects on EJB technologies? You *can* but I suspect it will make your job of attracting a community harder. It would be much more widely useful if it did not require EJB technologies and I suspect iy would thus be much easier to attract more developers. If at all possible I would suggest making it run in non-EJB environments but thats completely up to you ;) I had a hard time deciding this myself and am not sure that EJB is the way to go, but part of me wants to push the envelope with this. It goes back to a lesson I learned about a year and a half ago when I was still working. Do not be ignorant of industry trends. One of my reasons for wanting to use EJB is that I dont want people to outgrow the product. I have gotten a wide range of responses from all types of people from college students all over the world to IT professionals at large corporations and everywhere in between. If I chose EJB I am probably going to spend a lot of time explaining it to newcomers, it is a lot more complicated than non-EJB, but it will be based on what is fast becoming the industry standard for server side components. To be honest I am not sure, but I might try EJB if no one bites than I might have to rethink my strategy. Is the IBM Public License compatible with Apache license? (Can I use Junit for testing?). Yep - this is fine and plenty of other projects use Junit at Apache (Just remember to put the license into the CVS). Anyways good luck - I hope you decide to stay and hopefully it will get enough exposure and a big enough community to get it off and going ;) -- Cheers, Pete *--* | Computers are useless. They can only give you | |answers. - Pablo Picasso | *--* -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: Thanks for the words of encouragement. Back to programming for me. Sincerely, Jeff Prickett -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: The future of java-icalendar
J2EE stuff has a different license than the JDK. I've been told conflicting things about what you can distribute. Most of it sounds bogus. I've read the license but you can read it a few different ways. Basically I would think provided you do not extend the APIs (not meaning the keyword extends...) you should be fine as long as you don't distribute any components of the J2EE. Thats AFAIK. -Andy On Mon, 2002-01-28 at 06:49, Geir Magnusson Jr. wrote: On 1/28/02 6:37 AM, Andrew C. Oliver [EMAIL PROTECTED] wrote: On Sun, 2002-01-27 at 23:17, Peter Donald wrote: Hi, On Mon, 21 Jan 2002 07:38, Jeff Prickett wrote: Can I base the iCalendar objects on EJB technologies? You *can* but I suspect it will make your job of attracting a community harder. It would be much more widely useful if it did not require EJB technologies and I suspect iy would thus be much easier to attract more developers. If at all possible I would suggest making it run in non-EJB environments but thats completely up to you ;) +1, proper encapsulation should include EJB functionality for those who desire it while not requiring it for those who do not. There is also a matter of licensing involved there. What matter of licensing would that be? I can't imagine that you need to talk to sun to *use* EJBs -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Be a giant. Take giant steps. Do giant things... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- www.superlinksoftware.com www.sourceforge.net/projects/poi - port of Excel format to java http://developer.java.sun.com/developer/bugParade/bugs/4487555.html - fix java generics! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: The future of java-icalendar
Andrew C. Oliver wrote: On Sun, 2002-01-27 at 23:17, Peter Donald wrote: snip previous converstaion +1, proper encapsulation should include EJB functionality for those who desire it while not requiring it for those who do not. There is also a matter of licensing involved there. Thanks, I guess you are right. Requiring EJB is quite a lot. I would like to take this time to formally request that the java-icalendar module be moved over to the jakarta-commons sandbox and that my apache commiter account be reinstated so that I can commit the new code into cvs. Once we have the new source code in place I will contact all the people who have emailed me about the project over the last year and tell them to join the commons mailing list if they are still interested. In the meantime I will be preparing the website with an initial set of project guidelines, documentation, and continuing to work on the code. Thanks for your input. Now back to listening Jeff Prickett snip some more www.superlinksoftware.com www.sourceforge.net/projects/poi - port of Excel format to java http://developer.java.sun.com/developer/bugParade/bugs/4487555.html - fix java generics! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
The future of java-icalendar
Hello Apache Software Foundation Community: I have previously donated a large chunk of time to starting the java-icalendar module which I had to stop maintaining about a year ago. This was because of personal reasons. I would like to publicly apologize to the ASF for not continuing the project. I would like to restart the project and take the initial steps to make java-icalendar a full-fledged jakarta project. During the last month I have begun rewriting the icalendar module to get it ready for release. I would like to name the project Periodicity. I would like to utilize the EJB architecture and support most of the major EJB containers starting with JBoss of course. I would like to use JUnit to write Unit Tests for the project I have begun writing the project guidelines and have started building the project website. I have rewritten the API to take full advantage of Java 2 Enterprise Edition. I have saved the email addresses of most of the people who have emailed me regarding the icalendar project in the last year. I have begun personally responding to email inquiries about icalendar. My questions are this: Would ASF accept my sincere apology and work with me to help make the project viable? Would periodicity be an acceptable name for the project? Can I base the iCalendar objects on EJB technologies? Is the IBM Public License compatible with Apache license? (Can I use Junit for testing?). You can take a peak at the revamped code base at http://www.shpimp.com/apache. Thanks All... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
