-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Implement links for participation in the OpenJS Foundation ESP Program #594
Comments
Thanks for putting this together. Some thoughts/questions:
So, my overall feedback is I feel like the proposed treatment is a bit heavy-handed for the intended audience, which is a small subsection of our userbase. I'd like to find a treatment that is findable but also not something most people need to skip over. Do you have some examples from other partners that we could look at to consider alternatives? |
just an update @nzakas, all great comments, I'm working with our designer to produce new screenshots reflecting your feedback. Some detailed replies
In reference still to #3, I realize that I personally missed the most obvious place. How about adding the link there? I'll get a more reasonable modkup from our designer. |
also, re: your question in #1 about the length of time, we recommend at least 6 months, and for a HUGE upgrade that can be difficult and lots of work, then 12 to 18 months. |
I put together a PR with "Version Support" under the versions on the homepage. You can use the deploy preview on the PR to see both it and the version support page I put together: For the banner, keep in mind that we need to support both light and dark mode, so we should either choose a color that works in both cases or pick one color for each. I kind of like option 1, at least for light mode. Option 4 is my second favorite. @eslint/eslint-tsc what do you think? |
I'll make adjustments to both issues later today |
@joeeames what will be the landing page for ESLint support? We can start adding links in various places. |
apologize for the delay. I'm running solo on all the OpenJS projects, so things are a bit behind. I LOVE the PR. Especially the content on the support page. Do you still want to put up a banner about the EOL of v8? If so it seems that color #1 is the best match (that's my favorite, I'm loving grays) For the docs pages (for example: https://deploy-preview-600--new-eslint.netlify.app/docs/latest/) still need a couple items:
Finally (3) we still need to put a short summary on the github README as well. I can mock that up if desired. |
I would like to help on completing the pending items if required. |
@joeeames sounds good. Do you have a specific landing page for ESLint support that we can include? Here's what I think are the next steps:
@amareshsm happy to have you work on this. After all that is done, I think we should do a formal blog announcement about the partnership and formally announce v8 EOL. |
I'm working on the link. I'll have that today. it sounds like that's the only thing needed on my end, am I correct in that? |
Yup. Once we have that, @amareshsm can finish up the remaining tasks. |
sorry it took so long. our guy was out of town and then I was: |
@joeeames no worries. I've updated the link on this PR: #600. Once the CI passes, I can merge it and we can move on to the other tasks. @amareshsm can you please prioritize doing the work for this issue? |
Yes sure. Need help with adding "Version Support" link to the left navigation in the docs? Any suggestions would be appreciated. |
I've updated our tracking issue here: Once we get the EOL banners up, we can close this issue. |
sure. I am working on it. |
Thanks @amareshsm! 🙏 |
All right, we've got the banners on the homepage and on the v8.x docs site, so closing. Thanks @amareshsm! Please follow eslint/eslint#18621 for further updates. |
What problem do you want to solve?
The new ESP program (https://openjsf.org/ecosystem-sustainability-program) allows projects to participate and gain funding for further work. This issue is to provide a discussion forum for the changes required for ESLint to participate in the program. I will make a list of recommended changes, and then once we have final approval, HeroDevs or the ESLint maintainers will produce the PR's to effect the changes.
What do you think is the correct solution?
ESLint Site Change Recommendations
Summary
1. New “Support” Page
—---------------------------------------------------------- start of content
Version Support Status
We support only the latest version of ESLint. Major versions less than 9 are no longer supported.
Still on versions older than 9? Here are your options
Upgrade to the latest version
If possible, the best solution is to upgrade to the supported version of ESLint as this keeps you safe and gives you the best performance and features.
Purchase extended commercial support:
If you cannot migrate, but require a secure version of ESLint, you can obtain commercial security support for your applications to keep them secure.
Stay on the unsupported versions
If your application has no security requirements, then you can stay on one of the unsupported versions of ESLint, but be aware that this comes with multiple risks.
Commercial Support
The following companies offer commercial support services for jQuery.
HeroDevs offers security and compatibility support for EOL versions of ESLint through the OpenJS Ecosystem Sustainability Program and is an approved commercial support vendor. You can find out more about their Never Ending Support options here.
—---------------------------------------------------------- end of content
2. Banner on Home Page
The following banner will be added to the home page with the following changes:
![banner](https://private-user-images.githubusercontent.com/1072285/343630631-a1fb61fe-afc2-47bc-bd03-252b860aa609.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU2NTI4NTIsIm5iZiI6MTcyNTY1MjU1MiwicGF0aCI6Ii8xMDcyMjg1LzM0MzYzMDYzMS1hMWZiNjFmZS1hZmMyLTQ3YmMtYmQwMy0yNTJiODYwYWE2MDkucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDZUMTk1NTUyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MjcwZTY5MzY2NGE4YThiMzY3ZjVmMWM5NmVhMmE2YWE1Njc1MWM0YTk4YjM2N2EzZDZiYWFiOTNiMDc3M2E0ZSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.UYkKatm2Dz9CHJ8TX-u8vbH0JSjBMunB34ytloVNPQ0)
3. New Top Level Nav Item
In the screenshot shown above, a new nav item will be added named “Version Support”
4. Previous Versions item in version dropdown on documentation pages
This link will point at the Version Support Page
![dropdown](https://private-user-images.githubusercontent.com/1072285/343630636-e08ddfa9-5645-4392-adb9-da66bc221c93.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU2NTI4NTIsIm5iZiI6MTcyNTY1MjU1MiwicGF0aCI6Ii8xMDcyMjg1LzM0MzYzMDYzNi1lMDhkZGZhOS01NjQ1LTQzOTItYWRiOS1kYTY2YmMyMjFjOTMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDZUMTk1NTUyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MzcyYjZkZDFiOTI3Zjk0MzE4NjQ3NzRmZDA4NWFlOTU0NDVmZDNkNjZiMzhhM2I0Y2M4YzhhMzlmYTRkOTRiNiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.s9H5shdP8sggjF_UXeu7ieNWorRtChTcEiLj6pGaFrc)
4. Link on documentation left nav
A link will be added to the docs left nav pointing at the Version Support page
![sidenav](https://private-user-images.githubusercontent.com/1072285/343630639-1af1f14f-1e48-4152-8d97-460b0f489267.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU2NTI4NTIsIm5iZiI6MTcyNTY1MjU1MiwicGF0aCI6Ii8xMDcyMjg1LzM0MzYzMDYzOS0xYWYxZjE0Zi0xZTQ4LTQxNTItOGQ5Ny00NjBiMGY0ODkyNjcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDZUMTk1NTUyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MDc4NWFlNzRlZWI2ZDExMjc4M2Q3ZTUyYTIxMGUwMzAyYjQ5MTBmMDllZWNlZDRkNjJjZTU0NmFhODA4NmVlNyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.tzI7FEkfeB7tORekVXQNs_Txz2fTeXQyze67lZRRGOE)
5. Github README changes
The following section will be added to the github README file right before “Code of Conduct”
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: