Skip to content
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

A production vs a beta version #495

Open
dartar opened this issue Sep 5, 2018 · 1 comment
Open

A production vs a beta version #495

dartar opened this issue Sep 5, 2018 · 1 comment
Labels
defaults what users see without customization documentation hopefully helpful explanations of how things work outreach Scholia team engaging with others
Milestone

Comments

@dartar
Copy link
Contributor

dartar commented Sep 5, 2018

I find that many experimental features make it to the "official" Scholia instance incrementally and change often, somewhat breaking expectations about what information a user can find in each Scholia panel and in what order.

Shouldn't we have a separate public beta/staging environment where new features can be discussed and reviewed before being integrated into the main instance?

I personally feel many features are not "production ready" and Scholia is mature enough to distinguish a stable vs beta version, have formal feature announcements and releases etc.

@Daniel-Mietchen Daniel-Mietchen added outreach Scholia team engaging with others documentation hopefully helpful explanations of how things work defaults what users see without customization labels Sep 5, 2018
@fnielsen
Copy link
Collaborator

fnielsen commented Sep 6, 2018

We could put up a beta environment. I do not mind being experimental on the official site though. Of course if users gets frustrated about features (missing or new unexpected) then it is a problem. I wonder if users know where to report problems?

I am wondering whether we can point to some problems users have run into? Personally I feel a lot could benefit from moving away from embedded frames (relates e.g. to #301). Another issue is to add reasonator-like information. The response time is more and more going to be an issue. Which panels are relevant to show is also up for question. On each page we shouldn't have too many, - I think, due to the load on the WDQS. Some ways around it is by moving panels to subaspects or make the panels configurable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defaults what users see without customization documentation hopefully helpful explanations of how things work outreach Scholia team engaging with others
Projects
None yet
Development

No branches or pull requests

3 participants