inspired by http://moinmoin.wikiwikiweb.de/MoinBounties
This Bounty Program is designed to encourage development of DokuWiki software by its core developer(s) and the many plugin developers. Funders of bounties help DokuWiki developers to enhance DokuWiki in particular areas of interest to its users.
Bounties are open for any private individuals and companies - you just have to ensure (by finding other interested funders or by raising an interested topic) that the bounties' worth is not too low. Of course small changes are done for a lower amount of money than bigger ones.
A bounty is valid as long as there is at least one non-timed-out funding offer for it. If a bounty gets invalid, it will be either removed or changed into a FeatureRequest by dokuwiki development core team.
As long as the bounty is not taken, you can take back or change your funding offer at any time.
At some time, one or multiple people will like to take a bounty
We use Dokuwiki for online documentation of our Opsview product: http://docs.opsview.org
We split out the documentation based on the release number of our product, so this allows us to make sure documentation is valid for a specific release. Our workflow is that for an upcoming release, we copy the entire subdirectory/namespace and rename to the new release number and we update documentation based on the changes for that new release as we develop.
However, we find we need branching. For instance, we could fix a problem in an earlier release, but only the specific release document would be updated - it is a manual task to update later releases. This manual task is sometimes forgotten. This in turn means that we could “lose” changes because we only cut new releases based on the latest release.
For our code procedures, if we update an older release, we can just use subversion to merge changes between branches. I'd like some automatic merging to take place behind the scenes by dokuwiki, though it would obviously have to flag if there are conflicts.
So this bounty specifically requires that I can:
Just for ideas: git in the backend?
We are offering 300 Euros.
This offer will stay open until 17th December 2007.
Im using feed module from Esther Brunet: http://www.wikidesign.ch/en/plugin/feed/start
Actually this module just exports plain text and i want full html. I've asked Esther to do it but she's too busy to take the job so im offering 100€ to anyone that can do it.
Here is the svn repo: http://code.google.com/p/feed-plugin/source Ask for further info.
Offer: 100€
Contact: muzzol muzzol [at] gmail [dot] com
Note! Im new to DocuWiki!
I was reading Scalability and saw this… 7,733 documents (23.4MB), on single user system, searches > 5 minutes. On hosted server removed search facility and replaced with another. Even excluding 6632 documents (18.6MB) having huge problems with Web spiders such as Google, effectively creating a denial of service. or 1477 pages (13.2 MB), intranet with 1-2 users (being tested for scalability) - Dedicated dual-processor server w/5GB RAM and eAccelerator. Searches are slow, but almost manageable. Viewing namespace indexes is almost impossible, and I get frequent PHP timeouts even after increasing the timeout value to 60 seconds.
So what would happen if the search of 7000 docs were broken down into 37 folder e.g. 1 2 3 4 5 6 7 etc. a b c d e f g h etc. ???
* I would like to have all the pages save to a Alphabetically folder .e.g. a.txt will go to folder A b.txt will go to B folder!
* I would like the Search to look in the folder beginning with the 1st letter in the search e.g. Batman first letter B = folder B search batman.txt!!!
* How much?: $25 USD payable via paypal. contact me: info a@t eziner d0t 0rg *If you like this Idea, Please Help Pay*
* My offer is open till it done!
I have a http://www.bloghoster.net/ plaform that saves files alphabetically if you need it email me!
Discuss this at my site please Eziner
A big effort has been put into improving DW speed of searching. Visit the mailing list archives for details and try the latest snapshot to get a first hand idea of the improvements. Its very unlikely such a system as you describe would be included in DW as DW is language and alphabet agnostic. Also search doesn't just look at page titles but their contents, your system would provide little benefit. Do you have an issue with the AJAX system currently used in DW whereby DW suggests page names as you type? — Christopher Smith 2007-03-15 03:46
PS. Your wiki isn't open to anonymous comments so its not reasonable to ask people to comment there.
I created a simple word counter script which will show the number of words while editing. Feel free to donate if this fulfills your needs. — Andreas Gohr 2006-12-15 21:50
* How much?: $25 USD payable via paypal. contact me: info a@t eziner d0t 0rg I will extend till it done!
this works: http://wiki.flux-cms.org/display/FCKW/Home we use it on our (internal) site - hoberion
Esther's blog plugin takes care of this, right? Yeah, this is solved by Esther's plugin. It works great to create page categories. I guess all that's missing is a tag index and a way to search by tags, but if you keep your wiki tidy, it's more than adequate.
maybe something like del.icio.us
Hello, I'm missing tagging, too. Tags are very cool for search in a messy wiki
The blog plugin is to big for me. Only a tag option and some functions that show the taglist like del.icon.us for embedded in some plase, I like.
I too am missing tagging. I'll add $25 USD to this bounty, payable via paypal. Nick Huntington
The blog and tag plugins have been split into different plugins. Can we/you donate to Esther and consider this closed now? — Viktor Söderqvist 2006-11-16 03:22
No, it's not enough. Esther's plugins are fabulous, but the list of tagged articles are not generated automatically. I hope DokuWiki has a built-in mechanism to handle tagging or categorizing, at least as MediaWiki do. — Roberto Ciang 2007-04-02 14:31
Is the tag plugin working as expected now ? — Christophe Gragnic 2008-01-05 16:31
Hi Werner. I am currently on holiday so wont be able to test this till next week. But of course I am very happy to see this new plugin. Email me privately on how i can send the bounty to you. It would be my way of saying Happy Halloween :)
— Shiva Shankar 2006-10-18 13:31
A way of doing this without re-writing the user manager plugin would be to set config for defaultgroup to something like “none” and set up the ACL in the root namespace for that groupname to have the same access as group “ALL” which is unregistered users or users without a group. Then to see a list of users awaiting approval, an admin navigate to the usermanager page and search for users in group “none”. Edit the user to be part of group “user” or whatever group has some rights according to your ACL.
I know this is not the best solution, as it requires a little more than just clicking a link to approve users, nor does it tell the user that he needs to wait for an admin to approve him. But I think it comes pretty close to what you want with minimal effort :) — David Lorentsen 2007-02-22 16:11
A small note: To inform the user that he/she needs to wait for an approval from “Admin”, the notification mail content can be modified and be sent to the user. — C Ravi 2007-08-13
SOLUTION by Andreas Gohr. The gallery plugin was enhanced to optionally use lightbox style image viewing including the set feature. Everyone using this feature is welcome to donate
{{edits_by>username or IP}}
{{editor>*?username}}, displaying the pages and last date/time of edit by username, or display each and every revision by a username. Now if we can only can only hyperlink every displayed usernames and IP, when clicked will show all the user's edits…dreaming :)Thanks Ryan! I suggest you donate the mentioned $15 USD to Andi. — Esther Brunner 2006-03-09 16:02done, donated 11 EUR ~ $15 USD to andi - — Ryan 2006-06-06 19:12
this is very good things //