Page MenuHomeFreeBSD

CONTRIBUTING: Explain Routes of Contributing
ClosedPublic

Authored by ziaee on Oct 17 2024, 5:55 PM.
Referenced Files
Unknown Object (File)
Thu, Feb 6, 8:39 PM
Unknown Object (File)
Tue, Feb 4, 1:09 AM
Unknown Object (File)
Mon, Feb 3, 8:31 PM
Unknown Object (File)
Wed, Jan 22, 9:50 PM
Unknown Object (File)
Sat, Jan 11, 12:19 PM
Unknown Object (File)
Jan 6 2025, 12:31 PM
Unknown Object (File)
Jan 6 2025, 7:30 AM
Unknown Object (File)
Jan 5 2025, 11:38 PM

Details

Summary

Attempt to explain the 3 routes the project has for contribution.

This thread is not to debate which of these we want to use, this is to explain the current situation as accurately as possible to newcomers, and I am open to wording suggestions to more accurately describe the current situation. Having it undocumented because we want it to be different negatively impacts the project. Thanks!

Moved from my suggestion on https://github.com/freebsd/freebsd-ports/pull/250, which should be closed if this is acceptable.

If this is acceptable, please git commit --author ="Alexander Ziaee <concussious@runbox.com>" so I can demonstrate my activity. Thanks!

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

ziaee requested review of this revision.Oct 17 2024, 5:55 PM
ziaee created this revision.
ziaee edited the summary of this revision. (Show Details)
This revision is now accepted and ready to land.Fri, Jan 17, 7:27 PM

Approved.

For this change you will want to tag it with:

Reviewed by: fernape
Approved by: fernape (ports)
Approved by: mhorne (mentor)

But I will withhold my 'Reviewed by' since it is outside of my area.

jrm added inline comments.
CONTRIBUTING.md
7

Optional rewording.

Wording and spelling LGTM, with or without jrm's suggestion. I'm not a ports committer either, so I can't speak beyond that.

This revision was automatically updated to reflect the committed changes.

Actually this is incorrect, they NEED to be submitted on bugzilla for timeouts etc to apply

Actually this is incorrect, they NEED to be submitted on bugzilla for timeouts etc to apply

That important information, thanks. I'm not sure how to integrate that with the wording. What are the other things in "etc"?

"Attachments to Bugzilla tickets are preferred, as this notifies existing maintainers. A bugzilla ticket is required for maintainer timeout."

?

Submission to bugzilla is required for any policy defined my Porters Handbook to apply. I've asked this question before without getting any answer but do we have some kind of unified agreement that we're to accept PRs at all from GitHub from portmgr or people involved with ports?

do we have some kind of unified agreement that we're to accept PRs at all from GitHub from portmgr or people involved with ports?

Ports are visible coming in every week via all three channels. As I mentioned in the revision description, I want to fix the issue of no longer accurate documentation in this file. The issue of ports comitters being unhappy about diversity of submission streams is outside my scope as a junior doc committer or the scope of this revision.

What I would like to do, is document it in the most accurate way possible that prevents as many problems as possible. I will make a new revision to note that policy based actions require a bugzilla ticket and tag you and all subscribers.

Submission to bugzilla is required for any policy defined my Porters Handbook to apply. I've asked this question before without getting any answer but do we have some kind of unified agreement that we're to accept PRs at all from GitHub from portmgr or people involved with ports?

We have what we always have in the FreeBSD project: sometimes PRs land via github. Nothing stronger has been officially promulgated at this time. There's no guarantee, but many things do land.

Until there's critical mass for this submission route, you aren't likely to see portmgr make any kind of statement given everything else on their plate. I could be wrong though.