[ ] implement value network which also shows maintainers
[ ] @mimi-uxui-dev Learn about supply chain
[ ] users can donate or tip the maintainers for a specific app/file/folder/content they created, which will automatically trickle down the supply chain to reward everyone who indirectly contributed
[ ] user can reach out via submit feed and become contributor
@info
it's not just "maintainers", its "value network" (or supply chain network)
There are lots of information about "the people" who make and enable a workshop.
It's for the workshop-creators who made and updated the workshops' content but also the tools they use, each of the tools is maintained by other people, the dependency workshops that enable the teachers of the current workshop to even offer it
We can maintain the entire workshop and it's tools, which includes: workshop content, chat program, gigs and sub tabs in the tiling window manager, also, you can see the maintainers behind every a tab (content + tool)
once you see the maintainers, you might also see news about new versions of that particular content or tool
maybe you want to discuss the tool, check the source code, maybe you want to check out the currently open issues and some of them are bounties (=gigs), also maybe, you want to contribute and become a maintainer yourself
So while you are a learner, you go through the workshop and learn also, do gigs
BUT: occasionally you check who are the maintainers behind certain tools or content and what are they using and who are the maintainers of that; This way, you can start exploring the entire supply chain and if something sparks an interest in you, you can reach out and even start helping maintain something yourself, solve gigs around it and learn even more interesting things
Alright. So when you "submit feedback" it goes to the people who made a website/app/service/workshop/whatever...
They receive a lot of such feedback. There are different types of feedback and we should definitely thinkg about what types exist.
But the following types (e.g. feature request, bug report, improvement proposal) and maybe even "answer my question", those types go into a big list of things the team has to decide to work on to fix the bug, implement the feature or improvement or to answer the question and if something is popular that will create a long list of tasks/todos for those who make the thing that people submit feedback on.
Now in an open p2p world, ...why would anyone go and work on that list of tasks that exists because people submit feedback?
Maybe somebody can put a bounty on those tasks ...its maybe the person who submits the feedback or somebody who sponsors it and so the team of maintainers is motiviated to work on acting on the feedback to make things better.
BUT: ...now people can make stuff and maintain it and work on a constant list of paid tasks to make things better.
Isn't that just what gigs are? :-)
So why would we create "a different mechanism" instead of integrating it into our overall system in the way we already brainstormed and try to make a core feature of our system in general ... and thats gigs/exercises :-)
So if i am using e.g. figma and every day you come across this missing feature or annoynig behavior and you have a good idea how it could actually work smoother and make things better. At the moment you are helpless, because you have to maybe send a feedback to the figma team and hope for the best, but in the future, your feedback would be public and other people who use figma just like you and feel the same can maybe add comments and because they earn a lot of money with their work and know a better figma tool would help them, they are willing to maybe bounty it with 1-2 USD if the figma team improves figma based on the feedback ...now imagine figma was a popular tool and 10.000 people think your feedback is important and it annoys them too, so they put also 1-2 USD on it... and all of a sudden that amounts to 10.000-20.000 USD to act on that issue and implement that feature and the money would go to the figma team ...so all of a sudden the figma team has some serious motivation and is incentivized to actually act on your feedback.
now even better ...because of course the future is open source.
Lets say the figma team doesnt care :D
Doesn't matter... a team of skilled developers can go and FORK FIGMA and implement the feature and get the bounty money. That in fact happens, so i personally for example do not use vscode and instead i use https://vscodium.com/ so what vscode does not fix, maybe i can convince the team behind vscodium ...thats fine :-)
mimi-uxui-dev
commented
2 years ago
@todosubmit feedand become contributor@infoit's not just "maintainers", its "value network" (or supply chain network) There are lots of information about "the people" who make and enable a workshop.
It's for the workshop-creators who made and updated the workshops' content but also the tools they use, each of the tools is maintained by other people, the dependency workshops that enable the teachers of the current workshop to even offer it
We can maintain the entire workshop and it's tools, which includes: workshop content, chat program, gigs and sub tabs in the tiling window manager, also, you can see the maintainers behind every a tab (content + tool)
once you see the maintainers, you might also see news about new versions of that particular content or tool
maybe you want to discuss the tool, check the source code, maybe you want to check out the currently open issues and some of them are bounties (=gigs), also maybe, you want to contribute and become a maintainer yourself
So while you are a learner, you go through the workshop and learn also, do gigs BUT: occasionally you check who are the maintainers behind certain tools or content and what are they using and who are the maintainers of that; This way, you can start exploring the entire supply chain and if something sparks an interest in you, you can reach out and even start helping maintain something yourself, solve gigs around it and learn even more interesting things
Alright. So when you "submit feedback" it goes to the people who made a website/app/service/workshop/whatever... They receive a lot of such feedback. There are different types of feedback and we should definitely thinkg about what types exist. But the following types (e.g. feature request, bug report, improvement proposal) and maybe even "answer my question", those types go into a big list of things the team has to decide to work on to fix the bug, implement the feature or improvement or to answer the question and if something is popular that will create a long list of tasks/todos for those who make the thing that people submit feedback on.
Now in an open p2p world, ...why would anyone go and work on that list of tasks that exists because people submit feedback? Maybe somebody can put a bounty on those tasks ...its maybe the person who submits the feedback or somebody who sponsors it and so the team of maintainers is motiviated to work on acting on the feedback to make things better.
BUT: ...now people can make stuff and maintain it and work on a constant list of paid tasks to make things better.
Isn't that just what gigs are? :-)
So why would we create "a different mechanism" instead of integrating it into our overall system in the way we already brainstormed and try to make a core feature of our system in general ... and thats gigs/exercises :-)
So if i am using e.g. figma and every day you come across this missing feature or annoynig behavior and you have a good idea how it could actually work smoother and make things better. At the moment you are helpless, because you have to maybe send a feedback to the figma team and hope for the best, but in the future, your feedback would be public and other people who use figma just like you and feel the same can maybe add comments and because they earn a lot of money with their work and know a better figma tool would help them, they are willing to maybe bounty it with 1-2 USD if the figma team improves figma based on the feedback ...now imagine figma was a popular tool and 10.000 people think your feedback is important and it annoys them too, so they put also 1-2 USD on it... and all of a sudden that amounts to 10.000-20.000 USD to act on that issue and implement that feature and the money would go to the figma team ...so all of a sudden the figma team has some serious motivation and is incentivized to actually act on your feedback.
now even better ...because of course the future is open source. Lets say the figma team doesnt care :D Doesn't matter... a team of skilled developers can go and FORK FIGMA and implement the feature and get the bounty money. That in fact happens, so i personally for example do not use vscode and instead i use https://vscodium.com/ so what vscode does not fix, maybe i can convince the team behind vscodium ...thats fine :-)
Supply chain ideas