Hi and welcome, everyone!
The Morroblivion community has grown a great deal recently, and I would like to thank all the developers, moderators, contributors and members of both the project and the forums in general. Morroblivion would not be so active today if not for everyone's combined enthusiasm! However, with all of this rapid growth, comes a lot of growing pains too. :) Despite everyone's shared efforts to get v065 released, there are still a number of things that could be improved or updated: like a list of v065 compatible mods, v065 specific installation instructions, cleaning up sticky threads, etc. I think one of the barriers for making all these changes is that many people with access are busy and the people with access that are not busy are afraid to change things.
I would like to start a discussion here about assigning/re-assigning clear roles, responsibilities and permissions to everyone actively involved in the Morroblivion project and the forums. I think these responsibilities need to be shared among multiple people so that if one person is busy, there should be other people that can perform the necessary tasks without us having a discussion to ask for permission to do so. This includes managing and updating the forums, project announcements, new major and minor releases, bug-reports, bug-fixes, etc. Some of these things can be done without website moderator privileges but some require it.
For example, some people consider me to be the de-facto "lead-developer" for Morroblivion, but I actually do not have any permissions to edit the current Morroblivion Release Post even though I am listed as the author of it. I am happy to start a new thread to help manage and update v065 updates, but it does not solve the underlying issue: if the owner of the project release thread is busy, other people with moderator privileges must have the responsibility to make sure the information is up to date.
This should also apply for making announcements, maintaining FAQ, maintaining compatible mod lists, maintaining the bug-report list, and even for creating new bug-fixes. Obviously, we will need communication so that contributors do not waste time fixing the same bug -- but we should also not allow progress to be stalled because multiple people are waiting around for someone else to do a task instead of them. I think it is important for everyone to communicate what task they will do. It is also important to communicate any changes which prevent or delay people from completing their tasks. If more than 1-2 weeks have passed, I think other people with that shared responsibility need to step in and help complete the task if it is still not done.
I propose that we officially (re)create these shared roles with the following shared responsibilities:
- Website moderator: post and update announcements, update release threads and download links, update sticky threads
- Project Release maintainer: create ESM/BSA installers, post new major and minor release threads, update release threads
- FAQ / Installation Instructions maintainer: update the FAQ page and Installation Instructions pages.
- Bug Reports maintainer: update bug reports page and links to bug-fixes.
- Bug Fixers: volunteer to fix bugs
- Shared by all forum members: answer questions, vote on what is merged in releases, etc.
Unfortunately, I think roles 1-4 require moderator privileges to be effective. This means we have to be very careful about assigning these roles and tracking who is on this list in order to maintain security.
Please let me know your thoughts, reactions and feedback for this proposal. Thanks.