No, you're welcome to criticize, and you're especially welcome to help
rectify the perceived problems, but the tone of your proposal suggests
that you have another hidden agenda. In addition, you're rehashing a
problem that has been discussed at length before. If you trimmed your
document to a strictly technical proposal, it would be less than half
its current length, and we would currently be arguing the technical
merits of it instead of having this fruitless discussion. Even
better, if you had offered to implement it, your proposal would have been warmly received.
Yes, acs-messaging should go, and acs-workflow should go, but I'm not
so sure that the CR should go. In past discussions, we agreed that packages
should move towards using the CR, so that common services like search,
categorization, etc. can be enabled easily for supporting
cross-package aggregation of content management. I think it was a mistake to not base the new forums packages on the CR, since we now have to add additional code to support searching and categorization of forums that otherwise wouldn't be needed, if it had used the CR as a base.
We don't need to use mist to rectify this problem. I could go into cvs
and easily fix that problem right now, if we had a consensus to do so.
If you wanted to change this, you could have done it yourself (years ago) after a
short discussion on the bboards.
