Wikidpad still maintained?

[Bjorn]

Hi all, 

Is wikidpad still maintained?

I saw that the last commit was over a year ago.

/bjorn

[Bastian Weber]

I think this is a valid question. There is also a discussion of that
topic right now in a github issue with some recent activity

https://github.com/WikidPad/WikidPad/issues/69


Here is my contribution to this discussion:



## Wikidpad Sustainability


First of all, I owe wikidpad a huge deal of my current life quality. I
probably would not have finished my PhD without this tool and maybe I
would have gone crazy due to information overload. So, dear Michael, and
all other contributors thank you very much for providing this great tool to
the world. It deserves way more attention!

My wiki has several 1000 pages and keeps growing. This means I heavily
depend on it. I hope to use wikidpad over the next five years or
probably much longer.

Recently I was affected by https://github.com/WikidPad/WikidPad/issues/61.
Wikidpad did not start at all. Luckily, I had some time to fix that, but
there are days on which such an incident would cause serious trouble.
While figuring out the background of this problem I realized that the
project activity currently is quite low: Latest News [1]: release of
2.3rc2 from 2018-11, several open pull requests, with now or low
discussion activity, several open issues.

I have the fear that I soon might depend on some orphaned software and I
have a quite strong incentive to prevent this. I totally understand that
maintaining a free software project consumes a lot of time and mental
energy and that there are a lot of other activities in life which are
much more important and probably more fulfilling. In fact I am a strong
advocate that free software needs sustainable funding <off-topic> See my
activities in this regard: [2] </off-topic>! So, to be very clear on
that: this message is not meant as criticism. I is an attempt to support
wikidpad, such that it continues to be useful for its current and
probably many future users.

I suggest the following:

- Consider to publish version 2.3 as stable version

- Close old issues (e.g. like
https://github.com/WikidPad/WikidPad/issues/13) and pull requests.
Encourage initial authors to open a new one if they think it is appropriate.

- Update the website an point to the github repo

- Deprecate sourceforge. It has IMHO a bad reputation and seems
redundant to github. And it seems to not support https which leads to
"unsafe-warnings" in some browsers.

- Consider to move the wiki from http://trac.wikidpad2.webfactional.com/
(last change 2015) to github (or completely drop it)

- Consider to include docs in the project repo and ship the on
https://readthedocs.org/ automatically (with web hooks)

- Reduce the amount of branches (currently 22)

- Make wikidpad installable via pip

- Complete the port to python3 (maybe drop python2 support for that)

- Introduce continuous integration (travis, drone.io, ...)


Obviously these actions would take quite a lot of work, most of which is
rather boring but nevertheless important. It would be unfair and
unrealistic to expect the maintainer to accept such a task list from
some random dude like me and euphorically start to work. Instead I
suggest the following:

- Gather people who are interested in keeping wikidpad acitve (and
improving). E.g. by contacting all people who have starred or forked the
repo.

- Collect reliable pledges from these people (E.g. "I will contribute at
least 5 hours of work until 2021-03-31" or "I will provide 10 Euro for
each milestone reached")

- Consider to use external freelancers to do some of the boring stuff
(via Upwork, fiverr, bountysource)

Obviously, I by myself am willing to pledge something: 50 Euro without any
condition, and 50 Euro more if togehter we reach at least 1000 Euro
until 2021-03-31. Additionally, I pledge at least 3 hours until
2021-03-31. In the future until 2025 I pledge at least 25 Euro per year,
in which at least one stable release happens, for general development
and more for specific features like Markdown support
(which I would love to have).


Let me close again with a huge thank to Michael and all other
contributors. Free Software is an amazing civilizing achievement and it
feels very satisfying to be part of that.

[1] http://wikidpad.sourceforge.net/
[2] http://fsfw-dresden.de/funding-foss



Best,
Carsten
PS: The email-address used for this mailing list blongs to an older
spam-prevention identity.... :)






>
> --
> You received this message because you are subscribed to the Google
> Groups "wikidpad-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to wikidpad-deve...@googlegroups.com
> <mailto:wikidpad-deve...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/wikidpad-devel/11a15e73-bfa3-4abe-8e2b-ff113c23f70bn%40googlegroups.com
> <https://groups.google.com/d/msgid/wikidpad-devel/11a15e73-bfa3-4abe-8e2b-ff113c23f70bn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Graham Harris]

Did this go anywhere? I love WikidPad, use it every day, over 13,000 .wiki pages in my 'main' wiki. 

I now have a regression (wikidpad2_3beta16 on Linux Mint 18, based on Ubuntu 16.04) in that I can no longer get to the Extra; Options dialog. I presume something has updated the system python to cause it. I have spent too much time today working on this rather than productively. I get this in WikidPad_Errors.log:

Version: 'wikidPad 2.3beta16' Session start: 2021-07-30 12:27:24

Traceback (most recent call last):

  File "lib/pwiki/PersonalWikiFrame.py", line 1995, in <lambda>

    _(u'Set options'), lambda evt: self.showOptionsDialog(),

  File "lib/pwiki/PersonalWikiFrame.py", line 4751, in showOptionsDialog

    dlg = OptionsDialog(self, -1, startPanelName=startPanelName)

  File "lib/pwiki/OptionsDialog.py", line 852, in __init__

    panel = pn(self.ctrls.panelPages, self, self.pWiki)

  File "lib/pwiki/MainApp.py", line 880, in optionsPanelFactoryWrapper

    return factory(parent, optionsDlg, wx.GetApp())

  File "/home/graham/bin/WikidPad2_3beta16/user_extensions/__init__.py", line 711, in __init__

    langs = [unicode(lang_def[0], "utf-8", "ignore") for lang_def in get_all_lexers()]

  File "/home/graham/bin/WikidPad2_3beta16/user_extensions/pygments/lexers/__init__.py", line 53, in get_all_lexers

    for lexer in find_plugin_lexers():

  File "/home/graham/bin/WikidPad2_3beta16/user_extensions/pygments/plugin.py", line 53, in find_plugin_lexers

    yield entrypoint.load()

  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2229, in load

    return self.resolve()

  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2235, in resolve

    module = __import__(self.module_name, fromlist=['__name__'], level=0)

  File "/usr/lib/python2.7/dist-packages/mako/ext/pygmentplugin.py", line 7, in <module>

    from pygments.lexers.web import \

ImportError: No module named pygments.lexers.web

 I do have pygments.lexers.web in my WikidPad source tree: /home/graham/bin/WikidPad2_3beta16/user_extensions/pygments/lexers/web.py

but I guess the system python is ignoring that, and I don't know python well enough to fix that.  

[Graham Harris]

And like others I would be prepared to pay just to get this stabilised somehow. Docker?