User:Dantman/MediaWiki Development Chapter

The name "MediaWiki Chapter" is used under the assumption that this will be run as a Wikimedia chapter. The name can be thought of as a placeholder in case another way of running the organization is needed.

The {MediaWiki Chapter} is a {not for profit} organization dedicated to the development of the MediaWiki software and anything of benefit to its community. The goal of the {MediaWiki Chapter} is not to supplant any part of the Wikimeda Foundation's activities or role on MediaWiki but instead to provide support to areas of MediaWiki which there is currently no organization supporting.

The {MediaWiki Chapter} may hire members of the MediaWiki volunteer community as employees to allow them to do their work on MediaWiki related projects full time. {The chapter} may pay interested volunteers within the MediaWiki community as contractors to develop features that the general community is interested in. And {the chapter} may take on development projects beneficial to MediaWiki's development community that the general community would like to see done but are not directly part of MediaWiki, are too large for volunteers to robustly finish, and the WMF is not interested in building and maintaining but volunteers are. Such as building a new bugtracker or code review system better fitted to the development community. {The chapter} may also assist in supporting and maintaining new tools and sites which are useful to the MediaWiki community but may have issues staying up on their own.

Website
On {the chapter's} website a system for listing projects and tasks will be maintained. This system will allow individual projects and tasks to be added as individual entries. These may small code ideas, simple references to bugs in Bugzilla that can be fixed, rewrite ideas, whole large development projects, et cetera. The goal of the system is to gauge community interest. The entry may be commented and voted on by the general community.

Developers in {the chapter} may put up entries for projects they are interested in working on. And the general community may put up entries for things they'd like to see worked on by {the chapter's} developers. Developers should add themselves to any entry they are interested in working on and are encouraged to prioritize projects that have high community interest. The system may give lower importance to — and in some areas ignore — projects that no {chapter} developers have added themselves to. Essentially acting as a non-fixed veto indicating there are no developers currently part of {the chapter} who consider the entry within their skilled area to work on it.

... working on projects listed in {the chapter's} website, finding small reported bugs and fixing them, ...

Developers are also encouraged to keep some sort of public diary, blog, micro-blog, et cetera on their daily development activities.

When a 3rd party company desires a feature that may be useful to the general community {the chapter} may also take direct funding for that project. With the understanding that the company is paying for a feature that will be built to suit the general community and be publicly available.