Would like to take you on on that offer. I will set up a branch to be used
for porting (I have a preferred starting point, not current trunk).
Strategy wise I believe we need to go to Gtk3 before we can go to Python3,
so that will be 2 phases.
For the first step going to Gtk3 I would like to split up the application
in modules. Trying to get the basic application running first, than port
additional modules and plugins one-by-one.
Let's simply use a wiki page to track progress and who-does-what. I prefer
(private) email for quick questions / discussions.
Is this what you had in mind?
On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek <janousek.j...@gmail.com>
> > Yes, I have plans to port zim to python 3, but can't commit to a concrete
> > timeline on this moment.
> I might help with the porting to Python 3 & GTK+ 3. What is the best
> place to discuss the strategy? Mailing list, bug tracker or Launchpad
> blueprints? I prefer the bug tracker.
> Best regards,
> Jiri Janousek
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : email@example.com
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help : https://help.launchpad.net/ListHelp
Mailing list: https://launchpad.net/~zim-wiki
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~zim-wiki
More help : https://help.launchpad.net/ListHelp