This is how all of us feel at times. I have important patches that have
been in the tracker since March that have not been tested enough. With a
complex proposal like yours it will take the sustained efforts of probably
4-5 people for 2-3 weeks to test it, generate complex and large enough data
sets to test on, figure out the implications for migration and so on.
As of now we have the following proposals on the table.
Your proposal to extend asset tracking to the menu item level.
Sander's proposal to extend it to the module level.
Sebastien's proposal to add back end access level as a new field.
My suggestion that we consider extending asset tracking to weblinks,
contacts and newsfeeds.
We also have serious problems with parent id as Sander pointed out in the
comments on the pull request and as I asked about in a detailed unanswered
question on the platform mailing list. Without knowing the intended
behavior for items not using the category system it is extremely difficult
to move forward with asset management without answers on that.
I would really not recommend edit.own as part of this solution. There are
good reasons it was only used in one extension in the core. Simply getting
baseline ACL for menus is itself a huge challenge. Make user groups with
one member if you want to implement that in a way that will be efficient.
Elin
On Monday, July 23, 2012 2:48:21 PM UTC-4, Richard McDaniel wrote:
> Well, I haven't gotten any interest in this lately so I'll just put iti on
> the back burner for now.
