Improvements for spreadtheword page #535
Open
opened 2018-10-06 08:33:41 +00:00 by max.mehl
·
13 comments
No Branch/Tag Specified
master
feat/YH4F-activity
feat/activities
translate-index-galician
ADD-event-20260830-01-01-97124eef77eb3133
redirect_wiki
ADD-event-20260815-01-01-bb0919851d1298f5
test
feat/translations
silviarbgl-patch-2
news-20260708-DMA
feat/lxml-ft
ADD-event-20260705-01-01-b3afb827ff50e603
silviarbgl-patch-1
ADD-event-20260721-01-01-5308156b31917ed5
20260608-newsletter
feat/alpine
feat/langs
wiki-links
refactor-booth-application
news-20250922-dma
followup-default-mail
feature/peertube-for-upcycle-android
No results found.
Labels
Clear labels
Accessibility
bug
build
cgi Scripting
design
disruptive
documentation
duplicate
easy
enhancement
feature-request
help wanted
javascript
priority/low
question
system-hackers
tagging
text
translations
wait/bugfix
wait/inprogress
wait/misc
wait/proofread
wontfix
xsl
Requires careful coordination and documentation changes
Improving what is already there
Milestone
No items
No Milestone
Assignees
albert (Albert Dengg)
alex.busch (alex.busch)
alex.sander (alex.sander)
anaghz (anaghz)
annarita.russo (annarita.russo)
ao (André Ockers)
bonnie (bonnie)
ciampix (Marco Ciampa)
cryptie (cryptie)
dario (dario)
delliott (Darragh Elliott)
dfajfer (Damian Fajfer)
dmaphy (Dominic Hopf)
doczkal (Thomas Doczkal)
eal (eal)
egnun (Erik Grun)
eventregbot (eventregbot)
fi (fi)
floriansnow (Florian Snow)
foxort (Tino Tempesta)
gabriel.ku (gabriel.ku)
guido (guido)
hf (hf)
hugo (hugo)
ineiev (ineiev)
jithendra (jithendra)
jn (jn)
jzarl (jzarl)
linus (Linus Sehn)
lucabon (Luca Bonissi)
lucas.lasota (lucas.lasota)
marcelo.fm (Marcelo)
max.mehl (Max Mehl)
mk (Matthias Kirschner)
monochromec (monochromec)
mweimann (Michael Weimann)
nico.rikken (nico.rikken)
patrick (Patrick Ohnewein)
reinhard (Reinhard Müller)
renovate-bot (Renovate Bot)
repentinus (Heiki Lõhmus)
schiessle (Björn Schießle)
silviarbgl (Silvia Rbgl)
sofiaritz (Sofía Aritz)
tobiasd (tobiasd)
vincent (vincent)
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: FSFE/fsfe-website#535
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This is a collection of issues and ideas we collected for the spreadtheword page (fsfe.org/promo). It involves changes on multiple ends to reduce fake/freebie orders, improve statistical evaluation, and increase awareness about the FSFE's work.
Thank you very much for this important work on one of our most visited pages. Here some thoughts on this:
Thanks for the feedback, @eal!
I see what you mean. Speaking in HTML, this would be a "placeholder". Would the text "For example: Spreading information about Free Software in my surrounding" work?
Phew, that's quite aggressive and I'm no sure everyone would like it. For fundraising, this indeed could be a working tool, but it's also a dark pattern which I would tend to avoid.
Yes, that's how I understood @reinhard.
the placeholder sounds good to me
I do not see the dark pattern here. We do not silently sneak something in. The only thing we would change is to write "10" instead of "0" in the field of donations. Nothing sneaky.
Don't know. Maybe a page works better, but then people have to read again, think about and do addtitional steps after ordering (fill in bank stuff) ... we can also try both for each two months and then evaluate?
Or what about having a placeholder of 10 and it is mandatory to fill in the field?
I like that. So people would have to actively fill in an amount and knowlingly insert 0 euro. However, then the separate page when donating 0€ might be seen as superfluous by some but I'd be fine with it. We don't force anything but just explain.
See #549 for the Pull Request with the first items completed.
PR #549 merged to master. See updated todo list in first post.
The following statistical data are now sent to OTRS in a structured way so they can be analyzed via CSV export:
TODO list in the first post is updated.
Like Max said 3 months ago, now adding an additional page asking for a donation might be a bit overshooting the goal. Currently we have:
Actually I do feel that this is enough of asking for a donation for something that we want to provide as a free service as part of our core mission.
Actually I meant that I'd be fine with an extra page although we have the donation field mandatory. But I see from your list that we indeed raise a lot of awareness (although email footers don't really count in my eyes 😉).
What about having an extra, short paragraph below the donation field, explaining why donations are crucial for us to offer this service for free and which costs this involves?
I like the idea of having a short paragraph explaining why one should donate. I could also imagine having just a link besides the donation field saying "Why should I donate?", which then upon being clicked opens a little popup window. So it would not clutter the form. But I would be ok with either way of implementing it.
Regarding the item "add a checkbox to enable people to receive information about the FSFE", it is now possible to subscribe email addresses at my.fsfe.org by calling an URL. The following variants are possible:
The following fields are possible:
I don't think I have enough knowledge in PHP to implement this well within the current script. Max, how about you?
Thanks for the update! I think I can manage to implement this. #755 is a first step to introduce a country dropdown selection with the country names and codes. It makes heavy use of XSL and uses the values we've already used in other places on fsfe.org.
The next steps will be:
sub_form_token) and makes the subscription for the user. We could also use this in other places.At the latest at this stage, I think we are required to link to our privacy policy, and potentially make its acceptance another required checkbox. What do you think?
Signing up to community emails now works perfectly after merging #760. Thanks Reinhard for helping via chat and debugging issues!
Most code for the newsletter signup does also already exist, but there is a strange bug I cannot trace down. So I will take care of it next week.