and the follow up... > On Fri, Jul 22, 2005 at 11:49:07AM -0400, Charles Fry wrote: > > Cool. How should I go about suggesting/making changes? I have an Alioth > > account as cfry-guest, if someone could add me to the project. Otherwise i've added you to the developer list, so you should now have cvs commit access. now wrt my other thoughts... having taken a read over your pear policy, i have the following thoughts: 1: there are portions of the text that are redundant with existing policy, or serve more as general advice to maintainers as opposed to being policy requirements. for example, with the package name, policy already requires that packages do not have capital letters or underscores. my guess for this example is that the intent is to define the differences between debian pear packages and the upstream package name; if that's the case it should be clarified 2: there are many informal 1st/2nd person references. typically policy documents avoid this. in most cases references to "you" could be replaced with "php pear packages". as for the "we" stuff, that should probably be rethought or removed to be more formal. 3: there should be a clear distinction between what are proposed policy requirements and what are packaging guidelines. what is probably the best way to do this is to have two seperate documents (one policy, the other a HOWTO), or at the least have the guideliness placed in an appendix or other seperate part of the document. 4: i'm trying to wrap my head around the "big picture" of how this fits in with the web application policy project. currently, my thought is that all the php-specific stuff (including pear stuff) should be seperated into a seperate php policy similar to how there is a perl policy. the web application policy could then be made to defer most php references to said policy (with the possible exceptions of required webserver settings etc). if you haven't read the perl policy, i'd strongly suggest taking a look at it for ideas of what the debian policy team will want to see. okay, that's it. let me know what you think! sean
Attachment:
signature.asc
Description: Digital signature