Learn more about these different git repos.
Other Git URLs
Currently a project avatar can be uploaded only via libravatar. It would be nice to have an option to upload the image directly to Pagure without having to set up a libravatar account with possibly dummy e-mail address.
While I hear the issue, this is going to be very low priority for me unless someone makes a patch for this :)
How about the ability to specify a project logo URL? most projects have an image either on their website, or in their git repo to their project logo.
This would avoid having to host an extra file
Yeah, I think that would work as well. Even projects that do not have any separate website can host their documentation on Pagure, and could link to docs.pagure.io/whatever/logo.png.
docs.pagure.io/whatever/logo.png
I am not too fan of this one (relying to external resources) as I remember a while back a security issues triggered by pointing to malicious content on an img tag.
img
While I'm not fan of hosting more files, it would at least allow us to check that said file is really an image.
+1 for this feature request
also to add that this could as well be implemented for user avatars in order to completely remove the libavatar requirement on the users
i thought about this a bit myself and it seems that the "releases" page already allows uploading an unlimited number of files of any filetype - so really, implementing this feature would not require any new functionality but is more a matter of constraining a feature pagure already facilitates
note that the semantics of this should change with the repo namespacing feature where the avatars would be more sensibly associated with a user or a team group rather than a single project
How does changing the avatar even work, anyway? You get redirected to a 3rd party website which looks stale and apparently works only half-way (try clicking the "Persona" link there), you get to use your OpenID, upload a picture there, it apparently assigns a picture to your id... Then what? Please, at least consider adding a "?" at the "Change avatar" button explaining the process. There's no user-friendliness in this. Also, explain the process in this thread so that it is documented somewhere.
I think https://secure.gravatar.com/ does a nice job explaining what they do/offer.
How does one get from https://www.libravatar.org/account/login/ to https://secure.gravatar.com/ ?
Sorry, I guess I should have pointed to https://wiki.libravatar.org/description/
Basically, they are two different application offering the same service byt libravatar is FOSS while gravatar isn't.
Thanks for the pointers.
related to #3125
4 years since last update, but let's put it into the backlog for 6.0 for now and decide later if and how to proceed
Metadata Update from @wombelix: - Issue set to the milestone: 6.0 - Issue tagged with: RFE
just to note, that this feature is essentially the same feature as the one that Dominik closed as 'wont-fix' on the same day - whatever the rationale to retain this feature request, and to reject the other, is not rational - the same rationales apply equally to both features
every instance of pagure has a running web server necessarily - all that these two features (#469 and #970) entail, is to allow uploading files, outside the VCS - they could all be destined for the same directory like ~/project/www - the remainder of the features is only their relatively trivial HTML representations
@billauger thanks for your feedback, as I tried to explain in https://pagure.io/pagure/issue/5372, labels not always fit and when going through such a massive amount of tickets, it might happen that I make a mistake by closing one with a specific label by maybe leave another, very similar, open. We are all humans, I just try to help identifying what's still relevant and put it in the milestones for the next minor / major release.
After checking https://pagure.io/pagure/issue/469, my thinking behind leaving this one open but closing 469: Being more flexible when it comes to uploading an Avatar without libravatar, that sounded like something which is probably relatively easy to implement and valuable from a self-hosting perspective. Providing a Pages feature is interesting but based on the discussion and the limited resources of the pagure project right now, I had the impression that for now there are other things to focus on.
On Wed, 25 Jan 2023 08:59:29 +0000 (GMT) Dominik wrote:
Providing a Pages feature is interesting but based on the discussion and the limited resources of the pagure project right
indeed, that would consume much more disk space; but pagure.io instance would not need to host the web space
from a self-hosting perspective, the feature could be very simple, as simple as the "docs" link - simply display a "downloads" link in the navbar, pointing to any arbitrary HTTP URL, IFF set by the project admin
the local admin could simply expose local files to the local webserver; or run an FTP server for others to upload
pagure.io project admins would need to maintain their own web/FTP space on another server, obviously
On Wed, 25 Jan 2023 08:59:29 +0000 (GMT) Dominik wrote: Providing a Pages feature is interesting but based on the discussion and the limited resources of the pagure project right indeed, that would consume much more disk space; but pagure.io instance would not need to host the web space
I was actually more referring to limited development resources. The issue was open since years and due to recent decision the amount of contributor reduced even more. So my worries are more if we are able to develop and deliver that feature in an appropriate time.
But I see that you are not agree with closing https://pagure.io/pagure/issue/469, so let me re-open and put it on the 6.0 milestone for further discussion and decide later.
Log in to comment on this ticket.