Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Healing a damaged team while continuing to deliver business results #48

Open
semioticrobotic opened this issue Jan 21, 2020 · 6 comments

Comments

@semioticrobotic
Copy link
Member

Article on this topic is incoming from @ldimaggi.

@ldimaggi
Copy link

Actually - I'd like to try to write a different article - sorry - can you mark this one as unassigned? Thanks!

@semioticrobotic
Copy link
Member Author

Done and done. Thanks, @ldimaggi!

@ldimaggi
Copy link

ldimaggi commented May 1, 2023

I'll take this article - again - thanks!

@semioticrobotic
Copy link
Member Author

Thanks, @ldimaggi! I'm delighted to see your interest in this. I just want to check with @AmyJuneH about the Opensource.com team's capacity and the publication's current position on accepting new submissions.

@AmyJuneH
Copy link

AmyJuneH commented May 3, 2023

I am very unclear the status of opensource.com.

I believe that they are no longer accepting new content, but are commited to publish the content already submitted.
I would check with Lauren. I longer have access to any of the tooling or email since the layoffs.

@semioticrobotic
Copy link
Member Author

Thanks, @AmyJuneH. Hang in there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants