Hi, Looking at Wave, also incubating, there are a few things we're missing here, part of the reason why DeviceMap got stalled and deliverables are scattered across the web in different personal homepages (e.g. Eberhard's or Reza's) instead of a well maintained project page like this: http://incubator.apache.org/wave/downloads.html
Did I mention the Apache master POMs contain valuable plugins for goals like deploy to the Apache Snapshot Repo or as Wave does it automatically JAR or ZIP up nightly builds?[?] Those are the things, a project specific how-to guide like http://incubator.apache.org/wave/get-involved.html explains, but the general Apache top level pages don't. E.g. I didn't even see anything about the Review Board at https://reviews.apache.org/dashboard/ there either. Wave uses it, and it looks like this can and should be used even (or ESPECIALLY[?]) while a project is still in the incubator. Wave has 400+ JIRA tickets it seems, opposed to merely 40 we used. Needless to say, the JIRA concept of "components" is used well. And even if there's just one person (like the project lead) who can manually assign or re-assign a task, if you define a number of components each should have a default assignee, then that person gets tasks for his/her component. E.g. "Data", ".NET" or "Java" as minimum proposal, I suggested that several times but those who could maintain it either refused or have no time and at least committers like Stefano, Eberhard or myself can't create a new component, release or other elements in JIRA, just report stuff. and fix or close (our reported) tickets. Needless to say our project home page is a shamble, given everyone else has "their own DeviceMap or DDR page" no wonder, nobody did this in the past 2 years[?] Like in JIRA I don't think I can, if it's part of the "SVN/site" structure maybe I could, then please let's decide who can do that ASAP. Cheers, Werner
