Well, a first hledger code review topic has selected itself over on #ledger. The topic for this week is hledger-web and it's recent updates. I'd like to review code but expect everyone will focus on UI. Just remember UI review is a different beast, almost none of us will get what we want but we'll have fun. :)
We'll discuss on the hledger mail list this week, and on the #ledger IRC channel this friday at 0900-1000 PDT (and sooner). If Ledger folks find this too much noise on the #ledger channel at any point please let us know. I'm cc'ing the Ledger list to invite y'all too - see below. Remember hledger-web can be used for Ledger files too if you avoid the fancy stuff. Links: http://demo.hledger.org - latest version (add :5001 for the really latest) http://hledger.org/manual#web http://hackage.haskell.org/package/hledger-web https://github.com/simonmichael/hledger/tree/master/hledger-web Let's review! Best, -Simon On Sun, Jul 20, 2014, at 09:29 AM, Simon Michael wrote: > Hi all, > > the latest GitMinutes episode - > http://episodes.gitminutes.com/2014/07/gitminutes-30-luca-milanesio-on-gerrit.html > - has made me wish for more code review. He makes a nice analogy: when > coding you are in a tunnel, trying to get to the end, with very restricted > vision. Other people, or you at other times, have a much broader view and can > see differently. > > Regular code review would doubtless improve quality a lot. Also, it's an > excellent way to spread knowledge about hledger internals and infrastructure, > learn haskell idioms, and expand the pool of contributors. Thirdly, solo > coding takes a lot of energy, but collaboration is energising. I wouldn't be > surprised if it also improved quantity (speed of delivering new tested > features). > > So: are there some of you out there who would like to help with a bit of > review and make hledger better ? It's not just about code either: UI (web or > cli), documentation, web presence and other topics could all benefit greatly. > > Here's what I'm thinking: I'll announce a code review topic on a sunday or > monday. We then have four days for asynchronous email-based code review on > the hledger list. On friday morning at say 9am PST (5pm GMT) we have a > half-hour or an hour of real-time IRC-based review (on the #ledger channel, > probably). Right after that I summarise the IRC chat for the mail list. > > How about this week ? Any ideas ? Any topic works for me; focussing on > recently changed areas could be a place to start. > > -Simon -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
