Hi Perry,
That is strange because Admins can edit anything regardless of whether the Admins role is selected as an edit role. I'm not sure how that problem is happening, I have never seen it and cannot reproduce it. It still sounds like possibly mismatched versions of files got deployed or something. My packages don't exhibit that error.
Regarding your development plans, I would encourage you to do all your custom development in external projects and NOT change mojoPortal code unle4ss there is no other way. Once you start changing mojoPortal code you are creating a fork and that will make it difficult for you to upgrade without losing your changes.
Its possible to submit changes to be included in the project but I have limited capacity to coordinate the efforts of others and only accept changes if they are aligned with where I'm heading for a given feature and depending on how easy it is to include the changes. For example nothing that uses the database in the core of mojoPortal can be included unless its implemented for all supported databases, I can't let the build get broken for any data layers. So, I'm open to contributions but its a case by case basis driven by many factors including how busy I am. Smaller changes are easier to accept if I agree with them. It also easier to consider new features as opposed to modifications to existing ones because this can be dne without any impact on other things going on in the project.
One approach that is safe (but not trivial) is to clone a feature before you start customizing it. That is the safest way to ensure you can always upgrade.
Best,
Joe