-
Notifications
You must be signed in to change notification settings - Fork 143
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
#885: Update README, inform about reviewing #887
Conversation
also: remove gitter-link, add a link with an overview of the PRs that need reviewing
Co-authored-by: Anders Mörtberg <[email protected]>
Co-authored-by: Anders Mörtberg <[email protected]>
Co-authored-by: Anders Mörtberg <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few suggestions! Sometimes someone else than us is the preferred reviewer though, like @aljungstrom or @mzeuner. Maybe we should have an even longer list of reviewers or is it up to the main reviewers to assign reviews to others?
How about including our Github handles together with our names? |
Yes - but I would turn the list into a table then... |
48a02cb
to
4b63c41
Compare
I like it - what do you think: |
I sorted stuff in the README by topic and threw in some headlines. Someone with knowledge of this stuff should look at it: @mortberg |
Everything looks good to me. Will it be possible that people request reviews from me, without me being able to merge PRs? |
Sure, you can review and someone else merges |
@ecavallo What do you want listed as your area of expertise? Most things? |
Most things is fine. |
I guess you mean the same as you area of expertise, which is "Most topics"? |
Putting this back to 'draft' - maybe it is better, if we actually use the 'Assign' field of the PRs. That way it is much easier, to get an overview of unassigned PRs and we could use the convention that whoever is assigned to an PR should take care of finding a reviewer or whatever else there might be to do (so a bit like the editor-role, but it is ok to review something yourself). |
Yeah, I was wondering what the point of assigning PRs was... So should we go for assigning in addition to requesting? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two suggestions
Co-authored-by: Anders Mörtberg <[email protected]>
Is this ready to be merged? |
There was one open question: Should we make use of assigning PRs? But I'll write an issue for that and we discuss it on the next meeting. So, yes, ready to merge. |
Done: #905 |
Merging this now. Thanks for writing it all up! |
algebra for Max and synthetic homotopy/cohomology theory for Axel.
how about including our Github handles with our names?
…On Thu, Aug 11, 2022, 11:07 Felix Cherubini ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In README.md
<#887 (comment)>:
>
* [Evan Cavallo](https://staff.math.su.se/evan.cavallo/)
-[](https://travis-ci.org/agda/cubical)
+* [Andrea Vezzosi](http://saizan.github.io/) (*inactive*)
I added them. Any hints for their topics?
—
Reply to this email directly, view it on GitHub
<#887 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIE27NHPVT23GI7YS2NSYTVYS7DPANCNFSM56HD6XEA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
See #885