Re: [PEPr] +1 for File Formats::File_CSV_Get
| From: | kazuyoshi tlacaelel | Date: | Fri, 05 Dec 2008 01:04:40 +0000 |
| Subject: | Re: [PEPr] +1 for File Formats::File_CSV_Get | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-51217@lists.php.net to get a copy of this message | ||
Anybody else feels like voting?
am waiting for that fifth vote so I can create a todo list.
On Thu, Dec 4, 2008 at 9:47 AM, Kazuyoshi Tlacaelel Tlacaelel <
kazu.php@gmail.com> wrote:
> Thanks David, Fair enough.
> I'll remove the documentation and other files from the package.
>
> On Wed, Dec 3, 2008 at 5:42 PM, David Jean Louis <izimobil@gmail.com>wrote:
>
>> kazuyoshi tlacaelel a écrit :
>>
>>> I though we needed to document the package, or is it not the right way to
>>> do it?
>>> I kind of like that the package ships with compiled documentation though!
>>>
>>
>> Package doc (not phpdoc) must be commited to peardoc cvs module in docbook
>> format, if not, you can provide external documentation (like googlecode) and
>> add the link in your package homepage, in this case I think you can ship the
>> doc with the package, it's ok.
>>
>> But phpdoc generated documentation should *not* be included in the package
>> as it is auto-generated by the pear website.
>>
>> I also like that peoople can see what is the status of the release by
>>> looking a test result logs and stuff, I defenetly feel like removing the
>>> phpdoc log!
>>>
>>
>> I don't think users will look at theses log files ;)
>> Also note that pear-qa guys have tools that give stats about coding
>> standards / doc coverage / tests etc... so it's not necessary to provide the
>> logs.
>>
>> --
>> David
>>
>>
>> --
>> PEAR Development Mailing List (http://pear.php.net/)
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>