Re: have anyone reviewed my files?

Your package proposal is in draft, you need to change to "proposed". Then -- if the email didn't work -- email pear-dev@ yourself and include a link. Till On Fri, Apr 3, 2009 at 3:37 PM, Dmitri Snytkine <d.snytkine@gmail.com> wrote: > Yes, there is probably some problem with PEPr because I have not seen any > emails of pear-dev after I submitted a proposal > > Can someone look at it? It's a finished package, with test cases and xml > file, ready for installation. > > > > On Fri, Apr 3, 2009 at 9:31 AM, till <klimpong@gmail.com> wrote: >> >> On Fri, Apr 3, 2009 at 3:23 PM, Dmitri Snytkine <d.snytkine@gmail.com> >> wrote: >> > Hello! >> > >> > I submitted patches for Net_GeoIP awhile ago, but have not seen any >> > comments >> > about it yet. >> > Net_GeoIP patch is not a new package, just a patch with some code >> > improvements >> >> In that case the maintainer needs to have a look. If they are not >> available/don't respond with a week or two, you could email them >> directly and CC pear-qa@ on your email. That usually speeds things up. >> If you're fixing bugs etc. pear-qa can commit your patches too and >> make a new release in case the maintainer doesn't have time/respond at >> all. >> >> Providing patches always helps for others to "judge" you (sounds >> harsh) and if you wanted to take over Net_GeoIP that would make things >> easier. >> >> > I also submitted a proposal for Event_Dispatcher2 and posted a link to a >> > finished package >> > >> > Just wondering, what is the usual timeframe for starting the votes on a >> > new >> > submitted package? >> > >> >> I think there are some email issues with the Pepr system. >> >> Usually, it's kinda like that: You submit the package in Pepr, work on >> it, ask for comments (proposed) and then depending on the comments you >> can call for votes. It also helps to address requests/comments >> directly so the people who want a change vote in favour of your >> package once you addressed. >> >> I'm not sure if the system sends out email (again), so it might have >> been missed. Just double-check if you see an email on pear-dev@ and if >> not, just email the info yourself ("I've proposed this package, please >> take a look and comment."). >> >> Till > >