> know that for many "email list" > == "community" == "Apache project". But Apache Commons is special. As > pointed out - not everyone here will be involved with all Commons > components.
Yet we consider this as one community that has cross pollination and shared responsibilities. > As Peter points out, it would be a short-lived activity span on a > "Working Group" list (6-12 month) during fleshing out of the API, and > then after say a 1.0.2 release, the list could be removed/disabled and > traffic moved to dev@commons for general maintenance. So bottom line: Commons is good enough for maintenance but not for development? Please stop arguing in the line of "we don't want to annoy other people with all our RDF discussions". We can take it. That's not the real reason. > That said - I believe the general points of the API design would be > great to get inputs from other Commons developer, like the Java 8 > Streams that we are already using. Now we are talking. cheers, Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
