> I'm writing you since you are the community leaders for the
> DTrace & MDB communities. For the past couple of weeks we've been
> hashing out a reorganisation and reclassification of communities and
> projects[1] with the aim of having some more consistency. I'm writing
> you as our proposal involves your community or project. Specifically,
> we would like to:
>
> - Re-classify DTrace & MDB as projects, endorsed by the already
> existing Observability community.
For a myriad of reasons, we feel pretty strongly about staying a Community.
We feel that a Community more accurately captures the current state of
DTrace. This is in part because DTrace is pretty mature -- there is not
a corpus of evolving code that represents DTrace, and there is not a
DTrace project team per se, but rather many DTrace-related projects
(DTrace providers for different environments, subsystems, etc.) led by
leaders that consist of more than the original DTrace project team. We
feel it is much more natural for these projects to be Projects in the
DTrace community than they Projects living along side DTrace in the
Observability community.
- Bryan
--------------------------------------------------------------------------
Bryan Cantrill, Solaris Kernel Development. http://blogs.sun.com/bmc
