Birthe, There will be plenty of time for feedback during and after a solution is developed. However few people necessarily understand a vision for an end solution and the best way is to build it and then get feedback. I will quickly outline the approach but avoid places with debate.
> You will all want to be sure, that everyone will back you up before using > lots and lots of time on this. > I only need a few people to be involved. I do not need everyone to back me up, how can they until they see the results. > If enough is interested in taking active part, should we have a vote about > it? > Look even the optional voting in the US and UK have given rise to perverse outcomes, I am not sure we have an established voting process that would provide much value. > No matter how this ends up, I want to thank you for you offer. > Thank you. You say *I do think you have to tell a little about the direction and the end goal. What can be achieved. Not necessarily in detail, but to secure you some feedback. What will you need? What kind of skills? You need answers from people able to take part in it, having the knowledge and able to use the time necessary.* Here is a first high level attempt. Direction: Provide a structured community resource and database providing a way for cumulative development and sharing but leveraging existing resources. End Goal Solve all our community issues as currently experienced and they arise. What will we need? I need some commitment from some volunteers and support promoting its use when it becomes available. Especially as we build the resources up, this includes people who can test and build the documentation to make adoption of the community resources accessible to everyone. I am sure we could ask for some additional specialist skills and particular skills from volunteers but the key would ultimately be people with tiddlywiki knowledge. What is needed for effective communities? - It should be so easy to use it does not cost people any additional time to contribute to the community. If people can trust this and spend time they would have otherwise building their own private resources to put this effort into the community resource. Similarly provide methods for the easy transfer of content into the community from public and private records. - It should not impose excessive obligation on anyone (including me) High level requirements - We need a platform that is aware of the features and objects within tiddlywiki such that any documentation can be easily developed, linked and discussed. - The platform needs to allow high level control to build and maintain structure whilst being as open as possible to collaboration, change, conversations and feedback - Collaboration, feedback and contributions need to be as seamless as possible. - A correctly structured resource will minimise maintenance effort and reduce volunteer time demands. - We need to seamlessly as possible integrate existing resources in a complementary manner but with the opportunity to migrate services into the community resources to benefit from further integration and cross referencing. - The Platform needs the ability to grant and control access to a range of users and contributors including a degree of anonymous access, this should be retractable in case of spam or other problems. So it needs a strong underlying user authentication and control mechanism. - Most importantly TiddlyWiki needs to be fully integrated such that it is easy to publish tiddlywikis and tiddlywiki objects from within it. However controversially I do not believe it should use tiddlywiki at is core, because it is not necessarily the right tool. However as tiddlywiki matures and new methods develop we should be able to plugin new tiddlywiki solutions. To place the development of the right solution in tiddlywiki on the projects critical path is to increase the time to a solution and may cause it to fail. In time we may place tiddlywiki at the core but until we have a comprehensive community resource we will flounder. - We need to be quite permissive to encourage contributions but we need to be able to reverse malicious activities. - Ideal we allow Open ID and other authentication methods to open access to more people with less administration. - All standard self serve, access management etc... needs to be automated to reduce the maintenance overheads. - The solution needs to be EXTREAMLY scalable, movable and standards compliant. - Ideally information and tiddlywiki objects will be stored in one place so that we can always return to a "source of truth". What is a tiddlywiki object? Tiddler, plugin, json, macro, theme... edition... library... Regards Tony -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/9982a3e6-4da4-466a-ad39-823dd5b69627%40googlegroups.com.
