As mentioned, if we find a reasonable workflow to accept and process device updates (see at least one JIRA ticket nobody acted upon, mainly because Bertrand is the assignee and it can't be delegated or picked up by others[?]) I don't see much benefit in a copy of either repository on GitHub.
A few unanswered Pull-requests on OpenDDR GitHub with similar aim (update signatures) shows, GitHub is not a universal cure if there's only one (or no?) person left in charge to merge. I pinged the old OpenDDR crew a while ago and received no feedback, so it is certainly very inactive now, or (as Reza/Eberhard called it) close to "dead"/"archived". Another reason to try foster activity here as the prime and maybe only serious Open Source answer to a handful of commercial proprietary solutions. Werner On Mon, Jun 30, 2014 at 12:31 PM, Bertrand Delacretaz < [email protected]> wrote: > Hi, > > Just one more note about this, with my incubation mentor hat on: if > the people currently active on DeviceMap want to move it outside of > Apache, that's perfectly possible. > > Apache owns the DeviceMap name, so doing so would require changing the > project's name, to clearly disconnect it from Apache. That might be > negotiable as DeviceMap is still in incubation and hasn't done any > releases, but a new name is probably easier. > > IMO it's better if the project can stay at Apache, finish incubation > by doing at least one release and form a PMC that has at least 4-5 > active members to create a minimally viable project. Apache is a great > neutral place for the kind of code and data that DeviceMap maintains, > but you need 3 active PMC members to be able to vote on things like > releases and new committers and PMC members. As people are not always > present, to graduate the Incubator usually requires 4-5 PMC members. > > I am willing to stay on that PMC if needed to oversee things, but > won't be active on the code or data gathering work this year due to a > change in my work priorities. I'm also willing to help make the > necessary contacts for infrastructure (data collection website), > moving to Git etc. within my limited availability. > > OTOH, if people think moving to github will help DeviceMap flourish, > so be it! The project can always come back later via incubation once a > community is formed, and the existing code can be forked as per the > Apache license, as long as it's suitably adapted (java package names > should not be apache.org, etc.) > > DeviceMap has been in incubation since more than 2 years, I guess it's > time to either ramp up the activity to graduate, or decide to move > elsewhere to create an initial community. > > So, Reza, Eberhard, Werner and maybe others, what's your preference? > > -Bertrand >
