inspired by http://moinmo.in/MoinBounties

This Bounty Programme 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 for 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' (monetary) value is not too low. Of course small changes are carried out for less money than changes which require more effort.

• List the bounty below under “open bounties”
• specify exactly what you want to offer money for
• specify exactly how much funds you offer (please use USD or EUR)
• specify exactly how long your offer will stay open (date)
• specify exactly who you are (including contact information)

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

• They will discuss with DokuWiki development core team how to proceed best for starting implementation.
  • If the task is implemented as a plugin, this is mainly to talk about how it is done best.
  • For the case the task needs changes to core code, it is mainly to discuss if this is needed and wanted.
  • The contacts person of the contracting group (mostly a subgroup of the core team) will contact the funders and invite them for paying some initial rate (50%). He/She will clarify outstanding issues at this point.
  • The feature will be implemented and after it is done, the final rate will be demanded (50%).
  • The resulting code should be based on current code and must be publicly released under the GPL after funds are transferred.
  • If not all funders want/can pay the initial rate, the whole bounty will be rolled back including the transfer of money if necessary.

The Code (2) Syntax Plugin has not been updated since late 2008, and as a result only provides minimal functionality (with Hrun, I get nothing but the CSS applied to the blocked text). Email to the author has bounced.

This bounty is to update the Code2 plugin to work properly with the current release of Dokuwiki.

Offer: $100USD via PayPal

Offer open until end of 2014

Contact: tstout [at] lv [dash] 426 [dot] net

— I take this task. — Constant Illumination 2015-05-13 12:37

• Task 1: Duplicate the functionality of the clade and Cladex templates from Wikipedia. Ideally, the syntax will be compatible with the Wikipedia template (possibly with a small find-and-replace pass if necessary).
• Task 2: Leave suitable hooks so that the displayed result can be easily manipulated using a custom css style.
• Plugin should not cause any clashes with the exttable plugins, which use vaguely similar syntax.
• I (Ashtagon on the DW forums) am willing to offer 50 GBP (about 80 USD) for this to be completed by end of January 2014.

• Task 1: Improve either the (old) pagemove plugin, or the openas plugin, or the editx plugin, so that any page can be moved including its history, and with updating all links to this page inside the wiki.
• Task 2: Make sure that this also works for an entire namespace. (Can be done by moving pages after each other - however some measures might be required against undesired effects such as repeated history entries, …)
  • This was also required on the editx discussion page: action_on_namespaces
• Manuel would offer 150 EUR for this, within 3 years from now: July 2015, contact: info06 at manuelbuser (.) ch
• Who else?

