Re: Small pile of Test::Builder 1.5 refactoring tasks
On 2011.11.2 7:24 PM, James E Keenan wrote: > On 11/2/11 4:35 PM, Michael G Schwern wrote: >> Here's all the current gardening tasks. >> https://github.com/schwern/test-more/issues?labels=Gardening%2CTest-Builder2&sort=created&direction=desc&state=open&page=1 > > I will start to look at these ... but would these be suitable for Google > Code-In students? Yes, except GCI will be too late for most of them. GCI doesn't start until Nov 21st and runs through mid January. Most of that needs to be done ASAP. However, the "Gardening" and "Easy" labels can be used as a dynamic set of tasks for GCI. -- The interface should be as clean as newly fallen snow and its behavior as explicit as Japanese eel porn.
Perl QA Hackathon 2012
Hi, Here are some news about the Perl QA Hackathon 2012. TEAM It seems we are picking up the gauntlet, and it will happen in Paris. :-) The current local team is very small: it's just myself and Laurent Boivin. Laurent is the treasurer of the French Perl Mongers, and has a lot of experience in organizing the French Perl Workshop and OSDC.fr conferences in Paris. He is also very good at reminding me this is all my fault, and we still have all those things to do. We will welcome help from perl-qa dwellers, for all things that can be done remotely, such as finding more sponsors, taking care of the web site, etc. VENUE - We have two possible venues: ** Carrefour Numérique, Cité des Sciences et de l'Industrie ** Dates: Friday March 30 - Sunday April 1st, 2012 Price: free Seats: 30 Rooms: 1 Location: inside Paris but on the outskirt (19th district) Opening hours: 09:00 - 18:30 (it's possible to negotiate more time, but we need to decide before January) Network: wired with little restrictions, or wifi with a dedicated VLAN and no restrictions Catering: it's possible to eat snacks, but we can't have lunch (or anything looking like a real meal) inside there are several places to eat close to the venue Accomodation: close to several hotels, we will soon start talking to them Constraints: will need the list of attendees 15 days in advance, to allow entry during "extended hours" and on Sunday History: The French Perl Mongers have a long history with la Cité des Sciences: it has hosted several French Perl Workshops and OSDC.fr conferences. The security people knows us, and there never was any issue. ** La Cantine ** Dates: Friday March 30 - Sunday April 1st, 2012 Price: we have a quote for 5700 EUR for the three days (this includes a 50% discount) Seats: up to 50 Rooms: 3 to 4 available Location: center of Paris (2nd district) Opening hours: no limit, we'll have the keys. Network: open wifi network Catering: possible to eat inside, there's also a lot of choice outside Accomodation: there are also many hotels around, but more expensive than around la Cité des Sciences Constraints: we are basically free, given what we will be paying History: We have no history with this site. This location is more "trendy". It would be great if it were in the price range of the other location. ;-) SPONSORS We haven't started actively looking for sponsors yet. Currently, we have: - the surplus from last year's QA Hackathon (about 1000 EUR) - a 500 EUR donation from Renée Bäcker Sponsoring doesn't need to be in cash: a company can directly pay for an employee's (or even a non-employee) travel and accomodation costs. BUDGET -- Our goal is to cover the travel, accomodation and catering costs for as many people as possible. The actual coverage will of course depend on the amount of sponsoring we can round up. WEEKLY MEETINGS --- Last year, we had weekly IRC meetings. This was very useful to prevent things from slipping, and to stay focused on the organization of the event. We will have a weekly meeting on #perl-qa (irc.perl.org), every Thursday at 13:00, for 15 minutes. Everyone interested is invited to participate. I expect the meetings will last longer as the hackathon approaches. Minutes will be posted on the perl-qa mailing-list. Next meeting: Thursday November 10, 2012 -- Philippe Bruhat (BooK) You never know what love is until you lose it. (Moral from Groo The Wanderer #38 (Epic))
Re: Perl QA Hackathon 2012
On Thu, Nov 3, 2011 at 8:25 PM, Philippe Bruhat (BooK) wrote: > It seems we are picking up the gauntlet, and it will happen in > Paris. :-) > > The current local team is very small: it's just myself and > Laurent Boivin. Hooray! And thank you! > We have two possible venues: > ** Carrefour Numérique, Cité des Sciences et de l'Industrie ** > Price: free > > ** La Cantine ** > Price: we have a quote for 5700 EUR for the three days I vote for "free", particularly since I would guess that hotels on the outskirts are less expensive as well. I don't mind the limited opening hours of Carrefour Numérique, as we can always reconvene at the hotel after dinner for evening hacking. > We will have a weekly meeting on #perl-qa (irc.perl.org), every > Thursday at 13:00, for 15 minutes. Time zone? --David
Re: Do we need subtests in TAP?
* Michael G Schwern [2011-10-29T05:20:07] > [ What if subtests stop indenting? ] Sorry, I'm quite late to the party. I really like the isolated planning of subtests, and the visual indenting, and (least of the three) the potential for building a better visualizer that works with the subtest organization. I would be quite sad to see it gone. -- rjbs
Document the delegator or the delegated?
When doing delegation I have a documentation dilemma: do the API docs go in the delegator or the delegate? In this case it's Test::Builder2::TestCase which delegates to a stack of Test::Builder2::EventCoordinator objects. The user will primarily interact with TestCase objects. Only rarely should they ever touch an EventCoordinator directly. Do I put all the documentation in TestCase, because that's what the user will work with, and put a pointer to EventCoordinator? This presents a unified interface to the user... but it's harder to maintain. And if you DO need to use an EventCoordinator it's harder to know which methods are EC's and which are TestCase's. Do I document their native methods in their respective classes and point the TestCase docs at EventCoordinator? It's inconvenient to the user to have to jump between two class's documentation to learn how to use one class. But it is easier to maintain. It also conveys the true nature of things presenting a more accurate model (not necessarily more useful). Meanwhile, I'm going with documenting in place. It's easier while the API is evolving. Hmmm... sectional POD includes anyone? -- Look at me talking when there's science to do. When I look out there it makes me glad I'm not you. I've experiments to be run. There is research to be done On the people who are still alive. -- Jonathan Coulton, "Still Alive"