I think funding announcements like https://futureofcoding.slack.com/archives/C5U3SEW6A/p1627463596030700?thread_ts=1627463596.030700&cid=C5U3SEW6A don't belong in #C5U3SEW6A. Thoughts?

hmm .. well, it's related to the 'future of coding'

where should they go, or don't they belong on this slack?

I was thinking #C01932BJGE8. Just my opinion, though.. Basically my lens for this channel has been to ask, does it help us think about what we should build? Generic funding announcements fail that test. (Though I may have missed something in the recent couple of cases. In which case others may as well, and it's worth calling out what's interesting about a specific early-stage company.)

linking-together seems more appropriate than present-company when i read this: https://futureofcoding.org/member-handbook#linking-together

I had the same doubt, decided for linking-together because I thought it could generate a discussion about funding and business models for FoC style projects, I'm ok if it's moved to present-company

#C01932BJGE8 sounds good, just wanted to make sure there's a place for it because it seems so related

Feels like policy has to be pretty broad, will be hard to convey to posters that linking-together can only be about construction or whatever The policy could be: • If it's news, present-company • Otherwise if it's a link, linking-together • Or if a text post, thinking-together

I've found this sort of channel delineation extraordinarily hard to capture in language, while also being memorable, consistent, and welcoming. It might be worth trying to do some writing for the Handbook about the meta-level matter of "What to do if you aren't sure where to post," in such a way that exudes a sense of forgiveness. I'd much rather people post something to a sub-optimal channel, but still post, rather than not post at all, or throw up their hands and just dump everything wherever. (And we've seen both of those failure modes occur here.)