|
| 1 | +# Support for Projects |
| 2 | + |
| 3 | +The OpenJS Foundation provides support to projects as follows: |
| 4 | + |
| 5 | +* Facilitating communication between the larger ecosystem and |
| 6 | + projects. This includes: |
| 7 | + * Javacript Newsletters and Periodicals |
| 8 | + |
| 9 | +## Communication Javacript Newsletters and Periodicals |
| 10 | + |
| 11 | +There are a number of great newsletters and periodicals. Getting articles |
| 12 | +into these newsletters and periodicals is one way that a project can share |
| 13 | +key messages and news but they often don't have a good way to do this. |
| 14 | + |
| 15 | +Further complicating things is that developers and those managing newsletters |
| 16 | +and periodicals don't use the same set of tools regularly and so finding |
| 17 | +a common tool/location that works for both groups may not be easy. |
| 18 | +The OpenJS Foundation helps projects get their news to these orgnizations by: |
| 19 | + |
| 20 | +* Providing a [news](https://github.com/openjs-foundation/news) repository |
| 21 | + where project contributors can open issues with news items that would |
| 22 | + be good to be shared in newsletters and periodicals. The expectation |
| 23 | + is the the person who opens the issue will craft the original info |
| 24 | + needed by a newletter or periodical that picks it up and will also |
| 25 | + be available to answer any questions. |
| 26 | +* Providing a mailing list that those who run newsletters and periodicals |
| 27 | + can subscribe to. |
| 28 | +* Periodically upating the list of organizations that are subscribed to |
| 29 | + the mailing list in the repo so that developers know who their news |
| 30 | + items are being sent to. |
| 31 | +* Generating a weekly summary from the issues in news repo and sending |
| 32 | + the summary to the mailing list. |
| 33 | +* Reviewing the most active newsletters and periodical's in the |
| 34 | + JavaScript ecosystem on a quarterly basis and reaching out to those |
| 35 | + who are not subscribed to the mailing list or directly to the repo. |
| 36 | + |
| 37 | + |
| 38 | + |
| 39 | + |
| 40 | + |
0 commit comments