Talk:Requests for comment/MediaWiki Foundation

But how

 * MediaWiki releases are not done by volunteers currently
 * Where would the new Foundation get money and workers?
 * Who would decide what it does?

Ways of meeting donor's needs
It seems to me that the donors should be in the driver's seat about what the Foundation's money goes toward. They could either earmark donations for a specific project or direct that the money be spent wherever it is needed most. Of course, fungibility of funds can sometimes defeat the purpose of these earmarks; for example, suppose $100,000 in general funding was going to go toward Project X, and then a donor gave $100,000, designating it for project X. Then Foundation could then shift the $100,000 in general funding out of project X, achieving the same effect as if the donor had given the money to the general fund.

By the way, why must it be a nonprofit? Why not set it up as a for-profit entity, and consider the donors as customers who receive software development services in return for their money? My guess is that most customers will be interested in specific projects, rather than in giving money to the general fund. This might be a more efficient way of doing things, since the advantages of nonprofits tend to be illusory. Leucosticte (talk) 23:14, 2 September 2012 (UTC)


 * You seem to have confused yourself there ;-) . The assignment of USD 100,000 to a certain project would help when WMF would otherwise allocate none. Now a better way might be to promote a project is by offering up to USD 100,000 for project X based on equal assignment by WMF from the general fund. Working for profit introduces taxes and many other expenses - which would end up monetizing all the assets. 84.3.85.135 20:06, 3 September 2012 (UTC)

Alternative - in-house WMF department
I wonder if an entity within WMF would be more appropriate and realistic. Utilizing the existing operations structure would be far easier. Perhaps setup something like FDC to oversee priorities and funds.

My hunch is WMF would be far more likely to sign off on something they retain a sense of sign-off on for the sake of maintaining the WMF projects than having to deal with an independent entity that would have the legal right to go rogue one day and not do what's in the best interest of the WMF projects. I recognize to some extent that's the point, but looking down a 5 year road of possibilities, is that something we'd ever want to happen? My feeling is no and allowing WMF to maintain some level of authority in the development of MediaWiki is in our collective best interests. From project management, fundraising, usability, system resources and paid developer support perspective.

Summary: Instead of a dedicated MW Foundation, I would instead propose a MediaWiki department or collective (insert your favorite term here). --Varnent (talk) 23:21, 3 September 2012 (UTC)

Broadly scoped
I see this RFC as a general statement about the ever-more apparent juxtaposition of the Mediawiki software and it's implementation at Wikimedia sites. We as the community need to learn how to balance the needs of the WMF (as an implementation of the software) with the need to have development of the software itself.

I agree with the statement that "there are few developers contributing to MediaWiki whose ability to take on large MediaWiki development projects is not either biased towards what is in their employer's interests or restricted in how much time can be spent on those projects." That is some good insight.

Questions:


 * 1) Where would funding come from?
 * 2) * Would this compete with the WikiMedia Foundation (WMF) ?
 * 3) How would this proposed organization interact with the "core" developers (paid staff and WMF contractors)?
 * 4) How is this different than large local chapters? (I'm thinking of Wikimedia Deutschland.)
 * 5) Who would provide the infrastructure for the release management? Where would the hardware come from?

-Daniel Renfro talk/ [mailto:bluecurio@gmail.com email] 00:45, 5 September 2012 (UTC)