Re: Proposal for File::iCal
| From: | Stefano F. Rausch | Date: | Tue, 17 May 2005 23:05:48 +0000 |
| Subject: | Re: Proposal for File::iCal | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37705@lists.php.net to get a copy of this message | ||
On Tue, 17 May 2005 23:16:07 +0200, Gregory Szorc <gregory.szorc@case.edu> wrote:
Sean Coates wrote:I've already filed a bug (#4207) report in this respect on 22 April 2005, but apparently it has not been fixed up to now - note that the guys have a lot of workload. AFAIK you can choose whichever approach suits you best. Due to the fact that you have already implemented some of the functionality, I suggest you go for PEPr - make it official.Gregory 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