The Eclipse Foundation does not have any formal position with regard to distribution of NPM or use of npmjs, other than the general rules.
You can distribute official project releases via npmjs. However, anything that you call an official release must be developed according to the Eclipse Development Process, needs to have all of its intellectual property approved by the Eclipse IP Team, must go through a release review, etc.
That channel should be for the project only. Please don't mix up your corporate interests with project interests. If it's an official distribution channel for the open source Eclipse project, then it's inappropriate (for example) to include a company-specific email address as a contact; use the project's public channel instead.
You should be sure to provide help/links on the project's "downloads" page so that the community can find the distribution channel.
We leave it to the project team to sort out what user should be used. The project team should take reasonable precautions to ensure that no single individual can dominate the channel or otherwise "go rogue". Sharing ownership is one way to do this.
Note that the channel must conform to the
trademark usage guidelines. Calling the organization "Eclipse N4JS" and providing links back to the official project website should do the trick.
If you want some specific guidance or that we develop some best practices in the area, the usual process is to open a bug for the
Eclipse Architecture Council and start the discussion there.
Note that everything that I've said above applies to services in general. e.g. Twitter accounts.
HTH,
