Folks, There has been a lot of talk about method/class naming in Lift lately. It's a good thing(tm) to normalize method and class naming in Lift.
But it's also important that after the initial cleanup is done, the consistency is kept going forward. It's also important that there's a pair of eyes looking at code as it's evolving and getting the names right early. For example, the common Actor stuff was floating around for 6 weeks (and very publicly so) before we rolled it into Lift. Jonas and I were the only ones that commented on the code. We got it to where we liked it and pushed it into master... then people made suggestions about the names. This is the wrong time. As important APIs are evolving, it's important to get the names right before people start using the code. So, I'm asking for someone in the community to step forward and own naming in Lift. You may choose to have commit rights to the Lift code or not, but you will be responsible for: - Understanding most (all?) of the Lift modules such that the person has a broad understanding of the pieces of Lift - Organizing a set of change recommendations for name changes and deprecations - Soliciting community involvement and feedback on the recommendations - Finalizing the recommendations for the next release of Lift (whether that's called 1.1 or 2.0) - Doing ongoing review of material additions to Lift to make sure things are consistent So, if you're interested in that role (and it's a non-trivial time commitment over the next 6 weeks), please contact me off-list and let's chat. Thanks, David -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=.
