Hi, On Sun, Mar 29, 2015 at 4:58 PM, Reza Naghibi <[email protected]> wrote: > ...The concern is that as this project evolves, we need to make sure that any > sort of public facing material matches the goals and reality of the > project....
It's the same with all Apache projects, what's important when talking about them publicly is to clearly separate between one's own opinion and the project's "official direction", whatever that is. In general no one represents Apache projects officially in public, we all just give our own opinion about what we are doing or planning to do in the projects. I would argue that Apache projects don't have an official opinion, they are just the sum of their community member's opinions. This is similar to the foundation not having a technical strategy or plan and "just" providing a space for its projects to exist - our projects provide a space for committers to do good stuff, but exactly what that good stuff is might not be known before it happens. More concretely, what DeviceMap can do is a) agree on a set of goals and maybe a roadmap, and publish that at http://devicemap.apache.org/ b) maintain a list of links to talks, blog posts etc. that the project agree go in the right direction, also at http://devicemap.apache.org/ c) make sure no one makes promises in the name of DeviceMap, which I think is not realistic. Once we have a) people are free to point at it however, so having that is a big plus. Note that I don't mention any votes in these three items, the best is if all this can happen by natural consensus, but if people want to vote on things to make the consensus clearer that's also ok. -Bertrand
