Drupal on Wikimatrix - welcome `Drupal Wiki`

Awesome.

I'm curious. When it comes to enterprise applications I hope you're using already established modules and/or distributions (casetracker, Open Atrium, cck). In my opinion the only thing that was a good node_access module, a good wiki linking/node relationships module, pluggable wiki wysiwyg module to pull it together (pluggable as in format neutral).

Can you go into more about not using already published modules or helping development of them?

On another note. Did you work on any import modules for foswiki/twiki? I was working on one myself, slowly, last year, but got distracted as always (plus i had to develop for an old version of twiki).

Hello,

I am interested in your product, because none of the wiki implementation on Drupal satisfied me. It there any knid of online trial version? Video or screenshots are not enough for me if I am going to pay.

Plus, is Drupal wiki a "blackbox" solution or is it possible to extend it with other standard Drupal Modules? The reason is I want my site to also use Storm (or other project management module) as well as a forum.

Thank you.

What is this exactly? Wiki as a SaS.. as in you provide a hosted Wiki solution based on Drupal? Is this correct?

I am trying to put together a wysiwyg wiki that has OG support. Some of what you have here looks close but of course not usable as a SaS as we have a very large OG based site that needs a Wiki.. not a need for a Wiki site that needs a ton of customization to add all the features we support.

But maybe i am missing the point here?

Dave: how is this off topic? it was Eugen's thread to start with. If he wants to showcase a Wiki SaS offering they have developed using Drupal i think no better place to do it that the d.o Wiki group. Even if not available to developers it gives us an idea of what can be done.

Eugen: as i said; doubt your offering could be of any use to me.. but should you ever release any of this to the community i would be very interested in your wysiwyg plugins for adding links to existing and as-of-yet-created wiki pages. Could alos fund development for some of this work.

How about releasing it as a distro ;-)

There we go... For some years no-one build on the present wiki modules, probably because no-one financed it. And now there is finance to make private wiki projects, which modules stay private. Understandable that companies who pay for development should protect their investments. But is this the future for Drupal?

We have developed 56 modules for getting the wiki-features done that way, that the users can actually use them.

Drupal has never been really build that way, that end users are surfing through the "backend" - so being able to edit all the time and see the local task and things like this. It never has been designed that way ( at least Drupal 6 ) and thats where you will need a lot of work to go into.

Eg. dont be blinded. You will patch a big number of modules to get them work with drupal core revisioning, even large projects. Getting real content revisioning done in drupal is a pain. And did you ever think about revisioning of attachments which is state-of-the-art in other wiki`s? There are really a lot of pitfalls on the way and the current wiki-modules are kind of trying to immitate wiki-functionality by saying:

"if everybody can edit - thats it!". But even every Media-Wiki can do more then this - much more. And drupal itself is of course capable of much more, but its quiet some work.
In this field drupal is like a diamon. Its valuable but you have to grind it (quiet a lot)

@ClearXSClearXS:
I think there will be more products for drupal in the future, yes. And i think that drupal will benifit from all this, as it gets more spreaded, more known and more accepted. Some of those modules will start to be private but from time to time they will get released and contributed back. Most companies just need a time-advantage and are not against contributing back.

So actually i think its rather good for drupal, as companies can invest more money due to the better protection. Most of them will release those quality plugins later which would probably never created in the wild.

A good example would be usability. Most of the devs on d.o. are not focusing on it, thats why most of the modules are shipped pretty "raw". They are functional but mostly only useable for techs. Why is it that way? My personal view is, that in the wild devs dont have the time to focus on those tasks like usability and they dont have the skills for - they have other skills. They most probably dont have a usability expert and a UI-designer next to them to assist them in that field. So in the end they create all those "backend work" and leave the UI alone with "well everything is done, if needed, just a proper UI is to be created". But as we all know, creating a good UI is a bunch of work.

And thats what companies can change(if they are up to it, of course).

Thanks for the feedback. I got a different opinion though.

Wikimatrix does not list only free wikis at all and it is not intended by the platform to do this. There are full-commercial wikis alonside with commercial open source and free open source. You should defently look up what open source means. To bring it to the point, open source (OS) is not free open source software ( FOSS).

We dont even thing that there is yet a model / project in the wiki-sector which is successfuly build OS. Most of them lack very much on usability or a lot of features. Thats most probably one of the reasons you chose to create a wiki using Drupal, doesnt it? Because the wikis yet do not fit properly in your use-case or even are not flexible enaugh nor usable.

Neither OpenOffice, MYSQL, nor even Linux-Children lik Suse, Redhat would then be "open source" by you definition, as they all have paid products / profiles.

There are a lot of media-wiki`s arround which are developed the same way. And they all have one thing together: They hardly ever get used in a corporate enviroment because of the lack of the things i mentioned.

Drupal Wiki would simply not exist, if it would not be paid. If you expect a team of developers (full time) to invest time over more then 2 years into a product, thinking about also they have to pay feed and by bread and butter, iam not sure how you would end up managing this. Giving it away for free and nothing, how should those people live on this? It is a huge investment building such a full-fledged and integrated product on base of Drupal, and it already payed back to Drupal itself ( Tagging module, WYSIWYG image upload module, content lock, jquery_ui_dialog, drush_make_ui... content_moderation and some more).

Drupal Wiki does exist, because we have chosen a model where customers have to pay for it, so we can pay invoices and solaries.

It is build on a vanilla Drupal 6, without any hacks or tricks. So its defintly o.k calling it that way ( my opinion ). And it does not harm Drupal at all. It does spread the word of Drupal.

It does actually show, what Drupal is capable of, what you can achieve with it and that it is not only a first class CMS but rather a application plattform. We are showing this to the middle to bigger sized companies, which wonder everytime "what is Drupal" - and then it becomes the "wow effect".

As we are giving back to Drupal, as we are developing, maintaing and supporting modules full time. So iam sorry to say it that way, but i find it very ignorant to say, that we are harming Drupal by calling it Drupal Wiki. We are helping Drupal, in every single term.

How is the normal Web-Designer who build a normal web-site using 50 Drupal modules and not giving back one nor stating on the site, that it is Drupal, helping Drupal? Are you also against those telling their clients, they used Drupal? Are you also against that wall? How do those give back to the community? How many people are just using it without doing anything?

We are taking Drupal to the hight-profile customers and getting it set into the company. And this opens the doers for the different sectors of the company to use Drupal for there website, portal or other projects. "Becaus yes, we already have a successful Drupal project in hour house. We are also used to it and things like views, cck and the workflows. Lets take Drupal!"

Sorry, no way we are harming our lovely Drupal - can`t see even one single case. Its not free - yes. But its an good door opener.

And not a "lets invent pure technology without guidience with Drupal and be sure it fails and Drupal will never ever get used by this customer anymore..".

There will be a free version of Drupal Wiki for, but even creating this profile needs time and a lot of effort and maintaince, support and infrastructure.
You dont want to release a half baked demo, which has issues because you removed some functionalities or similar.

There is no doubt people would benfit of this profile but i highly doubt the economical use of this.

I'm trying to implement a simple wiki for students and educational groups. Any progress on a free distro?