I’m considering participating in GSoC’24 with GIMP. The mentors suggested using this as a backend for authentication in the project, and I’m eager to delve deeper into it. Can someone provide me with additional resources to further my understanding?
- backend for what?
- wouldnt it require that pixls.us has agreed to be used as a backend in the first place?
4 Likes
Apologies, I should have provided a more comprehensive description.
The project I am interested in working on is outlined here: GIMP Developer - Project ideas for internship programs.
Pat David and Jehan are mentoring for this project, both of whom are from the GIMP organization. They suggested that pixls.us could be a suitable alternative for this endeavor. I need to delve deeper into exploring pixls.us to determine its feasibility as a backend. However, further exploration and confirmation of permissions are necessary before finalizing this decision.
I am not one of the people who would need to authorize this backend, but I think you need to really describe what “backend” means to you and your project.
From the project readme:
“As for comment or notation, if we ever want this (we might), Pat David
from pixls.us told us we could make use of their infrastructure.
Therefore we may be able to have mostly static pages which comments
handled by pixls.us infra.”
Does “using” the infrastructure mean having information housed on pixls.us, or does it mean copying the infrastructure to set up a separate site that works like pixls.us?
So, one of the use case will be instead of making the authorization separate, we plan to use pixls.us for it. Similar to how we use google authentication.
So you want to store XML files for GIMP extensions and some pages to access them on pixls.us? Is that correct?
I guess this is not the case, for that the database of GNU will be used. Just for the purpose of signup and login on the website by admins, reviewers etc would use pixls.us. I might be wrong, but this is what I understood as of now.
OK, I guess your next job is to confirm that this is what you are seeking.
BTW, welcome to the forum.
Thanks!
This will need a lot more details clarified before we agree on hosting anything.
It sounds like @patdavid is the one that suggested whatever the use case is, so it is probably best to continue with him.
He is not only a member of the GIMP community, but he also is a moderator (and I think also site admin?) here.
It sounds like he was suggesting that you somehow leverage the pixls infrastructure, not the forums themselves, but again, I think it’s probably best if you continue working directly with him and he can coordinate with the other admins since he has a much better idea of your requirements/needs.
1 Like
Hi!
I’ve discussed this with @darix and @paperdigits briefly.
It certainly makes sense if GIMP is going to continue to leverage GNOME infrastructure, such as their discourse instance, it might be better to use that forum as a sign-in authenticator. This way users would already have accounts to be able to communicate in the forums there.
In much the same way, I imagine this would facilitate pointing users to issue trackers for bug reports as well, which is a good thing ™.
I am happy to help the gnome discourse team set this up for you if they’re ok with it.
If we were to consider doing it here, we’d want to clearly state what the details would be for implementation and what the expectations would be as well. There are some concerns around privacy and resource drain for us (we already stretch @darix really thin, both mentally and patience 
).
I’ll respond to this in more detail on the gnome gitlab repo for the gsoc project so we don’t make too much noise here unnecessarily.
[edit]
I’ve been advised it would be helpful to include a link in case anyone wants to follow the discussion. So here it is on the gnome gitlab: Authorization/Login credentials approach (#5) · Issues · Infrastructure / gimp-extensions-web · GitLab
2 Likes