Re: Proposal for File::iCal
| From: | Ryan King | Date: | Tue, 17 May 2005 23:57:14 +0000 |
| Subject: | Re: Proposal for File::iCal | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37707@lists.php.net to get a copy of this message | ||
On May 17, 2005, at 2:16 PM, Gregory Szorc wrote:
Sean Coates wrote:Usually people propose the project to PEAR sometime between having 'something that kinda works' and being 'finished.' Generally its nice to be able to see some source code along with the proposal, but in the case of this package, which has a very well defined purpose, I don't think that's as necessary. I think the part about discussing it on the list is for more far-fetched ideas. I'd say go head and propose it in PEPr. -ryanGregory Szorc wrote:I was confused by the online manual with regards to PEPr. One place it says to propose in PEPr pretty much whenever, even if the project is just a concept. Other places it says to start a discussion on the dev list and to hold off proposing on PEPr until the project is complete. Which should it be?The RFC 2445 (iCal) specification is a powerful format for internet calendaring and scheduling. Almost every popular calendar application can import and/or export iCal files.I've had a need for this in the past. It would be nice to have a common iCal implementation in PEAR. Propose it in PEPr? S
Greg --PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php