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

The Ports Collection is now git-based #250

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

motminh
Copy link

@motminh motminh commented Apr 23, 2024

Pull requests are accepted at https://github.com/freebsd/freebsd-ports

@yurivict
Copy link
Member

yurivict commented Jun 20, 2024

I don't think that this is an acceptable change.

Let's say I maintain the port x/y, and someone would submit a pull request.
How would I be notified about this PR and other PRs for my ports?
Is there a mechanism of notification?
Is there a mechanism for port committers to merge/reject GitHub PRs?

@bsdimp
Copy link
Member

bsdimp commented Jun 20, 2024

Right now the volume is low enough it can be done manually. But we make no qos on these requests, and don't count it toward timeouts. For the moment, you'd find out by someone looking at things on github. And of course there's a mechanism for rejecting a change: comment on the pull request now and close it if it's bad. Just like you would in Bugzilla...

If you want, please automation join my github working group. That's the right answer long term. It hopes to get automation like this into github.

@@ -1,3 +1,3 @@
FreeBSD does not currently accept pull requests. This is a read-only mirror from SVN.
FreeBSD does accept pull requests.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd make sure that people know of the still experimental nature of prs.

Comment on lines +1 to 3
FreeBSD does accept pull requests.

Please see the [Porter's Handbook](https://docs.freebsd.org/en/books/porters-handbook/) section on [Submitting patches](https://docs.freebsd.org/en/books/porters-handbook/quick-porting/#porting-submitting).
Copy link
Contributor

@concussious concussious Jun 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
FreeBSD does accept pull requests.
Please see the [Porter's Handbook](https://docs.freebsd.org/en/books/porters-handbook/) section on [Submitting patches](https://docs.freebsd.org/en/books/porters-handbook/quick-porting/#porting-submitting).
# FreeBSD Ports Collection Contribution Guidelines
Contributions may be submitted to the FreeBSD Ports Collection via one of three methods:
- Attachments to [Bugzilla tickets](https://bugs.freebsd.org) are preferred, as this notifies existing maintainers.
- Code reviews on [Phabricator](https://reviews.freebsd.org/differential) are accepted by some maintainers.
- GitHub Pull Requests are an experimental feature and should expect additional delay.
To learn more about contributing to the FreeBSD Ports Collection, please see the [Porter's Handbook](https://docs.freebsd.org/en/books/porters-handbook/) section on [Submitting patches](https://docs.freebsd.org/en/books/porters-handbook/quick-porting/#porting-submitting).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TIL more about this issue and edited my suggestion above. One thumbs up emoji appeared before today's edit and does not reflect the new suggestion.

@diizzyy
Copy link
Contributor

diizzyy commented Aug 22, 2024

I'd argue that we shouldn't accept PRs at all, no one looks at this regulary (that commits) and given that it's not covered by Porters Handbook we're just going to suggest people to submit it bugzilla instead anyway.

@concussious
Copy link
Contributor

This is a feature that we have, PR is just updating the doc to reflect that.

All it takes is someone to start, but beloved ports team is currently doing an unprecedented amount of work per person according to the presentation at nycbug. If I'm understanding policy correctly it's a "when" not an "if", and the language I suggested reflects that.

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

Successfully merging this pull request may close these issues.

5 participants