Hi all! One of the main reasons for developing Murphy was the observation that a policy daemon is missing from the multimedia stack and everyone is writing their own solutions to the policy space. Murphy is aiming to be a flexible and reliable replacement for the custom solutions. It would be great to talk about how Murphy could play along with GENIVI components, so that possible overlap could be reduced and gaps identified. We (the Murphy team) would also be happy to answer questions about how Murphy works and how it can be configured/extended to fit different needs.
> It looks like re-using this mailing list: > https://lists.01.org/mailman/listinfo/murphy-dev is likely fast and > easy, I assume this is the right place to start? Then I think that a > call to bring up all requirements might be good. Sometimes a telco can > be effective, I know in Open Source projects it can be hard to jump on > telcos so perhaps this is something we use only if we have to. Yes, the murphy-dev mailing list is definitely the correct place to discuss anything and everything Murphy-related, including how it might be integrated or how it is interfacing other system components. I think it's also good to keep the discussion at least in the beginning in writing, so that it's inclusive and can later be found with web search engines by others who are asking the same questions. > It looks like this page is the central location for all things Murphy > related: https://01.org/murphy/get-involved, is that right? That's about right. The IRC channel has been bit neglected in the past, but the mailing list and issue tracker are active. Ismo Puustinen <[email protected]> _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
