 Hello, how many folks how many folks are in the room just because I'm I'm remote so I'm just hearing voices It's four of us right now, but I think more people because we just started So, oh, that's great. Yeah Great. Um, so, um, lolly, did you want me to Kick this off or did you want to kind of jump in and um, give a little background here? No, no, you can you can start I'll I'll just share my Point, uh, if I if I have some like you you can start. Okay. Yeah. Okay, perfect. So, um, hi everybody. My name is rachel romoff and I work with the open jf foundation and I am your um, communications and public relations support for all things open jf And and no jf project Um, I am relatively new to the role um It seems like I've been here it feels to me like I've been in this role a little bit longer than I actually have I just think that's kind of the nature Of the project everything kind of moves pretty quickly. Um, I've been with the linux foundation since uh, november of last year and I took over for um, zibby keaton who kind of had some of this stuff in motion prior to me coming on board um and really the purpose Of today's uh, conversation and that's really how I kind of hope this goes is to get some feedback on um, how things are running with the node jf collection and How things are going with social media? um, specifically the the node jf handle and uh, the facebook and the linkedin, but I think um I think we do get a lot of traction on twitter. So, um, so not only how things are going but also You know, how can we get how can we improve and what programs can we put in place and what processes Can we put in place that? um, that just includes more more relevant content um a more diverse, uh group of people You know and how we can just get some of that stuff Just a little bit more collaboration on on both of those topics. Um So before I kind of dive into the topic here just got some background info. Um, are there any questions? Um, you know before I dive in Uh, I think no Okay, perfect perfect. So, um Okay, so a little bit about the node jf collection Um, it is and I apologize. I'm not exactly sure who's in the room So I don't know how much everybody knows about what it is and sort of the purpose of it So I can be pretty brief and if there are other questions, I'm happy to answer those questions um, so the node jf collection is a It's our basically our community blog on medium and um, really the the purpose of that is for people to share technical content tutorials um, you know That kind of thing um, some of the some of the things that we are collecting today Some of the things that we want to talk about um on that blog today are things around the community best practices and how to cloud and containers internet of things AI mobile and node core those are some of the things that we kind of Would like to get topics on Let me just find your screen again here while he does reading off a list there. Um, there it is and so typically how people publish Today, so if you wanted to publish something today, uh, we do have a medium email alias where people will email in I do get um ping directly as well um, but typically how it should work if people would hit that medium alias It would send in either An abstract so like an idea of something that they want to submit or A fully a fully fleshed out post And then how it should work is is this group of of medium participants and editors would read it and kind of you know say As a group how it's working today, and I think this could this is kind of part of where we can improve Um, we kind of say yay or nay and it you know, some folks are a little bit more available So, you know, we'll get um, so not everybody's necessarily Voting on it, but it's you know, we're cut if I get the all clear then I can work with the The contributor to publish. Um, it's a very it's a pretty manual process in so far as You know, we're copy and pasting Um from documents that they have into a word document And then we're you know putting it on The the blog with you know, it's kind of bylined under the no jay foundation um Versus maybe bylined under them with we we obviously attribute it. Um, but there's some things we can do to So maybe streamline that process um So I'm just going to move on to the next bullet point here if there are no questions about sort of that review process because it's there's not I guess my point is there's not much structure around the review process. Um So after that we so how much time Is this is this how much time should it take to publish or what's What's this trying to address here while we um the second bullet? Oh, so it's like, um, how much, um How much time we should um like how many times do we publish in a in a oh or oh, yeah, so yeah, so um You know, it's It's really as we're we're not getting a ton of content today, so You know As far as like a like a best practices standpoint, I would say a couple times a week would be great. Um Just to kind of keep You know just to kind of keep the content fresh and to keep people coming to read Um our our things Um, you know the the thing about this is we can time it out You know just because we get something on a given day doesn't mean like we have to get it out. Um that day Um and depending on what it is. It doesn't necessarily have to go up that week if it's more evergreen content, um, so you know, I I think we could get much better at Using an editorial calendar and get these things um scheduled out in advance And um, you know, so it's you know, it's part of the best practice around, you know, how often we should be publishing I would say a couple times a week would be great. Um, if not It's not more. I think where we run into problems is when we post You know a ton of stuff on one given day close together Um, so even if we've got a couple of things going out on the same day Um, that's okay, too. We just have to be mindful of the timing of it Um So how to become a reviewer and how to leave so today's folks would just email that medium alias and I can I can find it and drop it in the The chat here too if that's helpful. Um, and essentially what what what what we're doing Is people are requesting to Requesting to become an editor um and Hold on just one second. I'm just grabbing that email address because I keep referencing it And it would be helpful To give it in there. Okay. So, um, yeah, so essentially just just requests to uh to become one and we're we are looking for technical Um folks to come and help us review. Um at this point we I we don't have a process to To leave but that is probably something That we should address Um, because there's probably some folks who maybe their jobs have changed or uh, you know for whatever reason It's just not something that they're able to do right now And so, um, just so that we kind of I'm sorry. Did I No, no, no, you would just okay. Yeah, and please um again. I'm on the phone. So I'm just kind of Talking through some things If you need me to stop and you've got questions just interrupt me. Um, I will not take offense to it. Um Let me see her. So should we have a trello board or something? I mean, let's kind of let's talk about that. Let's I I think maybe there is another way to to project manage this a little bit more. Um A little bit more in a streamlined way. Um, I think that's a huge, you know, a huge uh question and a You know Something that we could probably improve upon because um at this point It's kind of just, you know, things like things are coming in through um that email alias um And you know, unfortunately It's one of those things where it could be a single point of a failure if you know, if it's not Maybe documented somewhere else outside of that email Um, so are there any thoughts around? You know having a trello board or even just Um, I know I know at one point there was a contact calendar. Maybe we could read You know revive that Yeah, does anyone have uh idea about Such it's like a process for the for a blog post to manage to the review process GitHub has um, you know trello boards on it now um, is there Is there are you guys talking about trying to Schedule posts specifically or just how to get them into the pipeline because I would assume that they would be i'm john church by the way, I That's what you're speaking. Hi um and uh I would expect it to be like, you know, somebody submits a poll request To a repository the way that the most of the committees work and whatnot and then that can be reviewed and marked down there Um, and other people could weigh in on it, etc Is there a reason why um, that's not the way you guys are working currently or am I missing something on that? I guess So one point of not using github is that we share early material medium because our collection is on medium So then getting posts from github to medium to get formatted. Yeah, so yeah, that can Trouble uh, because yeah github sports the default, you know, the markdown format and for github for the medium it can get So you need to figure out like one platform where we can settle down and then Yeah, just go on please another reason These blogs could be published elsewhere and we are just by the nature and by the Quality or by the relevance of it. We are just reposting it in the medium. Yeah Okay, yeah So medium does have like a we don't we don't fully utilize it today, but medium does have a way for people to submit drafts For review, um, you have to request to become a writer Um, and then that's kind and then you can kind of go through mediums process I am a big fan of doing it this way because it kind of promotes repeat contributors Uh, because you know once they are a writer They can continue to be a writer at any time something You know, um something they write something interesting They can submit it and then every editor Of our medium publication has access to all of those drafts um, so really it would then turn into more of a um versus it would be more of a ensuring that our editors are either, you know, either we're assigning them or You know, basically that things are just sitting in the medium queue. Um So there is kind of a there's a more automated way to to use You know to use the the tools that we you know, we kind of have in place today um And I've done it a few times with with some of with some of the folks and it works out really well um, I think where some of the process Where we where we would need to maybe put some more process in places around assigning editors and recruiting Editors um But so I mean that that's that's an option as well. Um I don't know if we've got but there's Sort of more because I see that we took some notes around, you know, using github Which I think is also a good idea. Um, just because I know that a lot of folks Here use it so use the tools that we're already using. Um I'm gonna sell I'm gonna be I'm gonna admit to the to the group here I'm not a github Pro Again, I've just started using it since joining the linux foundation. Um, that doesn't mean I can't learn. Yeah, that's also Yeah, one problem because not everyone is familiar familiar with the github and everything they don't Like yeah, maybe someone doesn't write up some some things like some technical blog or some some Not related stuff, but they don't know how to like submit it to the open a pr Follow through with the details and updates. So yeah Yeah, the the kanban or trello style board I was talking about um on github Those are through I believe issues or they can be they can be pull requests or issues So you won't have you wouldn't have to commit code, but it's it's a moot point really I mean if you guys are just trying to get a board for that way everybody can see what's going on It can be trello can be whatever people are comfortable with that's fine um, one question I have is right now, um, so I I work for a company that we do Um, we we do training and we we have a site called hey node calm and we create Written and video content teaching people how to program in node j s So this could be something that I could potentially, you know help and help volunteer with I'd be interested to chat with you guys, you know looking at what that looks like, but um, I do also like the idea of the medium Like with that people can you know people can request to be a an editor or writer not an editor but a writer on the medium publication and they can Submit their own things that are published there so they could make it look how they want and then submit it um That would maybe make the flow for like getting uh putting out a call for submissions might be easier But then I'm curious about how then you need somebody in place who decides what gets published and what doesn't Yeah, because if no j s foundation or if you know if if node says hey, please submit your your posts There's a really high there's a good chance that you'll get submissions and they might not be high quality So then you need to have some kind of standard in place of um, you know, who decides what gets posted basically I don't I don't know how that works or if you guys have clarity on that right now Right now it seems like the bar to even submitting stuff to you is kind of self selecting for you know You get a much lower rate of submissions, etc um But yeah, I don't I don't have answers for that But I uh, I'm just curious if you guys have decided about like, you know, how would you What's the bar for what gets published on that? publication On the other hand my question is Do you have any complaints coming about the quality of the publications I mean, what is the motivation behind looking at improving the review process So So the I think the question there is have have I gotten any um complaints about quality? um And I I have not however I typically get I'm again, um You know, I'm not I'm not I'm not a software developer. So I'm not I'm not super technical when it comes to that um, so I have been working with um, you know, the technical members of the review committee to To make sure that it's good content and until you know, that's that's kind of goes to this next point about um You know more technical reviewers Because that can be a time intensive process, right? Reviewing this stuff making sure that it's technically sound um, it can take time and so um, typically, you know, what I'll what I'll do is I'll get either get um, you know, someone will submit something And it's a trusted source Or I'll go back to that medium Email alias and say, you know, hey folks I'd like to get back to this person, you know, and you know a week's time Can somebody just take a look and you know, let me know if this is You know thumbs up or thumbs down And that's typically how it works. I think we could probably um I think we could probably improve on that process as far as one getting more technical reviewers to kind of share the share that workload and also Totally open to giving those folks at it Because I understand that this stuff takes time. So whether that's, you know, a footnote or, you know, a thank you at the bottom Whatever it may be But just really kind of increasing that pool so that You know, um John is that your name? Yep. Sorry. Okay to john's point like when we put, you know, if we were to put out some sort of call for um, you know call for submission, we probably will get a lot and um And I want to make sure that this thing can scale So it's you know, when people are submitting they get a timely answer whether or not we're going to, you know, accept their Um submission And you know, it could be we accept it. It could be we decline it and give them reasons I mean, those are kind of things that need to be flushed out as well So there's been a couple of times where some things needed to be updated and so You know, we just kind of went back to the to the writer and said could you, you know clarify one or two of these things and then they resubmit and um, you know, that gets published but Content You know takes time and content is an investment. And so we would need, you know, obviously we would need quality content but we would also need, um You know the experts on the editing or on the review side to ensure that we are putting out Meaningful and helpful stuff from the community. So that's you know, that's Uh, yeah, I did I did I answer that question? Hi, Rachel, I don't know if you can hear me I can Oh, okay. Can you hear me? I'm loud enough. Hi, my name is Erin And so I come in a little bit late to this discussion and I have a question which is Why? So I think that we all agree that there needs to be more high quality content about nodes And so is there a target user that we are looking for to read this material because someone just new to know We need a different set of content than someone who Is in the middle of their note career or someone who wants to become a core contributor So, yeah, that's yeah, exactly That's uh, one of the points we want to discuss and highlight that what kind of content we want on the our publication We can drive like three or four type of channels one for like experts one is for the beginners where we post regularly on There should be like a topic for the beginners every week or every twice a week And then there should be a topic for intermediate one and there should be Topic about like getting the reviews and then Yeah, yeah, how do we know if this is successful? Do we have traffic goals? Is there a conversion goal? Is there a sign up for a newsletter goal? I think without a goal We won't even and the goal can be like a purely Quantitative goal of like we want to publish X amount of articles in a wide time period but Without a goal set out It'll be really hard to decide whether it's worth the effort that we want to put into it and to get people on Board because they won't be able to go back and say I feel good because I helped get to this milestone And then the last thing I want to ask. I'm sorry to ask so many annoying questions I actually used to run a small magazine. I used to work in publishing. So like these are the annoying questions that people in publishing ask There's already a large community of people who volunteer to judge content for the various node and javascript conferences What about using the conference presenters as a pipeline because if you're presenting a 20 minute talk Turning that talk into a blog post Is not all that much more effort sometimes? and so saying hey Your talk got accepted and you know an attractive Let me connect you to the blog people And so that's one way of vetting if they've already been accepted to the conference Can we encourage them to write a blog post for people who don't like to watch videos? Sometimes the video is not very high quality or there's a glitch and it's a different way to reach people that's not tied in Um and people who have already signed up to review No And they they passed some sort of filter. Yep Which I I'd like that idea at least because there's efficiencies there and it removes some work and removes people from the process Etc. So really reusing content is a great idea and another thing to do like which you can steal from the world of academic publishing is just to be like August is streams month Right and have put a cfp out like far in advance So like three months in advance. So You have an editorial calendar. That's about we want Intro content. We want intermediate content and we want like how to help content on all these topics And then just have a call for gamers The same way as you have I love I love that. I love both of your those last two suggestions Wow, like those will I will copy we will copy and paste those into our proposal to kind of improve this those are wonder those are awesome. Thank you um I do have a question just not to not to answer not to answer a question with a question but for the um You said you know for for things that are vetted um already through Like conferences. Um, are you talking specific for Like obviously we have the the interactive conference in december you talking about that or are you saying like there are I mean, obviously there are other conferences that are you saying to kind of do outreach to speakers at those conferences and and and fill the pipeline That way as well Right, you can start it with the conference that you have the closest connection to right interactive, right right, so let's look at the Look at the calendar, you know javascript across the year reach out to the organizers and say Hey, we would love to feature your three keynote speakers on the blog if they want to write a six to eight hundred word piece about Why they think yeah, it's important and why everyone should know about it. And then you get a two there to get like uh, the last time I gave a talk at You don't interactive it was about All the array methods because I love arrays Right, here's all the things you could do with arrays And I never turned that into a blog post because it was a jupy turn of books that you could play with um But if I were going to do like another blog post that here all the stupid ways to log things right then If I was going to do that talk if I got the blog post out Either around the same time or just a little bit before the talk it helps me write the talk Because you can turn the outline for the blog post into the talk And then it's promo for the conference Right, right write that blog post. I'd be like here this here the three main things you should know About arrays or here are the five gotchas when using array methods and JavaScript To hear more about this Come to this conference in here the talk Yeah, but uh, one point I want to raise with that But if if you are already a speaker on talk you can get the You get the viewers attention you get the word out But like if if you are new into blogging you don't get a chance to Speak at a conference that does that stop you from sending a blog post or making Your first contribution things like so we yeah, we can we can filter out We can take always that that would be the best scenario, but we should be always be open for the newcomers who maybe who don't have our talk or conference, but the post itself is A nice and the quality of the content is good. Yeah I think mentorship works really well for that because it helps with the quality bar because usually if you're new to both writing and coding Some help translating within your head off the page I'm wondering like I know there's some various node mentorship efforts going on now. Yep. I'm wondering if it's It's worth thinking about how to do node mentoring for blog and technical writing as well Yeah, I want to put something out there real quick that I some thoughts that I wrote down while I was Listening to all that and what I was hearing from from you and I loved I loved your suggestions specifically one of the things some of the things I heard from it was Reusing content is great because if the speaker's already invested time they have something to talk about and what what you said about I'm sorry. I don't remember your name really believe. Yeah. Yeah. What elite said about Not setting the bar being more equitable and being able to signal boost new people So that that made my mind start thinking about like one's very important thing is Whose mouth is this content coming out of? Who because there's we're gonna have to review the content regardless, but it It depends on where we set that bar and part of it is the messaging around The actual content itself in terms of is this coming from Is this the node j s? You know folks boosting user created content or is this node j s Stamp of approval. This is a good idea and that last one The bar is so high on that that i'm very lazy And I want to figure out ways to you know like that there's so much effort and quality that goes into Verifying that and I don't think any one person Can decide you know what what node j s would stamp with an approval But specifically on medium and specifically with collections Um the workflow and what the pipeline and what people are used to is typically collections are ways to boost other authors And if you submit as a medium user It gets posted onto the publication with your name as the author You know and so it's very clear who wrote that content and who says it and whose voice it's coming from And the collection is just collecting it. So I really really like the idea of Putting out a theme because that's minimal effort for the you know We can decide those a whole year in advance and then you can put out the um You can give the opportunity to any developer any new developer Of hey write something about this and then you know, we'll still have that bar technical review Which we which you know people can help with but we'll set it much lower Because it's no longer saying this is a node j s stamp of approval thing But it's saying here's people from the huge community we have And here's us signal boosting and using their content not using it like giving it a bigger platform so then the work that is involved is more aligned with Being that gatekeeper but setting that bar as low as possible with not as low as possible But as low as is useful and is something we can all stomach While saying Hey, we don't necessarily endorse all of this content You know like we haven't vetted all of it. We've technically reviewed it and we're it's good enough to get up there But you know, this is someone else's this rep. This is not coming directly from the mouth of node j s So don't don't put this in a production and ensue us over it or whatever right have they changed the thing on medium where you're Your posts on medium can only be in one collection at a time They haven't so what you would have to do is start a new post but that's that's a really good observation I like that idea of Having tiers of content. So right there's content produced by people from The foundation there's content produced From events related to the foundation There's content on these themes and then you can even go one step below that and have link roundups Yeah, yeah, link roundups. Yeah, and then that's a nice way to like Say somebody puts a lot of time and effort into something and but it's not quite at the level you can say hey If it were shorter or if it had more examples or you know, if it were written against no 12 It's done no 10. We would have accepted it But we'll put it in the link roundup And I'm just looking at the collection and I saw a lot of stuff posted by rising stack and it looks like Yeah, they have a huge content marketing arm. It looks yeah, I didn't look directly at their content too much But it looks like they're doing link roundups already. So that's one thing potentially taken care of too I'm basically, you know, I I want to volunteer my time to help you guys in the way that I can Um to do something like this because it's it's it's within the The my organization like the company I work for we have some some experience doing this stuff But also I'm looking at it in terms of um, how can we mo how can we best leverage the Community around node js to do as little work as possible But still give the most value to people out there and also like it's thrilling for a new developer to get Their content posted on the you know, the node js collection And so we could even honing in on that specifically for now or you know, this is just my opinion, obviously But I feel like that would be the lowest effort quickest way to value for both the foundation or for node js And also for the users because if you just get that one person to do the technical review and say that none of this is Abjectly damning our system or whatever. So here we go, you know If you can get people to submit it through medium And yes, they would have to create their another pop another post But that's the way it works with every collection on medium Um, and it kind of helps streamline that process in my mind So I feel like that would be something that one or two people could own pretty well Um, and then you know as long as one of those people being maybe a technical reviewer or at least getting some people to Cycle in through that role etc But I that that sounds better to me specifically than Trying to set that bar too high or if if a the thing about the conference speakers um I don't think that a lot of the conferences are affiliated with node js in any way I'm not actually sure how many are So it would be kind of difficult to even use that as a bar quality specifically Because how to at what point do you draw a line of what's you know, who's a good speaker who's not? I wanted to surface a bit of experience from Getting people to submit talks to a theme uh If if this is going to be pursued everything it should be because like themed editions would be great But it needs a fair amount of lead time because Making sure you get enough stuff to fill an edition that is themed means that you're only able to accept for each edition A subset of ones available to you. It's a really good observation. So you'll need to Make an editorial calendar for say a year in advance, but have it start say A couple of months in the future to have enough time to accumulate But but it's a great idea and it really should be done And I sort of just one particular publication as a great example of how of theme editions Stripe the the publication called increments And it's beautiful. Like when it comes into my email Great, and it's also very minimal brandy you can't help So yeah, so I'll just Go with a with a few other Topics we have to cover is one of the point is to how to get Writers to review in return or maybe how to In incentivize them for the in the review process because if there is some incentive kind of then you get you can get Easily more more reviewers Oh, yeah, so any thoughts anyone have about uh about Badgers with stickers man Yeah Yeah, and also maybe Reaching out to technical writing communities like write the docs because they may not They may not be daily node developers or job script developers, but they have experience reviewing technical content Yes, and if there's a big theme like jobs that write the docs to left you get Portland There's a big theme about how to become more involved Which one would you say uh, oh the conference is called write the doc And there's one important and there's one in prog and then one in dill me this year And that's thinking about you in an ecosystem. It's a very and there's also api the doc That's great. Yeah. Yeah, uh, there's write the docs also in australia Yeah, they do the other kind of everywhere now. Yeah, there's other docs And yeah, and so one thing that makes technical reviewers jobs in here is having a style sheet and a style guide because one of the things that's a pain about reviewing technical content is like Google style guidance that open source is always two words and it never has a hyphen Yeah, and if you learn some other style than you You're always trying to check it in your mind. So every time that something is reviewed You also want to incentivize the reviewer to add something to the style guide Like I have decided that when we talk about this it's capitalized this way Well, we link to this source. We'll be talking about that Menial, uh It was related to incentivizing. Um, so it's not the Rachel, can you hear us clearly clearly? Oh, I'm sorry. I haven't I can yes No, no, I can I can hear you. Um, yeah Um, I'm just taking notes I'm gonna surface a open issue that's out there right now For a no jest thank you program For which this would be a like great candidate to actually have swag for so for context that issue was opened a little while ago to help thank contributors for making commit to no jest and Rich already does something to thank contributors. I'm really happy for what but I know he does something because people have said that on the issue but We were thinking about Giving people swag that their contributions Will like entitle them or reward them with So we have a store right now that is the no jest store. The thing is right now, there's some There's some like shipping is a little expensive and I don't think a lot of people necessarily order from it Um, but I've been talking related to that. Thank you program I've been talking with a couple of the folks that gasping jest who have a great thank you program um, and they have Uh, I said that they're willing to share I help us implement their open source code base for their shop Um, so their shop uses the shop is by sdk In javascript and it also they have their own system for using Generating coupon codes that are usable in the shop Based on people logging in with their handle So you can check like their contribution So they're willing to help us implement it which saves us a bunch of time Not to mention we don't have to re-implement any of the stuff that they spent like three four weeks full time working on Yeah, um, and they're very keen to like actually like share it They're a great group. They're a great group. Um, and they said, uh, Like we had discussion about it. I don't have hard numbers, but their contributions have gone up and people actually do use it Um, and it's their way of just saying thank you Usually people are given for a shirt or something and shipping costs are lower than Than what they've said it's lower than what we have so far faced and if you have seen issues There's so many design issues in people in javascript that they could make Yeah I just want to um real quick on on how to incentivize and how to get more technical reviewers I think it's very tightly related to how to get um more contributors in general in that um Like low barrier to entry I guess like low friction for that way low friction meaning I want to put a differentiation between technical review and editing Um, because I've published on other collections before and they didn't edit any of my stuff They're high volume collections that are just churning churning churning stuff out As a result they get a lot of followers and they're more attractive to You know, I'm not saying that y'all should be a high volume thing, but um When I say technical review, I mean just specifically in terms of like Is this a spam malware like filled article that's garbage or is it, you know, it like does it meet the bar of This person tried their best and if I think that if we framed or if it was framed around Hey, like in vp version, I guess that I'm lazy I'm imagining how can the fewest number of people make this whole thing work with the largest impact And I think that specifically having One person do a technical review, which is mostly just read through it and this you know Is it garbage or not? Or is it did they do did they do try their best or not and frame it around This part of the bulk of the collection is a signal boost to other people, you know That's what comments are for if it's garbage people are going to tell them or they're going to try to correct them or do whatever Obviously, you know, we don't want flamers, but that's what the review is We don't want something to get through which is going to damage that person themselves and I think that just so putting a differentiation between editing and Reviewing it because editing will increase the the style guide is, you know, that's how my company works That's how every publishing company works and it's how you should do it But um, I don't think that we really have the resources right now We not from my perspective on this to be able to really edit people's stuff Um, and that increases the lead time and increases the cycles of everything So I think that if people can submit One person could sit down Every week or every two weeks or every month or whatever You know every week maybe two whatever however many days and just boom boom boom boom check and decide and then they just move Things through the pipeline and then maybe somebody else can decide what actually gets published win or whatever Um, and maybe the maybe the mvp version of it is just trying to work out that process to be as smooth and Low friction as possible and then we can figure once we have a volume and a following Then we could figure out how to do the theme stuff more specifically because like like many you'll make brings up a good point You're with themes, you know, you're just selecting a subset of what is being published And it's not that and it's not that incentivizing for people if Oh, wow, I submitted that article four months ago And now it finally is getting published because my theme finally came around So I think that once there is the volume of people submitting and it's that happy feedback cycle happening Then we could probably y'all could do the um The themes or whatever more effectively. I think it's a great idea and I would love to do that But I think in the meantime, um, it's a it's a big process challenge currently And if one person can really be the reviewer or the gatekeeper who is you know They would have to have some kind of technical expertise at node and want to do this Hopefully there'll be 10 people doing it But you can only really count on there being one person and if that person and then assume that person is overwhelmed You know, that's the way I look at it. But that's how I think to get more technical reviewers And that's how I think we could incentivize the reviewers themselves is make the process as painless as possible Because if you have 18 different reviewers, well, are you really controlling the quality that well? Or is that person Favoring other people, etc. So fewer reviewers that are closer to the team or closer to all of this I think is is best in my opinion. Maybe there's a small like walk committee or something Yeah, or no something like that. That would be great. You can also back to your way into being by Setting them for time to be no people are going to be writing about that. Anyway, for example, uh, October Oh, no projects that are exciting for half that's a great idea And then, you know, since we know pretty much when Versions are going to go into long-term support. You could have hey write about how to upgrade And on that is also a hard thing for your people to do Yeah, and hacktober specifically for anybody not familiar is, you know, a big event that happens Where people try to, you know, like come together and hey during this month do an open source commit or something I think that's the way it works But also there's huge communities that are even bigger than node j s that we could tap into like 100 days of code If you could offer like hey, this is our MVP version is or part of it would be like, hey, if you're doing 100 days of code This is our 100 days of code You know track or whatever that we're, you know, like if you're doing 100 days of code and you're blogging about it Anyways, which you are if you're doing 100 days of code and you're doing node j s submitted to us And we'll signal boost you and look at you, you know all this stuff So I feel like, you know tapping into where that content's already being created Having the processes in place to be able to review it, etc And then at that point it's 100 days of code. They're newbies. They're learning And so the bar is a little lower And then that I think you can work out your process and get you know And then those people are going to share the heck out of it because you know, so whatever Yeah, I want to have people would submit those or recollect them, but yeah, but that's a cool idea. So Sorry No, no problem. So the next, yeah, we got enough. I think you're not enough but some feedback for this The next point could be like Which kind of surveys do we should we do for our blog post for the content which we want to drive or for like They should be a roadmap similar to like I have a special team for each month, but there could be a roadmap for for For the whole Node.js ecosystem that we want to drive like there's a new coming in and we want people to adopt it the new Feature the new functionality which are we going to provide in a year or in few months into the next quarter We can drive the whole community through through the publications and what we put on the social media So, you know, I you say you know reader survey is here about how to get input on news topics But I would be super lazy and just go ask Peter Cooper who runs young weekly and jobs through weekly What topics are the most clicked on? Yeah, I bet he would share that if he thought that it would lead to more content that we could link to Yeah, okay And also in the beginning if you have a high high issue volume of publicate of big things being published You can you know let it go for a couple of months or something and take a look at you know What's driving the most engagement? That's not a perfect heuristic by any means And also there's a good argument to have You know what you asked a very good question, which was Aaron, which was what's the goal? Why why are you all doing this part of it is to one? Put better content out there, but two to also be able to drive eyeballs to important things in the node ecosystem um So I you know having that direction of like, you know We want to be able to highlight specific things which are important But also in order to even get that audience you need to have a volume of you know You need to have a reason for people to follow the publication to begin with so Okay, so yeah, we can we can now jump on to like specifically social media like uh, facebook twitter Maybe LinkedIn, uh, what do we post there? So, uh This yeah, it's the Rachel go on. Yeah, okay. Yeah, so, um Just a little bit of background here. Um Another thing that we are trying to do is just create more collaboration Um between uh, you know the the the foundation and the project in the community with social media um One of the things that was proposed at a comm comm meeting several months ago was to have a To sort of have social media chairs so people from the community that have access to Our publishing platform, which is throughout social to help, you know, um, you know identify tweets Edit tweets curate tweets all of those things and just just, you know Work with engagement just kind of be a counterpart You know to to me on the foundation side and you know, just to kind of again improve content improve engagement um From a social media standpoint The second bullet here is is talks about the social media chair initiative, but I know that a hot topic is also just um, you know safeguards in place around, you know Code of conduct and things like that. So, um, again, this is just another initiative that we're, you know trying to Put some thoughts around um and put a plan around and to start, you know executing on um, you know just so that you know folks Have other ways to participate in this community. Um, that's not just code related Yeah So yeah for for social media chair, it's uh, I think in at the end it's kind of a A reviewer or what writer does for a blog post it would be the same person doing the same kind of stuff But for the social media not for a blog post they can they can review they can filter out They can point out what what should be highlighted, but should be posted or like but yeah Any thoughts or any ideas if anyone have about such initiative or any feedback One I see I think a The simplest question to answer because there's a lot of hard questions in there. Um, I think would be, you know, what platforms Would would be best to focus on and part of that goes to the why of you know, why why are we on those platforms? Why why is Why would why would things be posted on those platforms, etc? Um, and you made the point, um Rachel you made the point rachel that the goal is to create a collaboration between The no j s org and the foundation. Um, so I You know, I could see like you know coordinating posts like oh, hey There's a big announcement with no j s and the foundation could post that node could post that or Things going on with the open j s foundation those could get kind of passed down from, you know From the org from the open j s to whoever that social media chair might be but I I also feel that initially, you know Limiting it to as few like I'm personally and this is just my opinion literally I don't know if Facebook is the right place for that or if engagement is specifically the the goal then it would be, you know Where where can y'all get the most engagement, etc? And um, maybe twitter is that place? I don't know but I think limiting that scope to like what what platform would you guys want to focus on first Otherwise it could just be Here's the messages we want to put out and then you just schedule them with you know Sprout social or whatever to get blasted to You know the instagram twitter facebook like all of your have the same message to go out across all channels Which is the the least customized approach, but definitely the most hands-off like autopilot kind of thing um I don't have any answers to that specifically um I would love the video stuff would be exciting, but also that's like A lot of production and a lot of work For youtube or whatever so so I don't I'm not I'm not so sure what or how it should be done But I think answering the question first of what platforms are the most important and what specifically Is the goal that you're trying to achieve there is an engagement. Is it just to have a presence? Is it like I see further down on the on the on the section To highlight things in the community which gets difficult because then it's speaking from the mouth of the node j s which is Unless the whole organization can agree on what things it wants to highlight Maybe it could it gets dicey to you know that one social media chair would Know somebody would always be upset about something basically But there could be things that could be agreed upon Foundation-wide that could then be you know promoted or whatever. Maybe come from the foundation that are approved or whatever Yeah, I agree with you And I especially think that Maybe a very simple place to start is to just have one twitter account Let's be official foundation account and it tweets Incredibly boring but authoritative things that are like It's the new release when the next conference is this is like how you contact Various people and it's just on the schedule between once or twice a day and then You fill up a queue with fairly safe things. Yeah, because twitter is really noisy right now Facebook is like you can't even think about who's going to see what you post Like if you might as well just go shout off the top of the skyscraper Um and then linkedin I think like it also has the same problem that is very very anything for them So my my gut would say start with a boring administrative twitter account Yeah, or like signal boosting the More official things published on the collection You know, you could set up to post to linkedin to post to twitter or whatever the simplest kind of those can be automated Even is my point Um, but the safer stuff or I could just say hey, we posted a thing But I think smaller volume more focused Would be the most manageable right now and also would upset the fewest amount of people probably One of the things that I find that are that the community really likes are like open-ended questions Um I find that those are the ones that we just get so much engagement for and lots of retweets And so what would be help? I know for like what would be helpful for my perspective Is to kind of like understand What people want to know about and and what what some of those questions could be You know and that kind of goes back to the potentially the reader survey That I was kind of that we kind of outlined I mean it's also interconnected, right? I mean it's It's just that's just how it works And harder than doc with just questions to ask even even better than that sorry to cut y'all off Keep if we're talking about twitter because that's a super, you know for this community It's a super popular platform double thing. Yeah double Or votes could be but even forget even that just a hashtag Just a hashtag and then see what gets the most likes, you know And then call from that basically and say Okay, and you know you could either retweet other people's questions Which would be super easy. You could just get one person logged in You know even still then it's kind of difficult to You know somebody has to make that decision But if you go by like Here's the hashtag to ask questions and then the node js account will Either phrase them in its own voice because it could look at the aggregate and kind of distill it Or it could be as simple as just a human retweeting ones that are good But even that actually let's not do that because you don't know who you're retweeting that could get messy But if you just have a hashtag where people could ask the questions and it's already on the platform It's already people that are going to see it and be engaged Um, and you know you could take the aggregate and take the individual out of it But just see what the themes are or I don't know if it's a really specific question and they're a known community member Then it would probably be safer to credit them, but um retweeting is often seen as endorsement. So it's you know Yeah, it can go through. Yeah, but we could yeah, we could do like AMA node. Yeah, AMA node that'd be cool. Yeah Yeah, I mean it could even you could even and then the node account could jump into 100 days of code Or girls code or like a bunch of the really cool community hashtags and just go You know like hey, we're doing AMA blah blah like ask us questions and you know just signal booster Jump into that stream of crazy content. That's always happening. So I'm lazy like I said very This is to Adopt what's going on in the community on in the current days like if it's what's the new conference going on What's the new event is going on? What's happening within this this week or this month and we can boost the content and the quality of social media Post through that like if it's a tuba press the going on if it's 100 days of code or similar topic Yeah, and also we talked a bit about incentive and there's so much power behind the node js brand. There's so much reach So much and so there's questions that I would love to pick the node js community's brain about And so that's why I would tweet a thing which would be like How are you guys using streams? Do any does anyone understand streams? You know like that's a question. I would love to see The community at large go you know decide whatever they're going to say about it. I'd follow that thread So that's exciting to me just as a as a consumer basically What what Could go wrong about about being specific about some technical detail is the same There would be some folks who don't who get messy and really picky about some specific point that yeah You guys are not going to pick the issue in the streams. I'm like, yeah Yeah So that that comes down That comes down to voice in my opinion and with the voice and character that we tweet those things from would be uplifting positive and inspirational that would you know words you could throw on a you know word cloud or whatever But there is like code newbies. It's a big community. They do a lot of stuff where it's just like What are you working on? You know or Yeah, or what was the last time you failed or you know like tell me a story about you failing or you know something that's at least has a A whiff of uplifting this of share your last error message is always fun. I haven't heard of that. It's hilarious Yeah And that I feel like that builds community because you get to discover other people in that thread and it's around a shared interest and experience I don't know if you all follow the developer swearing twitter account. No It's a bot to just get commit messages that includes profanity Or like yeah, your last your last commit message is a good one too, but Okay, so yeah that that thing or maybe I'll offer all all doing all these things Rachel, I don't know. Maybe you at this point. Maybe we don't need a social media chair person May I don't know. Maybe you can handle Maybe we can focus more about quality and type of the content then just Just throwing stuff Yeah, but yeah, I don't know just just thinking just it came into mind that maybe or Maybe we don't need more content. We need more quality and more specific and some theme content kind of thing More curation. Yeah motivation. Yeah, I yeah. No, I I definitely I definitely heard that I think the idea of bringing in a social chair was to kind of Help guide some of that as well someone who's more embedded with the community, but I you know, you know, but I do see I I do see I I wrote down all the questions. They were really super funny and I do see an opportunity to To just do some different things. So this has just been eye-opening for me. So I do appreciate that Yeah Yeah, yeah, that that's I agree with your point. Yeah, everyone here is super happy. So yeah, yeah, social media chair could it's not just about Yeah, getting the content A specific person from North community can also help you guys Uh, the one managing the social Community channels to Like what kind of questions would be good? What's which things the community likes? Yeah, I think it would be good if that person is a deaf person who knows a bit about Uh, the things we have I it sounds like it I'm assuming but what might be an ideal workflow for y'all is like A spreadsheet with a whole bunch of topics that somebody or the community has already Vetted or you know, whatever it's like that way you can you can worry about just scheduling and getting them out there Yeah, and you know like if you can asynchronously do the work or someone else can asynchronously do the work Where they're like, here's Three years a month's worth of this or three months worth of these questions like one or two tweets a day or something like that Um, because then obviously somebody would need somebody who knows the community would need to really select that stuff Um, but then yeah, definitely, you know, maybe that would be the social media chair perhaps One of the things one of one of the things to your point one of the things that I find helpful is um, you know Obviously, I've got I've got twitter on my phone. Um, and I'll get a direct messaging This is a really interesting tweet or this is a really cool kudos or whatever. So that's something that like, okay I'm going to retweet this or like this or or something. Um And and I'm it's 10 out of 10 times. They're always great recommendations Um, and so just things like that that kind of help Um, you know people who are sort of in it um A little bit, you know, not say that I'm not but they're you know, there are people who are coding all day and they're you know They're just you're up to summit um Things like that are just helpful. Um, just to kind of and it's you know, kind of helps guide Other things that I'm looking for that that's the community will find helpful So I'm sorry. I think I interrupted you. I interrupt someone. I'm sorry Now that makes a lot of sense. They only have to think that I would add is that it's often good to have somebody who's on call Just because you know, let's say haven't forbid the queen passes away. We don't want like your tweet to be in the stream right like When when big terrible things happen. I feel like brands need to turn off their twitter feeds for a while Yeah, yeah You don't want to make a ill time joke. Yeah, I have a bunch of weirdly chipper tweets when there's some huge tragedy in the world Like if there's a terror if there's a terrorist attack in a conference city where a conference is happening You're like y'all having a good time involved love That's that sounds like a compelling reason to have um, some kind of social media chair who just has their thumb on the pulse I mean Tierney is probably too busy. But like that's the per that's the the spirit of somebody who's in the community Connected knows how twitter works good. You know and is like Able to they're in the middle of those things where they could curate it and even if it just means filling up your inbox But that's just me being lazy again Yeah, that's a really yeah Or maybe those are the people who but I don't think who got affected by the by the thing actually ended. Yeah. Yeah You can't turn off the tweets without because there's been a hurricane in the city where the Yeah, what were you trying to say, menial? We're having you know having several Some methods some somewhere out there where there's a couple of trusted people who have the log in or something Right, because you know what the bust factor of the twitter account to be one, right? Yeah Yeah from the bust factor. I like that Somebody gets hit by a bus, right? So, yeah, the one last point what idea was to manage the twitter or account through the github so that once like you can log in I think into Twitter through github profile and you get the access but then you know what the person who is Who is some submitting some post who's who's the person behind? But yeah, I haven't seen this but This idea was shared In an in another talk See I can Um, you'll know uh at six the dinner was off the starting so Oh, it's six now. Yeah Yeah, that just started mentioned so So that's at America Okay, this is fun. Yeah So, uh, I think I think we're good for now. Okay, because yeah, we are almost over 10 minutes Yeah, yeah, it's been a good conversation. Yeah, it was really good. I've collected so many They've taken the note we can can continue the Talk we can set up a one-on-one meeting leaders. Yes. That's that sounds good I think um, I think what also what I'll do Is take these notes and maybe synthesize them into just like a recap of what you know what we discussed and They're maybe put together some initial recommendations based on this. Yeah, but it was super awesome I really appreciate you know you getting this together. Um, and I you know, I think we'll get really I think I think the next steps will be really really positive for us. Yeah. Okay. So great. Thank you. Thank you. Yeah