Welcome to Newsletter Discussions!

[JFWooten4]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[JFWooten4]

I think @AltairAster was running into some permissions troubles last night, possibly because of that incidental spam challenge thing with their new account. If they want to actively participate in the Newsletter repo, and especially if they want to add some custom technical plugins from #1, then I propose adding them as a repo Admin.¹

Footnotes

1. Maintainer should give them any tools they need to connect with publication or interfacing apps, but I don't think we really need to make this distinction here just yet given the complete lack of any coding work done yet, and the clear drive from Altair to make something happen here. ↩

[JFWooten4]

Shit, color me corrected – thank you, James! Enabled now ☑ I think it's super important we let everyone voice their ideas in any form that suits them, and certainly would have done this if we knew earlier 🙂

The setting below "Integration access requests" seems interesting—maybe that could help with the integrations Altair was brainstorming without a permissions change. I have no quarrel with their upgrading, but it could help in the future for new community members to experiment with external tooling and help innovate when permissioned access could have been a roadblock.

[JamesAlfonse]

@JFWooten4 we can take another look through the member and admin privileges and maybe do some testing during Wednesday's meeting to make sure that it doesn't impede on progress but also ensures security. Currently, I believe only members and above can create new discussions in any repo, and non-members can comment within already open discussions.

I did a quick search for popular Github orgs and found this one that has 230 members. Their most popular repo has 188k stars and includes 3655 collaborators, just for reference.

[JFWooten4]

Brought this into WhyDRS/Taking-Stock#24 as a potential collaborator. Just as a minor aside, I think most of the security items matter more largely for private/proprietary work. As far as I’m concerned, we just need to protect the repositories and their community content from WSB-style mismanaged admin. And given the transparency of activity on here, akin to the Lemmy admin log, I think the biggest risk would be anyone unilaterally deleting a whole repo or work item. The rest should be simple enough to piece together as I see it or reverse Git histories.

What do you think, James? I know and appreciate that you’ve been a big proponent of security.¹ Love this and value your take on any access items!

Footnotes

1. As another aside, I know you’ve wanted the LinkedIn side of the org to grow by means of helping traditional career paths and personal positioning. Super OK with you starting that up if you’d like. When I made the GitHub, I just did it and then invited Chives in. Presumably, we can add a social media manager or such as an admin down the road. ↩

[JamesAlfonse]

@JFWooten4 With our work being out in the open and fostering an environment of transparency, my biggest concerns are Integrity and Availability. We should strive for high availability and data that we can trust/rely on; having the proper systems and procedures in place can be a big help. A whole repo being deleted sounds bad, but a repo that has multiple missing directories and new directories mixed in there over an unknown time period of changes would be a shitshow to remediate. As the association is still small it's the perfect opportunity to learn and understand the limits and nuances of all the permission options Github offers, and it will pay off in dividends.

I'd love to get the ball rolling on that LinkedIn train, but unfortunately I don't think I have the time to really give it the attention that it deserves. I wouldn't want to start it just for the page to get stale and eventually drop out of the algorithm altogether. However I would love for someone else from the community to pick up that torch and really flesh out a comprehensive social media strategy!

[JFWooten4]

100% agree as to now being the time to get these items understood and implemented to reap big dividends down the line! I agree and appreciate the nuanced perspective on integrity and availability.

From the article, I would hopefully think the data duplication and deletion protection is relatively safe given the style of forum here. I've never had any challenges with GitHub really losing something meaningful.¹ With you on keeping everything in line.

As for LinkedIn, I'm sort of in the same boat in the sense that I've given up on creating anything to serve their central algorithms. But yeah, completely with you as for supporting media strategist apes.

Footnotes

1. Aside from a couple small user-side errors like closing a tab down in the middle of an edit change. But, honestly, by and large, they have some incredible safeguards in place. I'm not sure if you've noticed this, but you can refresh the page when you're writing a comment like this, and it will save your work! You can also start writing in a new commit, close the tab (and press OK to lose your progress popup), and then it will have a "recover past work" button when you reopen it. Really impressive! ↩