Re: [PEPr] Changes in proposal for SMS::SMS_Clickatell

Quoting Tobias Schlitt <tobias@schlitt.info>: > > <quote who="Marko Djukic"> > > >> > what do people think of using this class for PEAR's Net_SMS? > > >> Sounds cool. I suggest to start a PEPr proposal, once you think that > >> you are finished with everything. > > > sure. what do i need to do to get a PEPr proposal inserted? > > Sorry, but what is that all about? There is a proposal for Net_SMS in place. > Why to add anotherone? I am more than happy to hear any comments on my previous emails pointing out the fact that there is already the structure and classes for building a flexible Net_SMS package without someone recoding the lot from scratch or proposing packages which are just limited to one driver. It is currently sitting in the Horde framework packages collection, but I am more than happy to put the effort into submitting it to PEAR, adding any other extra functionality from the other proposals/ideas/classes floating around, if the end result is less work for all and one powerful/flexbile class - in fact I should have the Gammu driver finished tonight. On the other hand I am at no loss to just continue using it within the Horde framework as it is and forget about PEAR. And as a side note this whole PEPr workflow seems like trying to jump through flaming hoops backwards and blindfolded to get anything even discussed. Starting from the fact that PEPr is unfindable on the PEAR website and has poor navigation within PEPr, to the fact that it is still a "talk to the lists"/"go register on PEAR"/"no, go back and talk to the lists"/"wait what are you talking about again?" business that just makes one want to give up and wonder why bother. I have more than enough hassles without trying to figure out how to fit into a non-existant workflow to offer something to PEAR. Here are some suggestions: - Make the PEPr open to comments from non-registered users, moderate it even, but allow them to make comments to proposals. - Add a link, any link, to PEPr *somewhere* on PEAR webpages. - Add some navigation to other proposals once in PEPr. - Allow package proposals to initiate on PEPr. Keep things in one place without bouncing people from lists to PEPr and back again. Marko