This bounty is similar to pagemoveng, we had a very good application for that idea for GSoC 2011 but the student decided to work for another mentoring organization. This means we have already some ideas and concepts how this could be implemented. You can find some of these things linked on the page of the idea, if there is anything missing feel free to contact me (due to lack of time I'm currently not interested in implementing this bounty myself). — Michael Hamann 2012/07/09 22:54

Thanks Michael, good to hear. This pagemoveng concept is more complete, so I'd increase my contribution to 200 EUR for the person implementing it — Manuel

I would add 50 EUR, within December of 2013 for the person implementing it ! – Martin

I would add AUD $100 (about $100 USD) for implementation of this before Dec 31 2013. – Lewis (liaung.yip@ieee.org)

I plan to implement this bounty. I started to work on the pagemove plugin some months ago and fixed the main problem. I'm going to focus on some still missing details and namespace moves during the next days/weeks. As soon as I'll have something ready to test I'll contact the people listed here. The current state can be found in my fork of the pagemove plugin. — Michael Hamann 2012/12/18 22:07

More details: https://forum.dokuwiki.org/post/36186

• issue date: Nov. 1, 2010
• I'd offer 150 EUR when this is completed. Of course - other people interested should also contribute financially…
• Possible AIP inspiration could be obtained from an absolutely mini Wiki with git backend, also written in PHP. see:

git clone git://el-tramo.be/wigit, index.php only 10 kB, contains git API.

• also refer to bounties
• Contact via maris dot rob AT vdi.de
• Offer is open until 31 dec 2010, if started at that time: is still Okay, provided the path takes a few months or less.

A recent plugin seems to do this job, isn't? GitBacked Plugin

• March 1, 2010
• Given two dates (one in the past, and the other is usually today) I need to see what all has happened on the specific page or namespace even.
  • Means to display the differences must be concise, clear and easy to scan through…
• As this is important to me, I am willing to offer $200.00 US to get this started. No funny stuff - PayPal when it gets completed.
• My offer is on the table until it gets fulfilled, or I pull it from this page (will give warning here first)
• My contact is hiflyer.x {over_at} gmail {dot} com & I would be willing to answer further questions when contacted.

• Specification: I wish to use a query of data plugin to specify the items of a “select” field, project numbers for example. Is it possible, to use a data-table for selection and display more than one column and enter only the first one to the template?
• Background: I stored project data via data plugin and assign wiki pages for documents to project numbers. I create new document-wiki-pages via bureaucracy form. In current state, I use a textbox to enter the number of the project. This means, that you need always a list of all projects to identify the required project number. I think it would be best to have a select field with 2 or more columns. In this case with project number and project title for example.
• Payment?: 50 Euro (via PayPal or EU bank transfer)
• How long?: December 31, 2009
• who am I?: Jörg Ferlein, ferlein [at] infodok [dot] de
• OTHERS: Please add money to this bounty, if you want it too!

• what for?: “XSS vulnerability allows arbitrary JavaScript insertion.” Please fix this so the plugin can be used safely, provide an archive (zip or tar.gz) for convenient installation → exttab2
• payment?: 25 Euro (via PayPal or EU bank transfer)
• how long?: August 31, 2009
• who am I?: helmut [dot] giritzer [at] gmx [dot] at
• OTHERS: Please add money to this bounty if you want it too!

The author submitted a fix for this XSS-issue. http://www.dokuwiki.org/plugin:exttab2?rev=1273755792&do=diff

I have a site that uses ELGG, Vanilla Forums and DokuWiki - often embedded in the same page. The main login for the site is under ELGG and I have managed to get Vanilla Forums to use the ELGG login okay. The problem and the job is to get DokuWiki to use the ELGG login. The only requirement is that DokuWiki checks that the visitor has already logged in via ELGG.

Offer: £150 via Paypal

Offer open till Jan 1 2009

Contact: jededitor@gmail.com

The field is in the SQLite DB- it just needs supporting in the query syntax. Minimum: support queries for less than a certain date (e.g. to find overdue tasks) Ideally: support date ranges e.g. datefrom=2013-10-01&dateto=2013-10-31 would be a hack but acceptable

Offer: EUR100 via Paypal

Offer open till 2013-12-31

Contact: craig@sussol.net

• Bounty: Create a plugin (or modify core code) so that results to a search query are confined to the current namespace. More information here.
• Reward: $100 USD via PayPal
• Open until: 31 January 2010
• Who I am: Chris Sutton (chrispsutton AT gmail.com)

nssearch

• Actually : I use ACL to permit, hide or protect the pages according to users and group administrated with ACL. It's nice but the problem is that anyone who can edit a page can manage (or see, or use) all the images or documents stored in the media directories. Without restriction.
• Example : On a personal site, I present myself and some activities on a wiki, and on hidden pages I deliver some documents (copy of passports, and other PDF.). But I would allow some edit possibility
• Specification: I wish to protect the media. The more simple way could be to assign the same limitation (as these applied to the pages) to the same directories under media (according to their names). So if, the page -dir1:dir2:pageA- is forbidden for “Smidt” then the directory “media/dir1:dir2:pageA” should also be invisible or forbidden to the same “Smidt”.
• Payment?: 30 Euro (via PayPal or Moneybooker)
• How long?: March 31, 2009
• who am I?: Rolando Livet, Paris : rol2010 at rolsys dot com
• OTHERS: Please add money to this bounty, if you want it too!

ACL rules apply to media files as well - if you read protect a namespace foo:bar then all media files inside media/foo/bar are protected too. Maybe you have some errors in your ACLs? — chi 2010/01/19 11:58

Well, You are right. Thank you “chi” for your quick answer. Rol . (rol2010 at rolsys dot com)

• what for?: Using Lightbox for single image links like the: {{http://de3.php.net/images/php.gif?200x50}} link syntax (In other words: Not with the gallery plugin where you have to upload the images to the server first). Meaning we can use the lightbox feature for off-site images as well as with images on the server. (Preferably version 2 of lightbox)
• payment?: 25 Euro
• how long?: May 2007
• who am I?: — Mark Maas 2006-05-01 13:08
• OTHERS: Please add money to this bounty if you want it too!
• SOLUTION: LightBoxv2 by ogeidix

• what for?: Integrate Lightbox v2.0 into DokuWiki using a syntaxplugin, Especially the “Image set” capability is very important to me at least.
• payment?: 25 Euro payable via PayPal. Mark Maas
• how long? Until a new lightbox version is out
• who am I?: Mark Maas, systems admin. Would love this for his homepage.
• OTHERS: Please add money to this bounty if you want it too!

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

• what for? I'd like a plugin to that lists all contributions from a particular user, such as

 {{edits_by>username or IP}}

• payment?: $15 USD
• how long?: May 2006
• who am I? Ryan Knoll, US resident, ryanknoll @at@ yahoo @dot@ com, not affiliated with any company. Can pay with PayPal or other reasonable means.
• OTHERS: Please add money to this bounty if you want this feature too!

• SOLUTION by Esther: Blog plugin can now display {{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 :)
  • NOTE It appears that this functionality is no longer in the current version of the blog plugin (at least there is no mention of it on the page and grepping the source for editor gets no matches). – AdamShand

Thanks Ryan! I suggest you donate the mentioned $15 USD to Andi. — Esther Brunner 2006-03-09 16:02

done, donated 11 EUR ~ $15 USD to andi - — Ryan 2006-06-06 19:12

this is very good things

• what for?: Managing large tables. Current syntax is too cumbersome to edit if there are multiple rows. It was discussed on the mainling list
• payment?: 25 Euro
• how long?: Dec 2006
• who am I?: — Shiva Shankar 2006-09-19 17:53
• OTHERS: Please add money to this bounty if you want it too!
  Shiva, please look at exttab1 if this goes in the direction you want

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

Hi,
I've recently set up a wiki (http://www.songtranslator.net/lyrics) which offers translations into English of song lyrics in Spanish. Although DokuWiki syntax can hardly get any simpler, I think that, seeing as though practically all my pages have exactly the same layout, it would be great to set up a form which would create a new page and wrap up the contents of the form in DokuWiki syntax.

The format of each lyrics page is:

====== Song Title ======
Artist: //[[Artist]]//\\
{{youtube>small:youtube_video_code}}
<exttab1>
{| cell width="100%"
|First line of lyrics in Spanish
|
|-
|Next line of lyrics in Spanish
|
|-
|Next line of lyrics in Spanish
|
|-
|Next line of lyrics in Spanish
|
|-
(... etc)
|}
</exttab1>

(the empty lines on the right hand side of the table are for the translators to insert their translations)

A form which could gather the song title (which would also be the pagename), the artist, YouTube link (optional) and the lyrics line per line, create the page and then publish the form contents all wrapped up in the syntax above using a template would be much cleaner and easier to use than using the addnewpage and pagetemplate plugins or any of the blog plugins.

There are already various form plugins which output to e-mail (conform, contact, form and bureaucracy) and other wikis have similar plugins (http://twiki.org/cgi-bin/view/TWiki/TWikiForms or http://www.mediawiki.org/wiki/Extension:Semantic_Forms)

It would be convenient to be able to configure the hidden fields of DokuWiki syntax which the form contents are wrapped up in so as to adapt it to any kind of page layout, and if someone attempts to create a page which already exists there would have to be some mechanism to avoid overwriting.

Offer: 100€ via PayPal

Offer open until end of November 2008

Contact: smith [dash] robertson [at] adslmail [dot] es

Thanks!

Implemented by modifying the bureaucracy plugin and money received. I try to get the changes into the upstream distribution of the plugin. If the plugin author refuses to integrate the changes I'll post the plugin on the plugin pages. — Michael Klier 2008/11/22 15:43

The Roundbox template has not been updated since the 2005-11-12 DokuWiki release, and as a result the mediamanager no longer works well with it. The author has indicated he is no longer active in DokuWiki or PHP development and doesn't plan to maintain the roundbox template any longer.

This bounty therefore is to anyone prepared to update the Roundbox template - as a minimum to make the mediamanager functional, but ideally to update any other appropriate areas to make it compliant with the current DokuWiki release.

Offer: 40€ via PayPal

Offer open until end of 2008

Contact: geoff [at] sokoll [dot] net

This was implemented and included in the 2009-01-26 version of roundbox — Don Bowman 2009/10/18 13:23

• Specification: I would like to create tables which have a column within continuous numbers like e.g. in Excel.
• Example:

• Payment: 25 Euro (via PayPal or EU bank transfer)
• How long/valid until: on hold (currently evaluating possible solutions)
• Who I am: Michael Zeidler, twisteeer [at] web [dot] de
• OTHERS: Feel free to add money if you like to have this bounty too.

Solved with the Autonumbering Plugin. Many thanks to Pat Brown for this recommendation and his time for detailed clarification. — Michael Zeidler 2015-05-11 16:12

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:

• make a change to a document at any particular release
• changes are merged “upstream” to later releases automatically
• conflicts are flagged within the DokuWiki interface for manual resolution
• can still revert back to prior versions as usual with changes propagated upstream
• without leaving the DokuWiki interface

Just for ideas: git in the backend?

We are offering 300 Euros.

This offer will stay open until 17th December 2007.

Ton Voon ton [dot] voon [at] altinity [dot] com

• I would like a word count function that counts the number of textual words on the page.
• How much?: $20 USD payable via PayPal
• Offer open during the months of August and September 2006. I need the word count feature, especially, for the semester beginning in September.
• Who am I? Professor of Law, Criminal Justice, and Writing at Rutgers and Rowan Universities (and SAHM) junk AT hillaryburgess DOT com. Please include “Wiki Word Count” in the subject of your email.
• Others: Please offer to contribute to this function.

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

• I would like a page info function that creates a page on the fly that contains the following information: Last Modified, Last Author, Page Version (Page version is the number of different pages saved), Markup (Markup is the number of significant changes), Size (in kilobytes), Hits(number of times the page has been viewed), number of paragraphs in the document, number of sentences in the document, average sentences per paragraph, average words per sentence, and most importantly word count (the number of textual words on the page).
• How much?: $30 USD payable via PayPal
• Offer open during the month of August 2006. I need the word count feature, especially, for the semester beginning in September.
• Who am I? Professor of Law, Criminal Justice, and Writing at Rutgers and Rowan Universities (and SAHM) junk AT hillaryburgess DOT com. Please include “Wiki Page Info” in the subject of your email.
• Others: Please offer to contribute to this function.

• I want 2+ users to be able to edit a single page via partial page edits of specific sections. I have outlined two methods in which it can be done. It seems this may not be a simple plug-in but a rewrite of part of the core? Can some authors comment on this at the link listed? In which case I'd like to discuss with you the best way to do it and bounce it off some of the authors of DokuWiki.
• How much?: $45 USD
• My offer is open through July 2006… or until I just do it myself. Contact me.
• Who am i? Resident of Berkeley, CA, USA. Tim Hon. (my firstname) –at– simulat —|dOt|— c0m.
• ANYONE ELSE WANT THIS FEATURE? I KNOW THERE MUST BE A BUNCH OF PEOPLE. ADD A BOUNTY TO THIS:

• This would be very useful in group editing/whiteboarding situations. I will add USD $50 PayPal dollars to this bounty. Since the previous bounty may currently be expired, I will extend through March 2007. – Pierre Omidyar (first[at]last[dot]net)

* How much?: $25 USD payable via PayPal. contact me: info a@t eziner d0t 0rg I will extend till it done!

• what for?: functional WYSIWYG similar to MoinMoin's WYSIWYG, preferably implemented as a plugin. There is a WYSIWYG started but it seems not to work (doesn't save pages properly)
• payment?: $25 USD
• how long? May 2006
• who am I?: Ryan Knoll, US resident, ryanknoll @at@ yahoo @dot@ com, not affiliated with any company. Can pay with PayPal or other reasonable means.
• OTHERS: Please add money to this bounty if you want it too!
  • I add 10 EUR via PayPal Konrad Bauckmeier 2006-01-19 09:00
  • I also add 10 EUR via PayPal Alexander Kucera 2006-04-28 10:22
  • I also add 100$ CDN via PayPal Jonathan Kelly 2006-04-05
  • I also add $15 USD via PayPal junk AT hillaryburgess DOT com
  • I also add €10 via PayPal PDD 2006-11-06 20:48

• Your have test this? http://apassant.net/blog/2006/06/25/96-integrate-fckeditor-in-dokuwiki.
  • Has anyone tested this fckeditor? How well does it work? Are internal links still easy to create? Thanks!
  • A closer read of that FCKeditor in DokuWiki posting says that it doesn't write wiki syntax, but instead writes HTML. It inserts beginning and ending HTML tags around the edited section. I'm thinking about whether this a good or bad thing. My experience with doing large tables in wiki syntax is that it's pretty messy (especially when doing colspan or rowspan activities), so doing the basics in Nvu and copying over into an HTML section of a wiki is somewhat of a relief. If you already have a lot of wiki syntax, then you could end up with pure wiki syntax pages and pure HTML syntax pages. - David Ing, 2007/01/22

this works: http://wiki.flux-cms.org/display/FCKW/Home we use it on our (internal) site - hoberion

• I like to add Tags to pages and find them in DokuWiki like described here in Mailing List
• payment?: 20 EUR
• how long?: May 2006
• who am I? Konrad Bauckmeier 2006-01-19 09:01, German. Can pay with PayPal.
• OTHERS: Please add money to this bounty if you want this feature too!

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 place, 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

• what for?: Config option for registration approval- lets you leave “auto-register” on, but new registrations require admin approval. Saves admins time of adding new users- when clicking an approve link is much preferable. We need this for our Intranet IT-only documentation wiki.
• payment?: $100 by Company check
• How Long?: Mar 2007
• who am I?: — Matt Wilbur 2007-01-03 22:05
• OTHERS: Please add money to this bounty if you want it too! - or if I'm a bonehead and you know a non-feature-adding way to do this, that works too. I won't offer $100 just to point out that I am a bonehead, just for a reliable and part-of-DokuWiki solution :)

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