Re: Re[2]: [PEAR-DEV] XML_RPC

On Tue, 2004-11-30 at 20:41, anatoly techtonik wrote: > Hello Helgi, > > >From Tuesday, November 30, 2004, 10:21:23 PM, you wrote: > > HЮ> Well we don't usually just give people access to some packages so that > HЮ> they can commit some fixes, and also we don't have the karma to add > HЮ> rights in CVS (or well only person I know from PEAR is Stig that can add > > If you're speaking about CVS account, I already have one for cvs.php.net No I'm not speaking of a CVS account, I'm speaking of allowing people to commit to others packages, even though it's in good intentions, it's a rule not to commit in other peoples packages, unless of course any of the leads give green light on that after talking to them. > HЮ> CVS karma), so I recommend you just places those patches online and file > HЮ> a bug report or attach the link to their giving bug reports, last time I > HЮ> knew there was a new developer taking over XML_RPC so I'd think that he > HЮ> would take a look and see if it should be included. > > >From the last bugs resolved I saw it took about !six months to > incorporate some fixes even with detailed information people provided. > http://pear.php.net/bugs/bug.php?id=1604 > I don't feel like waiting for so long to make a simple task done. > > Can I be added to the list of developers of this package for a week? > It seems that Stig is too busy these days. How soon there will be > somebody new to work on the package? What it depends on? How soon = there is one now, read what Daniel said. First read what Daniel said in his email, also Stig is a very busy person indeed, but I doubt we'll allow anyone we don't know to take lead on any package, sorry, guess people have to earn trust, that's life. Specially not on such a important package, again sorry :/ I said before and I say it again, open up bug reports if you fixed any bug that hasn't been reported, include the patches or link to them, or if a bug report has been filled before on any of the fixed matters, you could just comment on them with a link to the patch.... OR just wait until the new dev announces that he's taken over (which I think won't be long) and contact him directly and he might add your fixes and who knows make you a developer or something in the package. - Helgi