Community-committee: Should CommComm own the Node.js Foundation website?

[obensource]

A new initiative?

The Foundation website is out of date and broken in places. I'm not sure if there is an active maintainer, but should CommComm formally request to own it and make it our initiative?

Screenshots

Inaccurate count:

Broken images

[keywordnew]

Very much worth discussing. Thank you for raising the issue, Ben! I believe the topic came up during a website redesign meeting/discussion. Ping @nodejs/website-redesign 👆🏽

Some action does need to be taken, and the redesign initiative is a good excuse to sort this out. Ideally, people working with the Foundation have the access and control they need to manage the site. And some parts of it need to stay current without their having to keep track of and update on their end.

Whatever action is recommended, people in the Foundation will need to be involved in the running of it in some capacity. It is their site after all! 🙂

[ladyleet]

@obensource thx for bringing this up and @chowdhurian for chiming in! what do you think the easiest way to file issues for NF website is? should we create a repo so people can submit issues to it so we can address? there has been internal discussion to address these things quicker, and thanks for moving it to the top of mind! // @mrhinkle @annmarietonog

[Tiriel]

As much as I think this is a great idea and I think we should take advantage of the current website redesign initiative, I think the first thing should be to ask who is actually responsible for the Foundation website as of now.

I mean, I don't remember seeing a repo in the org about it, it's currently not in our scope AFAIK, so maybe it's a "corporate" thing of the Foundation. That doesn't mean we can't ask to add it to our scope, but that means it's not something we can decide to do without having first a proper audit.

So for my part, I have a few questions first:

• Who is currently responsible for this website?
• Is it in the GH org scope already?
• Is it even hosted on the nodejs.org website hosting or a different one?
• What would it take for us to take responsibility for this website (simple internal vote, board approval...)?

Maybe someone with greater knowledge of the Foundation and its workings can answer these questions? cc @hackygolucky

[ladyleet]

@Tiriel Yes, agreed that y'all should focus on the site redesign at first and I'll work within the Node Foundation to find a solution to address these problems. Just like any website - we just need to be informed so we can fix immediately.

The issues that @obensource brought up I just raised to get them fixed...

I do believe there may be a few current limitations for the foundation website itself and its maintained by the foundation. Still working internally to find out more info for y'all! Thanks again for raising the issue.

@hackygolucky love any "prior experience" thoughts on this. ;)

[Tiriel]

@ladyleet Don't get me wrong, I don't think we should prioritize one above the other, although that might become an issue too.

I was in fact mostly wondering about the "legal" aspects of the question, which it seems you are already enquiring about. Thanks for your quick answer anyway!

[WaleedAshraf]

It's not in Node.js Foundation on GitHub. I have seen multiple issues, where people create the ticket in nodejs.org site and confuse it with Foundation Website. And then someone tags a person from Foundation to fix the issue.

I'm +1 on moving it to Node.js Foundation on GitHub.

[mrhinkle]

We'll add a clearer way to add the reporting for Node.js Foundation website and the delineation between nodejs.org and foundation.nodejs.org. Its hosted on the on Wordpress for ease of administration and won't be moving to Github. Greg Wallace and Shawn Preissner will be glad to be responsive if there are issues that need to be addressed. We'd be glad to work with anyone who wants to provide feedback and we'll drive to get necessary changes done more quickly if they aren't being addressed. Well talk it over and get back to you to see if our suggestions make sense for everyone.

[obensource]

Thank you @mrhinkle! 🙌

[keywordnew]

To remedy future inaccuracies, it may be helpful to project if we were to create and maintain an up-to-date and limited reference of information. This information should be specific to the numbers and information regularly requested for resources created by the Foundation. It should be limited; to minimize the burden of keeping it updated. 💚

I suggest this as a partial solution to any difficulties sourcing accurate and reliable high-level information about the Node.js project. ✅

[fhemberger]

Slightly off-topic: There's also a plug-in to sync Wordpress themes with GitHub, so at least we could sync the Foundation's website design with the upcoming nodejs.org relaunch: https://github.com/afragen/github-updater

[keywordnew]

@fhemberger so using this WordPress plugin:

• the Foundation's theme could be built to match the website redesign and hosted on Github
• the Foundation would still have full control of content while the design of the website would match the redesign of nodejs.org.

Is my interpretation of this tool's value correct? 😅

[fhemberger]

@chowdhurian Exactly.

[WaleedAshraf]

Any update on this issue?

[bnb]

Communication I've gotten from the Foundation on multiple occasions is that it's a hard no on the community owning this site and that we should ping them if updates are needed. They also have their own managed hosting via the Linux Foundation, and the theme is based off of a standard LF WordPress template.

That said, I wouldn't be surprised if this site was made independent from *.nodejs.org in the near future with the Foundation changes that are happening. I can't say for certain, but it's a possibility. I know that a current Board member owns nodejs.foundation which would be a good home, I think.

[bnb]

I _think_ we should probably close this, though I'm not certain. Perhaps it would be a good topic to discuss in the next CommComm meeting?

[WaleedAshraf]

+1 for discussing in the next meeting. Can we add someone from LF side?

[SarahKConway]

Happy to discuss this with CommComm at the next meeting. Looking forward to seeing the new website work from @amiller-gh. Adding @kbarnard10 - our main marketing contact for the NF & JSF websites.

[amiller-gh]

We discussed this at the tail end of Website Redesign last week. After going through the site IA with @RRomoff we're going to try and find homes for all the content on the Foundation site we'd like to see carry over post-foundation-merge in the new site IA. We'll continue working with @SarahKConway and @kbarnard after drafting a plan for the content we're planning to port over in the second half of the year. I'll open an issue with the site IA notes I took during the walkthrough in @nodejs/website-redesign and we'll continue work over there 🙂 I'll close this ticket once I open the other one with a cross-ref.

[amiller-gh]

Closed in favor of https://github.com/nodejs/website-redesign/issues/134