People might want to check that out of they haven’t.
And I wonder what should be there and what should be here on Discourse… the lines really do get fuzzy when the discussion is primarily about the code base but with research questions not far in the background (and coming into the foreground from time to time).
Somewhat relatedly, I’ve been thinking about the Orientation section of this Discourse site (which doesn’t yet have any posts), and how it really ought to be outward facing. The Push project needs an outward-facing orientation site in a big way, and using this as a mechanism might motivate and support us in building it.
The rub is that I don’t think there’s a simple way to make a single category public with our current setup, which specifies “Require authentication to read content on this site, disallow anonymous access.” and " Public registration is disabled, all new users must be explicitly invited by other members or staff." There may be a way to get the mix of public and private that we want, but it’s not obvious. I’m looking into ways to change what unregistered users see (awesome if it could be the orientation category!), but that’s not looking promising.
But what we could do is develop the content on Discourse in the Orientation category and then manually repost topics in static form to some other site. At least for orienting people to the fundamentals, it shouldn’t have to be done too often.
Which leads me to think about where we would put the outward-facing orientation content, which in turn leads me to ponder in horror the motley collection of related web resources that are in desperate need of rethinking/unification/whatever, including not only this Discourse site (for Push-related research discussions, among trusted collaborators) and github (for the world), but also the ci-lab mailing list (for Hampshire Computational Intelligence members only), the lab’s site at http://sites.hampshire.edu/ci-lab which has never-filled sections and is crusty and musty in other ways, the the project page at http://pushlanguage.org which forwards to http://hampshire.edu/lspector/push.html, a pretty-much-totally-dead Push mailing list at https://lists.hampshire.edu/mailman/listinfo/push, and a blog that we abandoned in 2012 at http://push.i3ci.hampshire.edu/. Some of this should probably just be ignored, but several of these resources fill ongoing needs.
I’ve spent some time trying to figure out if we could fold more of this into Discourse, but unfortunately I don’t see ways to limit what people can see once they have access to the site at all. There’s an elaborate “trust” mechanism, but that seems to limit only actions, not viewing.
I’m not at all sure about how to proceed with any of this, but I’d appreciate thoughts (or actions!).