The Lift Community and Expected Behavior
The Lift community strives to be a warm and welcoming place to newbies and seasoned users alike. If you've got a question, the community will try to provide a substantive answer (not RTFM.)
The Lift mailing list is the official support channel for Lift. The IRC channel is a popular, but unofficial, support channel for Lift.
- The following are not ways to get support for Lift:
- Personal email to one of the committers (unless you have a relationship with that committer)
- Personal IM with the committers (unless you know them very well)
- Twitter... the Lift committers don't monitor Twitter for Lift support requests
- GitHub... don't use GitHub messages. None of the Lift committer will pull from your repository. The Lift IP is clean which means that unless you are a committer and you have written the code yourself, it doesn't get into Lift. This allows businesses to use Lift knowing what the provenance of the code is.
Please be polite on the Lift mailing list. Please say "please" and "thank you." The community tries to be timely with answers, but very often a question may not get an answer for a few days. Being a squeaky wheel about getting an answer will not make it happen any faster. There are people on the Lift list who are consultants. If you need support in a timely manner and are willing to pay, please make that offer.
Disagreements... there are plenty of ways to approach technical issues. Lift was built from user feedback and we try to foster a community in which feedback is encouraged. But this implies certain ground rules:
- Ground rules:
- You can disagree with a person's opinion, but please continue to respect the person
- Using words like "nightmare", "sucks", and other similar words will not help your cause. Please spend time working on the positives of your position rather than focusing on the negatives of other peoples' positions.
- You may have to agree to disagree
New member of the group are moderated (this radically reduces spam). You may have to wait 2 to 24 hours for a post to be moderated. Please do not repost the same question if you don't see it show up immediately.
Lift is an open source project done entirely by volunteers. The Lift documentation is not professional. If you would like improvements to the documentation, please write wiki articles or add a recipe to Lift Cookbook. Posting complaints about the documentation on the mailing list does not help it appear faster. Posting questions and summarizing the answer into a cookbok recipe or a wiki post on the other hand will earn you faster and more detailed answers in the future.
Please also read! The Loyal Opposition. Before opening a ticket, please discuss it on the Lift Google Group. For more information, Creating Tickets outlines the rules for opening tickets. We have this policy to keep Lift-related discussions in the open and available to every community member.
2015/01/11 The Lift team is proud to announce the release of Lift 2.6 Final.
2014/11/23 The Lift team is proud to announce Release Candidate 2 of Lift 2.6.
2014/07/30 The Lift team is proud to announce Release Candidate 1 of Lift 2.6.
2014/06/19 The Lift team is proud to announce Milestone 4 of Lift 2.6.
2014/04/12 The Lift team is proud to announce Milestone 3 of Lift 2.6.
2013/11/20 Lift and BREACH: How Lift protects you, and how you can protect yourself
2013/11/08 The Lift team is proud to announce Milestone 2 of Lift 2.6.
2013/10/11 The Lift team is proud to announce Milestone 1 of Lift 2.6.
2013/07/15 A list of things new and noteworthy in Lift 2.5
2013/06/28 The Lift Cookbook is now available from O'Reilly.
Entwicklung von Web-Applikationen mit Lift und Scala by Thomas Fiedler and Christoph Knabe.
Lift In Action by Tim Perrett is available in print and eBook format.
Lift Web Applications How-to by Torsten Uhlmann is available in print and eBook format.