It’s a resource management system for groups. Documents are like private wiki items in the sense that they support Textile, have history, and you can run diffs on them.
I’m currently reworking groupthink to be a rails3 app running on top of DataMapper/jQuery. Luckily, not too much needs to be done. Stay tuned.
works. There’s a potential bug in testing this, and I haven’t added validations yet, but that’s what happens when we’re just getting off the ground. Files are called “artifacts”, couldn’t really think of a better name.
a “category” layer is in between docs and groups now. Eventually you’ll be able to say that a particular category is visible/invisible to non-group members. I’ll probably replace categories with tags, and certain tags will be visible/invisible. Who knows what the future brings.
USAGE
At the moment, the groupthink app functions more as a Merb app proof of concept than a fully functioning web application. It’s important to note that best practices for Merb haven’t congealed yet. That being said, I’ll try to keep groupthink up to date with those practices as they form. If there’s an area where groupthink is using an inferior practice or anti-pattern, please let me know.
Because of its dependencies and existing model structure, groupthink is not a good example of a base package. If you’re looking for a basic starter application, see dkubb’s merb-skeleton.
More to come, check the TODO.