Re: public SCM
| From: | Pierre | Date: | Wed, 20 Sep 2006 19:27:03 +0000 |
| Subject: | Re: public SCM | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-43993@lists.php.net to get a copy of this message | ||
Hello,
On 9/20/06, Helgi Þormar Þorbjörnsson <dufuz@php.net> wrote:
On Wed, 20 Sep 2006 11:33:57 -0700, Justin Patrin wrote: On 9/20/06, Lukas Kahwe Smith <lsmith@php.net> wrote:Hence Lukas point. And now that you can create a SVN repo in mins with googlecode, there is no more reason to accept packages without SCM. --PierreA public SCM is a rule. Either this package got in before this was checked or it was missed by someone.... It was never made into a rule, it's one of those "unwritten" known how that most pear devs have now ... some time way back I did some blog posts and ML posts about this topic (about having it also applied backwards i.e.. older packages, I think)Hi, A user just came into #pear who wanted to submit a fix for Mail_IMAPv2.. However the package has no public SCM, so the user will not venture elsewhere for his IMAP needs. Did we ever start to mandate a public SCM? If not maybe someone is motivated to write a PEPr RFC for this.