Define process & guidelines for elk.xwiki.org access and use

Hello! Bringing this subject from the matrix chat to the forum.

I would like to get access to the XWiki Community ELK instance. Currently, my main need is to be able to create visualizations so that I can track how installs evolve in time for some contrib extensions. Or at least be able to copy a link to a custom visualization, since this functionality also seems to be disabled for Guest accounts (copy link for already existing visualizations works). I am not currently sure if links can only be copied only for created visualizations.

As far as I understood from my discussion with Vincent on matrix, there’s currently only one user account on that instance, and it remains to be seen if multiple accounts can be created.

To be able to create visualizations, either of the following approaches would work:

  • get a personal account on the instance
  • get access to the already existing account

The goal of this post is to define the process for granting access to ELK, but also to define the guidelines for using this access.

I confirm that I will comply with the yet-to-be-defined guidelines for ELK use.

Hi @gabrielc

I think we should discuss with the XWiki.org infra team and create several accounts for accountability.

On the question about whom to give access to, I think giving access to committers who need it, is a no brainer. For non-committers, I’d say it should be on a need-basis and each case should be reviewed and decided by the committers probably.

Would that be ok for you?

Thx

(offtopic)
BTW, now that the project has grown over the years, we may want to establish a project’s PMC (Project Management Committee) that is different from the committers (which, today, act as the PMC). The advantage of a PMC would be that it could also include non-committers. Right now, non-committers are probably under-valued vs committers (I’m thinking of other roles like UI/UX, documentation, and more, who are not committers).

If there’s enough interest, I could start a different thread about this.
(/offtopic)