Conversation
Documentation build overview
Show files changed (3 files in total): 📝 2 modified | ➕ 1 added | ➖ 0 deleted
|
| {% block announce %} | ||
| <div style="text-align: center;"> | ||
| 🚧 DiracX is still in development and might not yet be suitable for your needs. See the <a href="/roadmap/">roadmap</a> for details. 🚧 | ||
| 🚧 DiracX is actively developed. If you intend to get in touch, see the <a href="developers/">developers</a> page. 🚧 |
There was a problem hiding this comment.
I am not sure this is the message we want to pass. As of today, you can't do anything with diracx alone. I believe the roadmap should still be linked at the top, and the warning stay very explicit until you can at least submit jobs or do something
There was a problem hiding this comment.
What we discussed is that:
- the roadmap should still be present, but its content needs to be revisited: Update the contents of the roadmap #819
- we said to not link the roadmap from the top because it sounded too much a work in progress. Now, it clearly is a work in progress, but we wanted at the same time to emphasize that "it works". DiracX standalone will take a long time.
There was a problem hiding this comment.
we said to not link the roadmap from the top because it sounded too much a work in progress
I don't think that was a consensus in the meeting. I strongly disagree with changing the wording from "work in progress" until we can run jobs at the very least.
There was a problem hiding this comment.
It was not written "work in progress" even before, and I did not remove the 🚧 emoji. I can reword a bit, but I would not link the roadmap there until we have re-written it.
4 participants
closes #797