snowdrift/tasks
12
1

Add use of paywalls within FLO to funding notes #243

Open
opened 2019年01月29日 07:14:17 +01:00 by snowdriftimport · 3 comments
snowdriftimport commented 2019年01月29日 07:14:17 +01:00 (Migrated from gitlab.com)
Copy link

Perhaps at https://wiki.snowdrift.coop/market-research/history/software or at https://wiki.snowdrift.coop/about/existing-mechanisms

Example: Ardour is FLO but uses a paywall for binaries despite it being perfectly fine to share the product out in the world.

Example: Blender is 100% FLO without compromise and puts out FLO assets (files / moves / resources), but the assets are behind a subscription paywall despite being FLO licensed (noting also that third-party proprietary assets are common and there might be some tie-in to the core ecosystem)

In other cases, there's not even a paywall but just the implication of one. Core issue: spreading the idea that paywalls make sense, that pay-for-access should be (or at least is) normal. But it's not actually a true wall, except it's not presented as a voluntary "suggested" donation either, it's presented flat-out as a price.

Question is not only whether this is effective at getting funding but whether it limits adoption. It's possible it actually increases adoption in the cases of people discounting the value of anything donation-based or otherwise gratis, but it's likely that this turns away many potential folks who would have given things a try if not for the apparent barriers.

Make sure our market research or discussion references this

Related are split-resources style of open-core for whole projects:

Example: Musescore has 100% FLO desktop app but it is tied in with proprietary web and mobile apps and proprietary add-ons store

Perhaps at https://wiki.snowdrift.coop/market-research/history/software or at https://wiki.snowdrift.coop/about/existing-mechanisms Example: Ardour is FLO but uses a paywall for binaries despite it being perfectly fine to share the product out in the world. Example: Blender is 100% FLO without compromise *and* puts out FLO assets (files / moves / resources), but the assets are behind a subscription paywall despite being FLO licensed (noting also that third-party proprietary assets are common and there might be some tie-in to the core ecosystem) In other cases, there's not even a paywall but just the implication of one. Core issue: spreading the idea that paywalls make sense, that pay-for-access should be (or at least is) normal. But it's not actually a true wall, except it's not presented as a *voluntary* "suggested" donation either, it's presented flat-out as a price. Question is not only whether this is effective at getting funding but whether it limits adoption. It's *possible* it actually increases adoption in the cases of people discounting the value of anything donation-based or otherwise gratis, but it's likely that this turns away many potential folks who would have given things a try if not for the apparent barriers. Make sure our market research or discussion references this Related are split-resources style of open-core for whole projects: Example: Musescore has 100% FLO desktop app but it is tied in with proprietary web and mobile apps and proprietary add-ons store
iko commented 2019年04月26日 02:16:37 +02:00 (Migrated from gitlab.com)
Copy link

assigned to @wolftune and unassigned @snowdriftimport

assigned to @wolftune and unassigned @snowdriftimport
davidak commented 2021年02月15日 03:23:58 +01:00 (Migrated from gitlab.com)
Copy link

good point. there are also pay-what-you-want models which could be considered a kind of paywall, since you have to pay, but the price can be 0 in most cases

examples are elementary OS and the elementary AppCenter

good point. there are also pay-what-you-want models which could be considered a kind of paywall, since you have to pay, but the price can be 0 in most cases examples are elementary OS and the elementary AppCenter
davidak commented 2021年02月15日 03:38:54 +01:00 (Migrated from gitlab.com)
Copy link

I did a quick research and found GitRoyalty (the first open source paywall).

I did a quick research and found [GitRoyalty](https://gitlab.com/snowdrift/snowdrift/-/issues/572) (the first open source paywall).
Sign in to join this conversation.
No Branch/Tag specified
master
master-pre-reset
v0.1.4
v0.1.3
v0.1.2
v0.1.1
release-0.1.0.1
Labels
Clear labels
Blocked
Confidential
We track some issues in a private repo, typically when they contain personal information. In the interest of transparency (and ease of tracking for us), we also keep a stub here in the public issues.
design
Visual design and assets
dev
dev/frontend

Archived

docs
Documentation
finances
Management of financial accounts; Grants and other funding sources
good first issue
Issues that do not require in-depth understanding of background or code
governance
Organisational structure and bylaws
legal
Legal terms, policies and documents
needs-info

Archived

ops
Operations
outreach
Community messaging and recruitment
product/blog
For the blog / Ghost
product/crm
For the CRM / CiviCRM
product/elm-site
Relates to https://codeberg.org/snowdrift/elm-website
product/forum
For the forum / Discourse
product/wiki
product/yesod-site
Relates to https://codeberg.org/snowdrift/snowdrift
research
Research, reference materials and studies
security
Issues about authorisation and authentication
type
bug
Broken feature or regression
type
chore
Housekeeping
type
feature
New feature or functionality
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
snowdrift/tasks#243
Reference in a new issue
snowdrift/tasks
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?