Site Map | --All Pages-- | --Github Commits--, Issues | Possible Initiatives | Open-source Society Project | Main Prototype website | Sub-reddit -- This documentation wiki is under construction
Editing Possible Initiatives
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
# Development of a '''[[Open-Source Taxi App|Community-owned Taxi business]]''' to serve as a prototype of a service-based business and to serve as a model for more businesses like this | # Development of a '''[[Open-Source Taxi App|Community-owned Taxi business]]''' to serve as a prototype of a service-based business and to serve as a model for more businesses like this | ||
# '''[[Report-A-Problem App|Report a Problem App]]''' - Report a problem for anything (one central solution for reporting and resolution of problems that also includes performance monitoring for those responsible for resolving the issues). This would tie into the main website's Unit structure etc (how to do that) | # '''[[Report-A-Problem App|Report a Problem App]]''' - Report a problem for anything (one central solution for reporting and resolution of problems that also includes performance monitoring for those responsible for resolving the issues). This would tie into the main website's Unit structure etc (how to do that) | ||
# '''Improve Road Safety''' (need a system for reporting bad drivers and other issues on the road). Need to consider privacy concerns, legal issues etc | # '''Improve Road Safety''' (need a system for reporting bad drivers and other issues on the road). Need to consider privacy concerns, legal issues etc | ||
# '''Community-owned Product and Service''': | # '''Community-owned Product and Service''': | ||
#* Development of an open-source '''community-owned product such as a home security system''' with affordable and transparent subscription based-service (server costs, on-going maintenance costs, costs of alerting emergency responders) | #* Development of an open-source '''community-owned product such as a home security system''' with affordable and transparent subscription based-service (server costs, on-going maintenance costs, costs of alerting emergency responders) | ||
# (meta Unit) [[Improving Products and Services]] | # (meta Unit) [[Improving Products and Services]] | ||
# (meta Unit) Improving Parenting and [[Global Citizen Curriculum]] | |||
# '''Charitable Trust/Bequest Management:''' Comply with donor's wishes to funnel their assets and retirement funds into Javul after they pass away (follow specific directions, the kinds of projects and initiatives they want to fund) | # '''Charitable Trust/Bequest Management:''' Comply with donor's wishes to funnel their assets and retirement funds into Javul after they pass away (follow specific directions, the kinds of projects and initiatives they want to fund) | ||
# '''Requirements for Products and Services''': We need a tool where people can suggest requirements that should apply for a certain type of product or service. People can discuss the requirements, refine them, upvote them and finalize them into a valid requirement. And then products or services that fulfill those requirements would be listed and people would be able to see what products and services fulfil those requirements. For example scanning a UPC code on a product in an app would tell us what requirements are being met. Reqs can be of many types for example for headphones, we want universally exchangeable ear pads or other standardized aspects. This tool could have an API that interfaces with the main Javul website or it could be integrated into the main website (depending on how extensive this tool is). Reqs can also apply to services. | # '''Requirements for Products and Services''': We need a tool where people can suggest requirements that should apply for a certain type of product or service. People can discuss the requirements, refine them, upvote them and finalize them into a valid requirement. And then products or services that fulfill those requirements would be listed and people would be able to see what products and services fulfil those requirements. For example scanning a UPC code on a product in an app would tell us what requirements are being met. Reqs can be of many types for example for headphones, we want universally exchangeable ear pads or other standardized aspects. This tool could have an API that interfaces with the main Javul website or it could be integrated into the main website (depending on how extensive this tool is). Reqs can also apply to services. |