Comments (6)
probonopd
commented on August 28, 2024
Any and all information needs to come from inside the AppImage, or from the location where the AppImage is downloaded from. No additional data should be maintained in AppImageHub. All data should be maintained by the respective upstream authors of the AppImage.
This ensures that all relevant metadata a) travels inside the AppImage along with the rest and b) does not have to be maintained in a central location.
from appimages.scraper.
azubieta
commented on August 28, 2024
Totally agreed with you.
But take for example the case were the developer was to lazy to properly
include a all the data that an user would need. This is the case for most
of the apps we currently have listed at appimagehub.
The idea is to have a fallback mechanisms. Theese community edited
templates could be used by the authors latter to generate AppStream files.
from appimages.scraper.
TheAssassin
commented on August 28, 2024
Perhaps you can convince users to send PRs to those people to add AppStream data? Of course, that doesn't always work, e.g., when they're not using GitHub. But it's a start.
from appimages.scraper.
azubieta
commented on August 28, 2024
That would work too, as you said in some cases.
The feature is already implemented I'm not planning to make it the default
way of gattering information from the appimage files but to use it as a
fallback mechanism.
El dom., 24 de jun. de 2018 8:53 AM, TheAssassin <[email protected]>
escribió:
… Perhaps you can convince users to send PRs to those people to add
AppStream data? Of course, that doesn't always work, e.g., when they're not
using GitHub. But it's a start.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABFdrvFrsJ9SK-NVYRHMAwvjODu9ZGinks5t_5nQgaJpZM4UzMNe>
.
from appimages.scraper.
probonopd
commented on August 28, 2024
But take for example the case were the developer was to lazy to properly include a all the data that an user would need.
I have always had positive experiences with sending PRs (GitHub) or MRs (GitLab) to the respective upstream projects. So I agree with @TheAssassin that this should be the way to go.
from appimages.scraper.
TheAssassin
commented on August 28, 2024
@probonopd please don't forget the other half of my statement, where I explain that this won't work in a lot of cases, e.g., when the software is not developed on github, or the scripts aren't open source.
from appimages.scraper.
Related Issues (1)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from appimages.scraper.