You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been thinking in the idea that projects can declare what issues they are working for; what are the objectives, the specific things they aim to change with their activity. The idea is that this issues are not specific to a project, but can be used across the site:
A project can say they are working to "protect user's privacy in the digital world". That would be listed in the projects page, but would be an issue in itself, an independent entity
A user can browse through issues, and follow/adhere to issues. In their profile it would appear which issues they support along her donations
In an issues page, you could see which projects works for that issue, and which users support it.
In a project's page, along the issues, you could see how many users support that issue (independently of them following/donating to that project)
Why
To explain better what a project fights for
To allow users to find project through issues
To allow users to adhere to issues and promote them independently of them donating to a project
To allow users to start directing specific action to an issue they worry about, or to make them worry about specific issues
Drawbacks
Extracting/generalising issues is not straightforward.
Who would do it? Ideally project owners... until them, maybe users could be in charge, with some moderation if needed.
Maybe each project would have their own issues? If there is no overlap, maybe this doesn't make sense
I like the idea because it's a good way to give more visibility to projects and for people to feel more identified to. I think reading that you support "free software users rights should be publicitized" is a good way to resume your values, no matter which projects you support, and it allows you to find projects you are aligned too.
The main problem is that I the content should be moderated 100% if we don't want to get with tons of duplicated issues. But I think we should try and see how it goes.
As part of #34 we could prepare a couple of issues for each project.
Also, I'd like to suggest to test TrackDons and this part with a small project or NGO (I was thinking on our friends in Galgos de Casa, but it can be another project).
I've been thinking in the idea that projects can declare what issues they are working for; what are the objectives, the specific things they aim to change with their activity. The idea is that this issues are not specific to a project, but can be used across the site:
Why
Drawbacks
I have drafted some example projects-issues:
https://docs.google.com/a/furilo.com/document/d/1BxNdo_NHkhOhGFD7v8NOLGoTLK2zxfkLntyTLPD5p-0/edit
Comments?
cc @ferblape @jorgesancha @paullop
The text was updated successfully, but these errors were encountered: