Rethink Krita development fund
Open, Needs TriagePublic

Description

Discussed briefly at the Sprint in 2019.

There are some issues that are wanting to solve with the current system

  1. Manage subscriptions better
  2. Have a donation bar and establish some goals for funding like Blender does
  3. Differentiate normal donations with sponsors
  4. Use some of the ideas from the sprint to determine what features to work on
  5. need to discuss if we want to have bigger higher level goals like "improve text tool", or smaller goals that people can vote on.
ognarb added a subscriber: ognarb.Aug 12 2019, 9:52 AM

With a little bit of looking into things, we are going to need to start having a username and login to manage this information like id.blender.org takes care of.

Do we want to have another log in system just for the development fund, or I wonder if it is possible to tie into a system we already have?

This ID could be potentially used long term for other things like stores and training like blender does. Something to think about.

This definitely needs discussion with the sysadmins. Ben -- what do you think? Basically, we will need to store our dev fund subscribers info somewhere, and allow them to change that themselves.

I think Blender has a standalone authentication site that runs through id.blender.org. The other sites like cloud.blender.org and fund.blender.org use it to authenticate. Those websites can do whatever they want then.

We already kind of do this with Krita.org since it has a LDAP plugin that does something with usernames. I am not sure if we could just just do something similar for a development fund thing.

I also see something like this that KDE uses, but the payment options look pretty limited... https://relate.kde.org/civicrm/contribute/transact?reset=1&id=9
That looks like it plugs into CivicCRM, which I am guessing at this point Krita is probably not going to be using?

KDE is looking for an identity replacement: https://phabricator.kde.org/T8449. I don't know if blender id (https://developer.blender.org/diffusion/BID/) was considered as a replacement or not.

huftis added a subscriber: huftis.Aug 12 2019, 5:53 PM

Sorry for the delay in getting back to you on this.

@rempt Integrating with KDE Identity should be pretty straight forward. Given all the issues we've had with CiviCRM i'm not sure it's a good base to use for this though.
I'm fine with storing that sort of information - we already do this for KDE's CiviCRM.

As far as the last fundraiser, I donated a good bit, but I cannot donate any regular way, besides theta, so, ... idunno.

3 of the 5 above options deal with money. No comment.

rempt added a comment.Aug 31 2019, 7:39 AM

@Metallicow: this won't be a remplacement for one-off donations or yearly fundraisers, but rather an extra option.

@bcooksley : no, I think we shouldn't use civicrm either. We might want to take a look at blender's dev fund code and check whether we can integrate it with identity. I don't think it uses civicrm in the background -- at least, I hope not.

ognarb added a comment.EditedMon, Nov 4, 12:12 AM

I'm doing some using blender id as a replacement for KDE identity. This would allow to get a krita fund based on blender fund 'very easily'.

My work is located at:

The current change between the upstream version and my forks are:

  • branding (KDE identity is WIP, Krita fund is very WIP)
  • using plain HTML instead of pug files
  • using requirements.txt and normal python venv instead of pipenv
  • a WIP branch with 2fa for KDE Identity

@ognarb - thanks for starting to look into this. This could work out pretty well. It sounds like the KDE identity work is still in flux a bit, so maybe this blender ID mechanism is something that could replace the old system.

I don't know all the touch points for the KDE identity stuff, so not sure how hard it would be to change the ID mechanisms. Let me know if there is anything you want me to take a look at or help out with.

ognarb added a comment.Mon, Nov 4, 1:41 PM

The work concerning KDE Identity is tracked in T8449. I already contacted the blender devs some time ago for license clarification and possible upstream of some features (2fa, multiple emails address support), but I didn't have the time until recently to work more on it (moving all the KDE website to php7 and some problems in the mediaWiki instances).