Re: Proposal for File::iCal
| From: | Ian Eure | Date: | Wed, 18 May 2005 02:51:11 +0000 |
| Subject: | Re: Proposal for File::iCal | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-37710@lists.php.net to get a copy of this message | ||
On Tuesday 17 May 2005 04:57 pm, Ryan King wrote:
> On May 17, 2005, at 2:16 PM, Gregory Szorc wrote:
> > Sean Coates 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?
>
> 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.
>
IMO, if you have an idea for a package, but have doubts about it's usefulness
(or need help writing it), RFC pear-dev.
If you have code, drop it in PEPr.
Attachment: [application/pgp-signature]
Attachment: [application/pgp-signature]