Comments on: MediaWiki limits Enterprise 2.0. http://www.gilyehuda.com/2009/09/25/mediawiki-limits-e20/ A blog about collaboration, trust, open source, workplace, and community behaviors. Wed, 08 Feb 2012 09:19:08 +0000 hourly 1 http://wordpress.org/?v=3.1.4 By: Quora http://www.gilyehuda.com/2009/09/25/mediawiki-limits-e20/comment-page-1/#comment-4993 Quora Fri, 29 Oct 2010 03:50:38 +0000 http://www.gilyehuda.com/?p=778#comment-4993 <strong>What is the best freeware wiki solution for a company with 200 employees? Is it Foswiki?...</strong> wikimatrix.org has a lot of factoids about many wiki options (though sometime dated).  It might help you, but I'm not sure it will truly guide you.  But I'll warn that your questions assumes there is such thing as a "best wiki solution" -- it's li... What is the best freeware wiki solution for a company with 200 employees? Is it Foswiki?…

wikimatrix.org has a lot of factoids about many wiki options (though sometime dated).  It might help you, but I’m not sure it will truly guide you.  But I’ll warn that your questions assumes there is such thing as a “best wiki solution” — it’s li…

]]> By: Proposing some sessions for #e2conf | Gil Yehuda's Enterprise 2.0 Blog http://www.gilyehuda.com/2009/09/25/mediawiki-limits-e20/comment-page-1/#comment-3616 Proposing some sessions for #e2conf | Gil Yehuda's Enterprise 2.0 Blog Wed, 20 Jan 2010 16:51:15 +0000 http://www.gilyehuda.com/?p=778#comment-3616 [...] scalable (it powers Wikipedia).  And its found in lots of organizations (maybe yours too).  But does it help or hurt?  And what should you do about [...] [...] scalable (it powers Wikipedia).  And its found in lots of organizations (maybe yours too).  But does it help or hurt?  And what should you do about [...]

]]> By: yeysus http://www.gilyehuda.com/2009/09/25/mediawiki-limits-e20/comment-page-1/#comment-3261 yeysus Sat, 28 Nov 2009 08:12:57 +0000 http://www.gilyehuda.com/?p=778#comment-3261 Hi. I think there are 2 aspects to this, one is the business case, the other is the technology. If you want to have only one single-point-of-web2.0 software for your enterprise, you are after technology, and should buy one of the clones that don't match with real life outside of a company, like Confluence and the likes. Think of it, you don't have only one software suite for everything you need. Even MS Office has still, many years later, one Word, one Excel, one Access, one PowerPoint and one Outlook. I believe on the philosophy of openness that promotes MediaWiki, so I see MediaWiki at the top of the information road on an enterprise. Like the white pages, you search for something, you find a description, an address, a contact person and so on. Still, you need a second click to actually go to the website of your search term. Or somebody needs to open you a door and authorize you to go inside your searched address. This is the way I see it: MediaWiki on top as an open, informal, way of collecting not only "what" (btw including how-tos), but also "where is the information", so you link from MediaWiki to your intranet, to your tons of specialised software, databases and portals (I work for an enterprise a few times bigger than Fidelity and much more diverse, I do have many pockets of information with many authorization schemas) and so on. Resuming: Non-regulated MediaWiki on top as a quick and informal Where to find What, below intranet (official communication channel of the corporate) and whatever information you want to link with read/write access control, including closed wiki systems like the ones from SharePoint and Confluence. Hi. I think there are 2 aspects to this, one is the business case, the other is the technology. If you want to have only one single-point-of-web2.0 software for your enterprise, you are after technology, and should buy one of the clones that don’t match with real life outside of a company, like Confluence and the likes. Think of it, you don’t have only one software suite for everything you need. Even MS Office has still, many years later, one Word, one Excel, one Access, one PowerPoint and one Outlook. I believe on the philosophy of openness that promotes MediaWiki, so I see MediaWiki at the top of the information road on an enterprise. Like the white pages, you search for something, you find a description, an address, a contact person and so on. Still, you need a second click to actually go to the website of your search term. Or somebody needs to open you a door and authorize you to go inside your searched address. This is the way I see it: MediaWiki on top as an open, informal, way of collecting not only “what” (btw including how-tos), but also “where is the information”, so you link from MediaWiki to your intranet, to your tons of specialised software, databases and portals (I work for an enterprise a few times bigger than Fidelity and much more diverse, I do have many pockets of information with many authorization schemas) and so on. Resuming: Non-regulated MediaWiki on top as a quick and informal Where to find What, below intranet (official communication channel of the corporate) and whatever information you want to link with read/write access control, including closed wiki systems like the ones from SharePoint and Confluence.

]]>