Front page | perl.perl5.porters |
Postings from July 2010
On Tue, Jul 06, 2010 at 08:00:00PM +0300, Gabor Szabo wrote: > On Tue, Jul 6, 2010 at 6:56 PM, Craig A. Berry <craig.a.berry@gmail.com> wrote: > > > > I think there are two questions here. One is, "How can a company that > > benefits from Perl support Perl development?" The other is, "How can > > a company that wants a particular feature in Perl get it implemented?" > > These are not necessarily incompatible, but I think a company that > > wants the latter needs to start with the former. Contribute time to > > do whatever needs to be done. Follow your inclinations but also do > > some scut work. Get to know the code, the documentation, the people, > > and the processes. In short, the advice for a company is the same as > > the advice for an individual. > > > > So the success of the latter cannot be promised in any way but the former > "How can a company that benefits from Perl support Perl development?" > can have several solutions in growing order of involvement: > > 1) give some money to TPF that might later be used somehow. But probably won't. TPF doesn't structure its grants programmes as "invitations to tender" for specific tasks. booking.com's donation sat unused for 14 months. A significant chunk of NLNet's grant for Parrot work sat unused for a couple of years, IIRC. (And this is now IIRC, as I believe most web pages detailing it no longer exist) This isn't a fault of TPF - it's simply that it's not a business that TPF is in. > 2) hire someone who is already involved in the development of perl and let > the person work X hours of paid time on perl. > 3) get some of its employees to go through the process descried above > and start sending patches. > > Other ideas? Buy a support contract from ActiveState. If you encounter bugs in perl, report them to ActiveState and encourage them to fix them for you. ActiveState already employ competent core hackers, and will feed those fixes back upstream, most likely by committing them directly. ActiveState already have the infrastructure *in place* both to hire, train and retain competent core hackers, and to solicit and maintain support contract relationship with commercial companies. Why re-invent the wheel? Nicholas ClarkThread Previous | Thread Next