• i

    Ivan Reese

    1 year ago
    I've noticed a bit of uncertainty about what belongs in #announcements. We've also had a higher volume of posts there than I'd like, so far. My hope is that the channel will be so low-volume that folks who only log in once every few months would find it worthwhile to catch up on all the posts there that they missed. How would you all feel about changing the rules around that channel a bit? I was thinking something like: If you'd like to share something to #announcements, please DM it to @Ivan Reese for approval. Additionally, we could make it so that I'm the only one who actually posts to that channel, which might help indicate to people "Don't post here — get Ivan to post here for you". / shrug / My thinking is that that channel should mainly be for stuff that everyone needs to see — eg, if we update the code of conduct, or if we add additional moderators, or if something changes about the nature of the community. Job offers and conference calls for submissions and such.. that feels like a grey area — not sure what to do with them; they probably belong in #linking-together or #share-your-work. But posts about croudfunding, or new initiatives by members of the community, or other things that are happening within the community (but not about the community itself), absolutely ought to go in #share-your-work or #linking-together or #thinking-together or #present-company, as appropriate. Nods of agreement? Grunts of disapproval? Epic poems of alternative proposals?
    i
    1 replies
    Copy to Clipboard
  • i

    Ivan Reese

    1 year ago
    The path that leads newcomers into our community is the Community page on our website. I've recently added the following message, right above the link to join: "Before joining the community, please familiarize yourself with the member handbook." If you have a few minutes, I'd love it if you clicked that there blue member handbook hyperlink, read through the text, and pointed out all my poor phrasings, typos, or inherently bad ideas. Though if it passes muster, a "LGTM" would be just peachy. And in the grand Osborne tradition of pre-announcing... now that this Member Handbook exists, my next projects are: • The Podcast (took a break for the summer) • A community wiki / knowledgebase
    i
    Nick Smith
    +3
    8 replies
    Copy to Clipboard
  • ogadaki

    ogadaki

    1 year ago
    In some other thread @Maikel wrote:
    maybe we should extend the 2 minute week channel to not only allow video's but also very short articles (max 1024 characters?) with some images. I have enough to share about my progress in incremental steps but I dont have the time to make a video that often.
    Followed a discussion about the scope of #two-minute-week , I copy in this thread some message of the discussion.
    ogadaki
    Kartik Agaram
    +3
    13 replies
    Copy to Clipboard
  • i

    Ivan Reese

    1 year ago
    An interesting proposal from @Chris G came up in the discussion about grant funding. This community could pay for some cloud/IaaS resources for its members' projects, to help them experiment. In Christopher's words:
    Make infrastructure available — Need a virtual machine? Some lambda functions? Some storage?
    Keep it simple — have 1 account, with multiple access groups so a person/team can keep their work private if they like (or in the open, per Maikel's nice point above), and just pay the tab on that account
    I'd love to know — if the community offered to pay for some cloud/iaas resources, specifically to help YOU work on your not-otherwise-meaningfully-funded FoC project, would you take advantage of that? What resources would you need? How might you use them? I love the idea of making resources like this communally available. It reminds me of what labour unions used to offer, in the good old days when the rail unions had well-stocked libraries and offered classes and such for members. Or, if you prefer, what the early-day perks at Google or the dot-coms were like. Extra goodies that are meaningfully valuable to an individual, but relatively inexpensive for the larger collective to offer.
    i
    Kartik Agaram
    +1
    6 replies
    Copy to Clipboard
  • i

    Ivan Reese

    1 year ago
    There was a self-promotional ProductHunt link posted in #share-your-work, by a member who has posted only a handful of times in the past, all of which were similarly self-promotional in nature. The product has little to no relevance to FoC, and they didn't provide any interesting technical info. This sort of content doesn't belong here, so I removed it and messaged the poster with some guidelines. I'm sharing this info with you here since it's the first non-trivial moderation action I've had to take since last summer, which, upon reflection, is a nice change of pace from the first half of last year. Cheers, everyone.
    i
    Nick Smith
    2 replies
    Copy to Clipboard
  • i

    Ivan Reese

    1 year ago
    Is this post in #introduce-yourself too spammy. It's entirely non-technical, and it's promoting startup-like stuff rather than anything directly about the future of programming. If it were up to me, I'd remove it as off-topic. Thoughts?
    i
    Chris Knott
    +8
    14 replies
    Copy to Clipboard
  • i

    Ivan Reese

    1 year ago
    I alluded to this on Twitter just now, but I figured I should share some thoughts here too. When I took over stewardship of the community last year, it meant doing a lot of new, ongoing work all at once, and it ended up overwhelming me in ways I didn't expect. There were many discussions needed to arrive at a sense of how to moderate this community, and how to deal with two people who (despite their enthusiasm) were making many other folks feel unwelcome. When that exercise in diplomacy died down, I was in fact burnt out from it, but I didn't realize this at the time. I had thought to myself, "Now that that's dealt with, I'll be able to put my energy into more generative things, like the podcast, and some new tools for us to use to organize our discussions". But I actually didn't have any energy left. I really, really, really like making the podcast. I just don't have the capability to consistently do it at the quality level that I held myself to. The biggest challenge is the transcripts. Steve and I have been using a transcription service that is not great. Steve didn't edit his transcripts, AFAIK. I extensively edit mine. I add inline links and embeds, sure, but more than that — I rewrite what is said so that the ideas being discussed come across clearly, absent the inflection and timing of the speech. I remove aborted thoughts, or rearrange sentences, or otherwise capture the spirit of each thought, rather than the mechanical series of words robbed of their articulation. I love the result of this editing effort, but the work is.. exhausting, time-consuming, and not enjoyable in the slightest. This isn't my first time moderating a community, or doing a bunch of big side projects in addition to my day job. But it is my first time doing both at once, with a toddler, during a pandemic. I've spent the last 6 months figuratively rolling over and hitting the snooze button, feeling like "I need to get up and get back to work.. but.. not just yet." I have several interviews for the podcast recorded, one of which is mostly edited and almost ready for release. But I'm just dreading doing the transcript editing work. So in the interest of getting the podcast going again at all, here's my plan. The next few episodes are going to be rougher — a bit less editing, and an unedited transcript. (The transcripts are on github, and contributions are welcome, so I might lean on that a bit more than before.) I'm also not going to pressure myself to do any new projects for the community, not for the next 6 months at least. I'll continue moderating discussions and maintaining the website and otherwise being steward. But I'm not in the position to lead us to somewhere new. Finally, I haven't been posting about Hest at all, because I haven't been working on it. That's a long story, but I think I should probably rank it higher in my list of "things to get back to, when I can" than initiatives for this community (like some sort of wiki / zettel, say). After all, that's why I came here in the first place. I hope this post isn't too much of an indulgence in your attention. Hopefully the next thing you hear from me is an announcement about a new episode of the podcast, or maybe a little 2 minute video about what I'm doing with my days. I think I'm almost ready for that again. 🍻
    i
    Kartik Agaram
    +6
    12 replies
    Copy to Clipboard
  • Mo

    Mo

    1 year ago
    Hey folks, I was wondering whether this community has considered leveraging clubhouse for events, conversations, ...? Is there already a clubhouse arm? IF not, are you looking for members of the community to take charge and lead the initiative?
    Mo
    i
    +3
    11 replies
    Copy to Clipboard
  • Mariano Guerra

    Mariano Guerra

    1 year ago
    Slack deprecating APIs[0] and the replacements requiring to fetch the replies for each message individually, realizing that last week's dump silently missed the replies and that the slack library I'm using is no longer maintained ... minutes before sending the newsletter If only there was a forum about the future of coding where I could go and complain 😛 [0] https://api.slack.com/changelog/2020-01-deprecating-antecedents-to-the-conversations-api [1] https://github.com/os/slacker/#this-repository-is-archived-and-will-not-receive-any-updates
    Mariano Guerra
    i
    8 replies
    Copy to Clipboard
  • j

    J. Ryan Stinnett

    1 year ago
    It seems we've unfortunately had some spam coming in via the bridged Matrix rooms in the last few days. 😖 I have gone ahead and removed the spam messages and reported the accounts on the Matrix side. As a temporary measure, I have set all the Matrix rooms to invite only as well, which should prevent any new spam accounts from joining. If you do happen to notice any further spam coming in via Matrix, please feel free to tag me.
    j
    i
    3 replies
    Copy to Clipboard