Who controls svn.perl.org?
Who do I need to contact to get access permission on svn.perl.org so I can add the 'threads' and 'threads::shared' modules to it? Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html
Re: Who controls svn.perl.org?
As with most things relating to Perl infrastructure, I'd start by asking Ask: [EMAIL PROTECTED] Regards, David On 4/2/07, Jerry D. Hedden [EMAIL PROTECTED] wrote: Who do I need to contact to get access permission on svn.perl.org so I can add the 'threads' and 'threads::shared' modules to it? Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html
Re: Who controls svn.perl.org?
On Mon, Apr 02, 2007 at 10:29:12AM -0400, David Golden wrote: As with most things relating to Perl infrastructure, I'd start by asking Ask: [EMAIL PROTECTED] Or, more generally, [EMAIL PROTECTED] Tim. Regards, David On 4/2/07, Jerry D. Hedden [EMAIL PROTECTED] wrote: Who do I need to contact to get access permission on svn.perl.org so I can add the 'threads' and 'threads::shared' modules to it? Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html
Re: Who controls svn.perl.org?
On Apr 2, 2007, at 7:53 AM, Jerry D. Hedden wrote: Who do I need to contact to get access permission on svn.perl.org so I can add the 'threads' and 'threads::shared' modules to it? I recommend using Google Code hosting at code.google.com instead. Setup is trivial, as is adding people to the project. Both of those require human intervention if you host it on svn.perl.org. But I see from http://www.perlmonks.org/?node_id=606275 that you've asked and been responded to there about this. I wonder why you still want svn.perl.org. Andy -- Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Re: Who controls svn.perl.org?
For my own modules, I might consider it, but for core modules, I feel they should go somewhere more 'official'. I thought that, too, but now I don't see that it makes a shred of difference. If you see anything where it would make a difference, even in perception, please let me know. But I see from http://www.perlmonks.org/?node_id=606275 You must be mistaking me for someone else on this point. I am not referenced on that node. Yes, my mistake. David Golden commented on the thread here, and on perlmonks, and I had a brainfart. -- Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Re: Who controls svn.perl.org?
On Apr 2, 2007, at 11:16 AM, Jerry D. Hedden wrote: If I should drop dead, someone in the Perl community could take over the modules. They can anyway. The repository at code.google.com is no less open than svn.perl.org. The big thing is that code.google.com takes the burden off of the already overworked and tireless Ask and Robrt. xoxo, Andy -- Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Re: Who controls svn.perl.org?
On Apr 2, 2007, at 2:19 PM, Tels wrote: svn.perl.org sounds much more officially perl than some random google URL, So what? plus you got two repositories, which is never a good thing. Why? We've got dozens of repositories right now. What's it matter if it lives in svn.perl.org or svn.petdance.com or svn.googlecode.com? For me, concern #1 is ease of people getting at the code and ease of administration. svn.perl.org is not easily administered because I have to go through Ask or Robrt to make changes. However, as far as third-party code hosting goes, I just have to remind people on sourceforge... one can only hope google fares better in the feature. And if it sucks in the future, then move it somewhere else. -- Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Re: Who controls svn.perl.org?
Jerry D. Hedden wrote: Who do I need to contact to get access permission on svn.perl.org so I can add the 'threads' and 'threads::shared' modules to it? Andy Lester wrote: I recommend using Google Code hosting at code.google.com instead. Setup is trivial, as is adding people to the project. Both of those require human intervention if you host it on svn.perl.org. For my own modules, I might consider it, but for core modules, I feel they should go somewhere more 'official'. But I see from http://www.perlmonks.org/?node_id=606275 that you've asked and been responded to there about this. I wonder why you still want svn.perl.org. You must be mistaking me for someone else on this point. I am not referenced on that node. Don't get soaked. Take a quick peek at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather
Re: Who controls svn.perl.org?
Jerry D. Hedden wrote: Jerry D. Hedden wrote: Who do I need to contact to get access permission on svn.perl.org so I can add the 'threads' and 'threads::shared' modules to it? Andy Lester wrote: I recommend using Google Code hosting at code.google.com instead. Setup is trivial, as is adding people to the project. Both of those require human intervention if you host it on svn.perl.org. For my own modules, I might consider it, but for core modules, I feel they should go somewhere more 'official'. The contact information Tim sent is right. As Andy says we are encouraging people to look at code.google.com. As for modules getting stuck/lost there if the author goes away: The people at Google working on Google Code are friendly and helpful, I am sure we'll be able to sort that out even if Robert didn't work there and had internal access too. That being said, we are happy to host things on svn.perl.org too, in particular core modules - partly for some of the reasons you list. Just know that the UI for setting up access stuff is sending emails to RT. We have plans to make something better for that, but we made them when Sourceforge was state of the art. Since the advent of Google Code it's fallen back on the priority list. - ask
Re: Who controls svn.perl.org?
Jerry D. Hedden wrote: Jerry D. Hedden wrote: Who do I need to contact to get access permission on svn.perl.org so I can add the 'threads' and 'threads::shared' modules to it? Andy Lester wrote: I recommend using Google Code hosting at code.google.com instead. Setup is trivial, as is adding people to the project. Both of those require human intervention if you host it on svn.perl.org. For my own modules, I might consider it, but for core modules, I feel they should go somewhere more 'official'. The contact information Tim sent is right. As Andy says we are encouraging people to look at code.google.com. As for modules getting stuck/lost there if the author goes away: The people at Google working on Google Code are friendly and helpful, I am sure we'll be able to sort that out even if Robert didn't work there and had internal access too. That being said, we are happy to host things on svn.perl.org too, in particular core modules - partly for some of the reasons you list. Just know that the UI for setting up access stuff is sending emails to RT. We have plans to make something better for that, but we made them when Sourceforge was state of the art. Since the advent of Google Code it's fallen back on the priority list. - ask
Re: Who controls svn.perl.org?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Moin, On Monday 02 April 2007 16:17:13 Andy Lester wrote: On Apr 2, 2007, at 11:16 AM, Jerry D. Hedden wrote: If I should drop dead, someone in the Perl community could take over the modules. They can anyway. The repository at code.google.com is no less open than svn.perl.org. The big thing is that code.google.com takes the burden off of the already overworked and tireless Ask and Robrt. So move svn.perl.org to google. Currently svn.perl.org sounds much more officially perl than some random google URL, plus you got two repositories, which is never a good thing. However, as far as third-party code hosting goes, I just have to remind people on sourceforge... one can only hope google fares better in the feature. All the best, Tels - -- Signed on Mon Apr 2 19:18:20 2007 with key 0x93B84C15. View my photo gallery: http://bloodgate.com/photos PGP key on http://bloodgate.com/tels.asc or per email. Retsina? - Ja, Papa? - Rasenmähen. - Is gut, Papa. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBRhFXYncLPEOTuEwVAQLTTwf+JTAwSSSypoXdPjZJTeKECaYkY8byrsK7 zW0t6T3Si7zJ4PM6VbBsxZxQruZAIYtsyD2G7ShNJXEu6b+6EDcbZfoylQZd/CUJ vygwHKaAFlpnUW93k7Dp3VDeiBFoA6sU4Zxr+J6Oo6UBTFB9tqqb1kb6sRIL64PO 6L+MllHYrl1rqy/lMi6viPdT8ltmobhPXL2PfYdDZDUIr0cF5OQUagKZs4/cnQEk FN2Ct0iCL/ChIUfcVnNBARxQqVPxQKZv0gfJM7u7YEY7hjln8dQYJLJB/yWkahT6 VRMv8UZj2faKFW0G5soZzIRb9ckuoImelAds3YnKBHlGlPTKxGMf3A== =vxUD -END PGP SIGNATURE-
