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

Reorder columns of source-browser #36

Open
xavivars opened this issue Mar 11, 2018 · 2 comments
Open

Reorder columns of source-browser #36

xavivars opened this issue Mar 11, 2018 · 2 comments
Labels

Comments

@xavivars
Copy link
Member

xavivars commented Mar 11, 2018

I was looking at the source browser, and I think the order of the columns is a bit inconsistent.

On one hand, we have a "right to left" approach for maturity of language paris, with incubator at the rightest position (taking into account only langpairs), and then getting more mature as we move left (trunk <- staging <- nursery <- incubator).

But the inconsistency comes outside the language pairs. At the very left we have "languages", that we could consider "as stable as trunk", which could make sense. But then "apertium-tools" is at the very right. "more unstable than incubator".

So my proposal would be to have tools closer to trunk. But as this could be achieved in different ways, I wanted to start a conversation to see what other people think.

Possible options:

  1. Move apertium-tools to the very left
    • tools -> languages -> trunk -> staging -> nursery -> incubator
  2. Change the order of colums to be left-to-right, so we have
    • incubator -> nursery -> staging -> trunk -> languages -> tools
  3. Replace tools and languages (with maturity going LTR or RTL)
    • I don't think considering "languages" to be "before" incubator is wrong, but this could be controversial, an maybe confusing to other people. In any case, this is how I've always thought about the different stages, and how I would have implemented this.
    • languages -> incubator -> nursery -> staging -> trunk -> tools

Thoughts?

@sushain97
Copy link
Member

sushain97 commented Mar 11, 2018 via email

@ghost
Copy link

ghost commented Nov 16, 2018

I'll have a look at this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants