• i

    Ivan Reese

    2 years ago
    There was a question recently asked in #general that I'd like to use as a discussion prompt. The poster has since deleted the question (see comments in this thread), but here's the text of the question for reference:
    How would you recommend implementing an extensive and large rest api specification? It will include lots of special operations such as negation and logical AND all specified via characters that special meaning. There is no formal grammar, only pages of docs with scattered rules and schemas. Example query: "/user?name:not=joe&alex"
    This feels like a very "present of programming" line of inquiry. It feels like something that'd be posted to Stack Overflow. To me, it doesn't pass the sniff test of on-topic-ness for the community. As the community grows, I think we can expect more things like this, and I'd like us to have a good strategy in place to maintain our focus. There are no shortage of other general programming communities, or technique/technology-specific communities, that address the present of programming. We're all here because we are unhappy about the present. It's necessary for us to talk about the present, so that we can understand what's wrong with it. But I don't think we should facilitate or normalize conversations that have no eye on the future. • Do you agree that this example question is too far from the core focus / purpose of the community? • If so, how should we handle these sorts questions when they come up?
    i
    c
    +4
    18 replies
    Copy to Clipboard
  • Orion Reed

    Orion Reed

    2 years ago
    With recent threads about channel names, appropriate content and community structure as a whole I want to examine the relationship between the community and its purpose. We all seem to agree on our purpose here, but the community is not the purpose itself: the community exists in the real world now; the purpose is something to be fulfilled or strive towards. I’m sure this has come up before in conversation but it seems maybe thread-worthy. Edit: I bring this up because I think there’s a whole bunch of people here who are highly motivated to figure out how to get to the future we want, really just wondering how we can all help each other do that. (more in thread)
    Orion Reed
    i
    +3
    21 replies
    Copy to Clipboard
  • i

    Ivan Reese

    2 years ago
    I'll now list and describe the channels. These descriptions are written off-the-cuff for the audience here, who I expect to be familiar with the community as it exists now and with that big previous discussion. I intend to write up something like this Member Handbook for a newcomer audience, with more clear and concise descriptions. The first three channels (alphabetically) are about the community itself. #admin — discussion about the administration of the community, meta-discussion about the Slack, requests for moderation, discussion of community finances and governance, etc. Formerly called #meta.#announcements — super low-volume channel with messages that every community member should see, even if they only log-in infrequently.#introduce-yourself — the first post by every new community member should go here. Formerly called #introductions. The next channel is by itself. #linking-together — If you want to start a discussion about an article, talk, book, paper, or other work authored external to the community, this is the channel. We devote a channel to these "external" discussions so that it's easier to follow the "internal" discussions that happen in other channels. This does create a decision that some might struggle with ("Which channel does this go in? I understand all the guidelines, but this falls in a grey area and I'm not sure!"), but I don't believe that's a problem that is entirely solvable at the level of channel design. The previously linked Member Handbook should carry significant weight here. Another point about this channel is that I'm not entirely happy with the name, and would love something that _even better-_satisfies all the design goals and starts with the letter "R". Suggestions welcome. The following are what I've previously called "subject-specific channels". They're all named with a common scheme, so that they (A) sort together and (B) reinforce that we're here primarily to talk about the future of these subjects, not just to gossip about current goings-on. This common scheme should make it much less painful for us to add new subject-specific channels as the interest arises, or to rename existing ones, since these channels are all off over there in their own space. #of-end-user-programming #of-functional-programming #of-graphics #of-music #of-research All the following channels are one-offs, and aren't meant to form a group. #present-of-programming — Our community contains considerable expertise about programming as it's currently practiced. It would be valuable for us to have a space where we could share that expertise, without dragging the community away from its main focus on futurism, research, and experimental development. A channel focussed on the present also gives us a way to more clearly define what subjects or projects qualify as meaningfully "futuristic", without entirely excluding other subjects from being welcome in the community — the lack of such an outlet has made me very reluctant to broach this topic. One other point about this channel is that, again, I'm not entirely happy with the name, and suggestions that balance the design goals are welcome, though it can't start with the same letter as any existing channels, or any letter lower than "I". #share-your-work — This channel is for nurturing feedback, fostering collaboration, gathering input, links to external things by community members. It has overlap with other channels (like #linking-together, the subject-specific channels) but the key factor is that everything in this channel is by someone in this community, and they want you to approach it on terms they define. There's no harm in someone posting their own work to another channel. There's no harm in posting things that aren't totally futuristic in their scope. This is the channel that newcomers should enjoy browsing, as a way of seeing all the cool things made by people here in this community, and how helpful we are with our feedback. #thinking-together — This is the most important channel. It's the new #general, minus the links to external stuff covered by #linking-together. This channel is for questions, ideas, brainstorming, wild visions, summaries of research. Things in here must be forward looking (though this can include scouring history for things we can apply to the future). This is the channel for people actually building the future of computing. Links in posts are welcome (eg: supporting references), but the discussions should not be centred on some external media that needs to be read/watched/etc and then reflected on. #two-minute-week — Closing out the channel list, this channel is exactly what it is now. It's a fun collaborative experiment in sharing our work, with accessibility prized above depth. If you are happy with this plan, enough at least to try it out for a while, please leave a positive emoji reaction on this post. (I'll be interpreting the sentiment of the emojis, so feel free to hit me with your best contrarianism.) If you have significant concerns about this plan, please leave a comment in the replies to this post. Thank you all for weighing in with your thoughts and ideas so far! I hope these changes (and other upcoming initiatives, like some sort of Member Handbook) will fix a few issues we've had and, as the startups say, unlock deeper collaboration across the organization. ❤️
    i
    opeispo
    +7
    27 replies
    Copy to Clipboard
  • Cole

    Cole

    2 years ago
    Sorry if this was surveyed recently, but what do people think about the #feedback channel?
    Cole
    1 replies
    Copy to Clipboard
  • i

    Ivan Reese

    2 years ago
    (Apparently, you aren't allowed to name a channel "admin" because that name is already taken by a user group — administrivia it is!)
    i
    1 replies
    Copy to Clipboard
  • s

    S.M Mukarram Nainar

    2 years ago
    Hmm... After the big rename, slack is saying I have one unread notification (shows up as a red badge with 1 on it in the workspace switcher), but I cannot find any mention of me and every channel is read. Anyone else with this issue?
    s
    i
    3 replies
    Copy to Clipboard
  • Nick Smith

    Nick Smith

    2 years ago
    Should "requests for exemplars" go in #thinking-together or #linking-together? e.g. if I want to ask people if "you've ever seen a language with X"? Seems like it would trigger #thinking-together convos, but it definitely starts with "give me links plz". I'm thinking that would qualify as #thinking-together.
    Nick Smith
    g
    3 replies
    Copy to Clipboard
  • Mariano Guerra

    Mariano Guerra

    2 years ago
    the "pass through" aliases are feedback -> share-your-work and general -> thinking-together right? my idea is to just remove general and feedback from the select and when searching on the new channels it will return results for the old ones too
    Mariano Guerra
    1 replies
    Copy to Clipboard
  • Steve

    Steve

    2 years ago
    I’ve been kindly asked to leave the FoC community. I’m not upset or disappointed by this request but I would like to share the reasons why, from my perspective and invite others to comment according to theirs.1. Harsh could be one word, but also bold, brave, and thoughtful could be others. I apologize if my feedback and comments on others posts hurt anyones feelings, I honestly have respect and love for everyone. My intention was to challenge and, at times be polarizing, which I hoped more people would be in FoC and the world at large. I don’t believe “poking the beast” and “stepping on toes” is wrong, even though it could hurt. 2. My intention to participate here was to share ideas, join in constructive criticism, and participate in debate which I was hoping would result in finding like minds that would work with our team — in short: recruiting. This may be against the policies of this community (I’m not clear on that) which I’m sorry for crossing the line if people felt I was advertising a product or exclusively looking to recruit. 3. We are not getting the collaboration or feedback we were hoping (good and bad feedback that is) from FoC participants. There could be many reasons for this that I won’t speculate on here, but often results in frustration as compared to other communities I’m participating in. I want to thank @Ivan Reese and countless others for maintaining this community and I sincerely hope you all the best. As for me, I’ll continue to pursue a mission that I strongly believe is the future of coding, but unfortunately will no longer be sharing here. I’m free to reach on Twitter, email, Linkedin, wherever for those that want to stay in touch. Again, thank you and I hope success to your projects.
    Steve
    c
    +4
    11 replies
    Copy to Clipboard
  • i

    Ivan Reese

    2 years ago
    If you're in this channel, that probably means you're familiar with our Code of Conduct (and maybe even the work-in-progress Member Handbook). One of the guidelines outlined in both places is that the first post from a new member should go in #introduce-yourself. This post should not be used to promote a startup, unless the post also includes something that is super on-topic for our community, like a deep technical exploration of their domain. We recently had a post in #introduce-yourself that didn't fit within this guideline. I posted a reply saying that that was the case, and then the OP posted an acknowledgement. I decided to delete these message, so that other folks coming to the community, heading in to #introduce-yourself to make their first post, would only see good examples and not bad examples. (In my estimation, the sort of people who skip the fairly clearly signposted request to check the Member Handbook before joining would probably also skip the replies to previous posts saying, "Hi friend, bad post!") For the sake of posterity and transparency, I'll include the now-deleted thread in a reply to this post. For the sake of mischievous tricksterdom, the inclusion will take the form of a screenshot, since that will boil the blood of a handful of folks here, I just know it. 😃
    i
    1 replies
    Copy to Clipboard