Turndown message #803
Turndown message #803
Conversation
rgrandl
force-pushed
the
weaver_turndown
branch
from
7569d55 to
58a4a23
Compare
README.md
Outdated
| </p> | ||
| <p style="color: inherit">We greatly appreciate the continued advocacy and support | ||
| of the Service Weaver community. However, we have learned what we needed from | ||
| our exploration, and we regret to announce that, <b>effective December 5, 2024, |
There was a problem hiding this comment.
Alternate wording suggestion:
However, we realized that it was hard for users to adopt Service Weaver directly since it required rewriting large parts of existing applications. Therefore Service Weaver did not see much direct use and therefore effective ...
website/index.html
Outdated
| @@ -27,6 +27,13 @@ <h1> | |||
| <a href="docs.html">Read the Docs</a> | |||
| </div> | |||
|
|
|||
| <div class="announcement-banner"> | |||
| <p>We regret to announce that, effective <b>December 5, 2024</b>, we will no longer be able to | |||
| continue active development on the Service Weaver open-source framework. For more details, click | |||
There was a problem hiding this comment.
s/no longer be able to continue active/no longer continue/
README.md
Outdated
| <p style="color: inherit">We greatly appreciate the continued advocacy and support | ||
| of the Service Weaver community. However, we have learned what we needed from | ||
| our exploration, and we regret to announce that, <b>effective December 5, 2024, | ||
| we will transition Service Weaver into maintenance mode</b>. We recommend that users |
There was a problem hiding this comment.
The sentence "We recommend that..." is a bit in the way of the overall flow. I think it can be removed, or maybe moved to the end of this paragraph.
There was a problem hiding this comment.
Good point. Yeah, I felt the same. However, we should let users know what would be a better approach maybe (to fork the repo). I moved that sentence to the end of the paragraph.
README.md
Outdated
| </p> | ||
| <p style="color: inherit">We greatly appreciate the continued advocacy and support | ||
| of the Service Weaver community. However, we have learned what we needed from | ||
| our exploration, and we regret to announce that, <b>effective December 5, 2024, |
README.md
Outdated
| <p style="color: inherit">We greatly appreciate the continued advocacy and support | ||
| of the Service Weaver community. However, we have learned what we needed from | ||
| our exploration, and we regret to announce that, <b>effective December 5, 2024, | ||
| we will transition Service Weaver into maintenance mode</b>. We recommend that users |
There was a problem hiding this comment.
Good point. Yeah, I felt the same. However, we should let users know what would be a better approach maybe (to fork the repo). I moved that sentence to the end of the paragraph.
No description provided.