There are two items. That we'd love your feedback on:
1.) It still seems like there's lots of people that think it might make sense to just keep the bier_app project as a sub-part of the bier project for a bunch of reasons including:
* lower overhead in the form of milestone readouts, testing readouts, jenkins job maintenance, etc.
* lower overhead for other people who do per-project work, e.g., integration/test, documentation
* at least the short run, there tends to be patches that end up having to go both into the plugin and the app from our past experiences
* you can still produce independent artifacts that could be re-used outside OpenDaylight without having a separate project
That all being said, if the two projects (and overlapping people) really agree that there should be two projects, we won't stand in the way.
2.) We need to figure out if there's any technical reason that we would rather not have bier_app as the git repository name. It will work fine for git, but it also gets re-used as an identifier in lots of places, e.g., maven groupIds, java package names. I _think_ underscores are fine in all those places, but it might be slightly safer to use bierapp if that works for you. Again, barring somebody telling me that this is technically infeasible, the call is yours.
Cheers,
--Colin
