Our community needs a convenient way to share stacks files and code. RevOnline is that solution, but some have reported issues which prevent them from using it.
Let's fix it.
The challenge is that these issues, AFAIK, are only intermittent. For example, I have the misfortune of always having it work for me, so I'm unable to fix it because I can't see the problem.
But if you have trouble with RevOnline, and you have some time to help fix it, we need you.
Let's form a team to triage RevOnline:
1. Make RevOnline work for everyone
This is an obvious first step, since of course if it can't be used it has no value at all.
2. Paper Cuts
We can make a list is small things we know we need done, like cleaning up the redundant unsorted tags, and knock those off second.
3. RevOnline Next Generation
Many in the community have expressed some good ideas on how to enhance RevOnline, and the core dev team at RunRev has plans of their own. If we can assemble a team to handle the first two RevOnline triage stages, we will have learned a lot about the process, and have established a team in the community who knows its code well, so it would seem a good opportunity to coordinate those community members with the relevant RunRev staff to work together for the next generation.
Exactly how this works in light of RunRev's plans is hard to say, but the one thing we do know is that if we can't do the small things the big things are even less likely.
So let's get #1 done and then a couple actionable items from #2, and along the way we'll have figured out what needs to happen for #3.
Interested? Chime in.
Community volunteer LiveCode Community Liaison
LiveCode development, training, and consulting services: Fourth World Systems: http://FourthWorld.com
LiveCode User Group on Facebook : http://FaceBook.com/groups/LiveCodeUsers/