On 18/01/15 12:07, Benedikt Ritter wrote:
...
To sum this up: All that is blocking github commons rdf to join Apache
Commons is the mailing list thing?
>
> Regards,
> Benedikt
Some thinking out loud ... in email ...
There are two mailing lists issues : "dev" and "commits".
"commits" has some very specific requirements for the Apache Commons PMC
(although this is sandbox, hence unreleasable, so therte is another
checkpoint later).
"commits" is also a place to see updates for contributors as well.
The commons commit list is about 350-900 emails a month; one day is over
several archive (/mbox/) pages.
It might work to seek tags like "apache/commons/rdf" but I feel that
asking people to get sophisticated (specialised) for one particular
community (we are all in many communities) is yet another barrier. Any
barrier is surmountable but the cumulative effects are not helpful in
establishing community.
Apache Commons works well for the existing components. I wonder how
much variation to normal Apache Commons processes is sensible and viable
long term. (c.f. the "mini incubator" effect). There is to me a
difference between this being a one-off variation of Apache Commons
compared to a evolution of Apache Commons for any component. I don't
know where the balance is, should be, could be, or can be.
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org