You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are close to the finish line for v2 of the guide. The last remaining bits, I believe are:
Including sections on tutorials for each of the packages (I'm working on this now)
Final typos, style changes, etc.
After that we will want to publish a blog post announcing this new version.
However, I think that we can probably work on the blog post now. That is, we don't actually need to finish these last bits before someone starts working on it.
I suggest we assign someone to work on the post now, and aim to have that plus the two tasks above done prior to our next meeting. That way we can devote next meeting to discussing not only where / how to publish the blog post but brainstorm any additional marketing efforts we want to do to raise awareness of this new version of the guide.
The text was updated successfully, but these errors were encountered:
One basic thought re marketing: when we finalize v2 and make a blog post, we can contact the authors of all the packages we included to let them know about the guide, and that their package is included.
We are close to the finish line for v2 of the guide. The last remaining bits, I believe are:
After that we will want to publish a blog post announcing this new version.
However, I think that we can probably work on the blog post now. That is, we don't actually need to finish these last bits before someone starts working on it.
I suggest we assign someone to work on the post now, and aim to have that plus the two tasks above done prior to our next meeting. That way we can devote next meeting to discussing not only where / how to publish the blog post but brainstorm any additional marketing efforts we want to do to raise awareness of this new version of the guide.
The text was updated successfully, but these errors were encountered: