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

GENERAL CONCEPT: feature ratings, rankings and milestones #16

Open
rouson opened this issue Jul 30, 2017 · 7 comments
Open

GENERAL CONCEPT: feature ratings, rankings and milestones #16

rouson opened this issue Jul 30, 2017 · 7 comments

Comments

@rouson
Copy link

rouson commented Jul 30, 2017

As the list of issues grow here, we might consider ways to rank issues for whatever value that adds in informing the committee discussion. There could be labor-saving value in adopting discussion practices that facilitate leveraging GitHub's issue-sorting feature, which can sort issues according to

  • Newest or Oldest
  • Most or least commented
  • Recently or least recently updated
  • Most reactions of each of the following kinds: 👍 👎 😄 🎉 😕 ❤️

I think the reactions would be especially useful if they could be applied to the issue as a whole, but I imagine they won't ultimately be useful insofar as they relate only to individual comments.

It might also be useful to use the GitHub Milestones feature to prepare for events such as the committee meetings. The next meeting will be in October. Possibly issues that seem to be of great interest based on the above criteria could be added to upcoming Milestones as a way to encourage moving the discussion to a mature state in time for consideration at a committee meeting.

Any related feedback or thoughts are welcome. Or this can be deleted if it's considered non-issue. :)

@szaghi
Copy link
Member

szaghi commented Jul 31, 2017

@rouson

Damian, ranking the issues is a good idea, I ❤️ it. Maybe we can firstly rank issues open-thread and subsequently we can also rank our proposal formatted by means of Zaak template.

Cheers

@zbeekman
Copy link
Member

I like the idea of creating a milestone, and using that to curate the most serious proposals that we feel are worth bringing to the committee.

As far as choosing those, that is a pretty tricky process to formalize. I think in general, we should apply the 👍 reaction to register a vote for the proposal itself. Perhaps we could add other formalism, like, after a discussion someone moves to move the issue to the milestone list, and then that needs a second, and then people can vote 👍 for, 👎 against... etc...

@rouson where are the details of the next meeting?

@rouson
Copy link
Author

rouson commented Jul 31, 2017

See j3-fortran.org. The next J3 meeting will be October 16 - 20, 2017, Las Vegas, NV, USA. For anyone who is unaware, J3 is the American subgroup of the WG5 international committee, although some people from outside the US attend J3. Other countries also have subgroups that I think meet less often. J3 plays the primary role in issuing interpretation of the standards and in developing each version of the standard.

@zbeekman
Copy link
Member

Thanks Damian! It would be great to get J3 on github, or to use some more modern approaches.... the 90s called and want's its website back 😛

@rouson
Copy link
Author

rouson commented Jul 31, 2017

Ohh... believe you me, I wish we could make that happen. This is why we need you to start attending J3. There was a major discussion at last year's WG5 meeting after a relatively new committee member suggested putting the standard itself on GitHub. What you're proposing is less controversial than that so there's at least a chance of it.

@zbeekman
Copy link
Member

zbeekman commented Jul 31, 2017 via email

@rouson
Copy link
Author

rouson commented Jul 31, 2017

Hopefully they will pay for your memberships so you don't have to be an alternate. The bigger question is time committment. The committee meets three times annually for a full week each time. I think a member cannot miss more than two consecutive meetings unless the member sends an alternate, but there are already many people lined up to be alternates when necessary, including yours truly, so you can actually miss more than one as long as someone there signs on to be your alternate.

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

No branches or pull requests

3 participants