![]() ![]() (Many people of small communities already moved to the English Wiktionary for that reason). People editing Wiktionaries with a small community may voluntarily move to OmegaWiki, where edits would have more impact.Therefore it cannot be considered as a replacement. At the moment, OmegaWiki does not have all the features that Wiktionary provides (inflexion tables, etc.).Forcing them to move to a different project would make no sense. English and French) have built a strong community. While OmegaWiki is better for translations - because of how it is designed -, it seems that Wiktionary will still be a better tool for monolingual dictionaries, in particular because it is a Wiki page with no constraint.OmegaWiki would coexist with the various Wiktionaries, and for several reasons: Most (if not all) of the contributors to OmegaWiki already have an account in a Wikimedia website, so that switching to Unified Login could be done without too much trouble. There is a legal problem of copyrighting words, phrases, sentences and definitions, which mean that it would be probably better to leave the least restrictive license as the OmegaWiki license. Licensing should probably stay CC-BY, not CC-BY-SA.Since we want that as many people as possible can use the data from OmegaWiki, it was decided to dual-license it, so that people using our data can choose the license that suit them. Some other localization is done by the Wiki itself: in a translation dictionary, you can find translations for your own interface :) OmegaWiki is already using translatewiki for its localization. images are taken directly from Wiki Commons), so that there are only a few images that would need to be transfered, which are screenshots of OmegaWiki illustrating the help pages. OmegaWiki already uses InstantCommons (i.e. The procedure for installing a copy of OmegaWiki is described there.īy moving the database, the old server would be switched off (since there would be no one left to maintain it), so that the website name "" - which belongs to GerardM - could be reused. Moving to a different server requires someone with access to the server ( Kip or Erik), who would perform a full dump of the database and transfer it in the new server. PHP, MySQL and anything else that is needed to run MediaWiki 1.20 and some extensions.at least 2GB RAM, since the current SQL database is about 750MB.Response time could be improved, perhaps by separating the application server from the Web server, or by improvements in the software. The current server on which OmegaWiki is hosted has only 1GB RAM which is very limiting. ![]() The WMF could host OmegaWiki on its servers. ![]()
0 Comments
Leave a Reply. |