Dear community members, I just joined this mailing list and I have a couple of questions regarding the way of working in this community. 1. Is there any documentation that explains how to contribute to the open source development (i.e. is there a kind of guideline for a BlueZ software engineer)? 2. How is the development of new profile features (or profile version upgrades) organized for BlueZ: a) How does the community discuss and agree on the features that should be developed next? b) What are the typical steps to integrate new/additional functionality into Bluez? c) Does a kind of roadmap exist for Bluetooth profiles/features? d) Are there working groups for specific topics in order to coordinate development activities and to share experience? 3. What is the focus of current BlueZ development? This question basically goes to all community members. Feedback from everybody who likes to answer is very welcome! Thank you in anticipation! Best regards Mike -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
