Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Source, 100% Free, Trial/Limited flags #3533

Open
2 tasks done
Mugane opened this issue Oct 24, 2024 · 3 comments
Open
2 tasks done

Open Source, 100% Free, Trial/Limited flags #3533

Mugane opened this issue Oct 24, 2024 · 3 comments

Comments

@Mugane
Copy link

Mugane commented Oct 24, 2024

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

It is really tedious to have to install dozens of different applications one by one to evaluate if they are feature limited in some way. Take diff tools for example. choco find diff returns over sixty (60) results.

Describe The Solution. Why is it needed?

I propose a unique tag (string flag) that can be used in find results to filter out software based on the license/feature category:

1.a. [#OS] Open source
1.b. [#CS] Closed source (proprietary)

and

2.a. [#FFF] Free (fully functional)
2.b. [#FTL] Free (time-limited)
2.c. [#FFL] Free (feature-limited)

Or something like that. The important thing is that they are unique, and appear in terminal search results for grep filtering.

Each package would have a tag for each of 1 and 2 to cover all the combinations of properties. E.g. WinMerge would have #OS #FFF since it's open source and the open source version is fully functional while GitLab CE would have #OS #FFL since even though it claims to be open source, it has only a subset of features of the full GitLab Enterprise version.

Additional Context

This would be invaluable in saving time selecting open source tools that always seem to claim that designation these days but are very frequently limited in major ways when there are paid versions available. I don't care about how people collect money, but I do care about having that information up front. What an absurd practice, btw - who would ever start paying for software they thought would be free after they spend hours setting it up to discover such a rug-pull deep in the greyed out settings? But that is the world we live in.

Related Issues

No response

@pauby
Copy link
Member

pauby commented Oct 28, 2024

The answer to this is very much the same as that in #3497. I don't want to just repeat everything in there so I'm happy to respond to any particular points mentioned in there.

@Mugane
Copy link
Author

Mugane commented Oct 29, 2024

The answer to this is very much the same as that in #3497. I don't want to just repeat everything in there so I'm happy to respond to any particular points mentioned in there.

I'm honestly not seeing any correlation whatsoever

@pauby
Copy link
Member

pauby commented Oct 29, 2024

I propose a unique tag (string flag) that can be used in find results to filter out software based on the license/feature category.
Each package would have a tag for each of 1 and 2 to cover all the combinations of properties. E.g. WinMerge would have #OS #FFF since it's open source and the open source version is fully functional while GitLab CE would have #OS #FFL since even though it claims to be open source, it has only a subset of features of the full GitLab Enterprise version.

I'm honestly not seeing any correlation whatsoever

The questions I was asking, and I believed I answered over on #3497 was:

  • Who would you see being responsible for adding all the tags?
  • Who would you see as being responsible for ensuring the tags are correct?
  • Who would you see as being responsible for handling discrepancies?
  • Who would you see as being responsible for correcting tags when they are wrong?
  • Where would you see the information on what tags to use (i.e. what categories the software falls into)?
  • Who would be responsible for deciding the edge cases?

This would be invaluable in saving time selecting open source tools that always seem to claim that designation these days but are very frequently limited in major ways when there are paid versions available.
who would ever start paying for software they thought would be free after they spend hours setting it up to discover such a rug-pull deep in the greyed out settings?

Would that not be the responsibility of the user to ensure that they software they are spending hours setting up, is what they want to spend their time on? As this is specific to each individual, would it not be better for them to decide what they will and won't accept?

There are tags that can be used on packages today, which some use. trial is one of them. Tags are not strictly defined or their use mandated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants