Skip to content

Add CONTRIBUTING.md - #420

Open
jmroot wants to merge 1 commit into
macports:masterfrom
jmroot:contributing
Open

Add CONTRIBUTING.md#420
jmroot wants to merge 1 commit into
macports:masterfrom
jmroot:contributing

Conversation

@jmroot

@jmroot jmroot commented Aug 4, 2026

Copy link
Copy Markdown
Member

The first section is mostly codifying things that have always been implicit. The second section adopts what appears to be the emerging de facto standard for tagging AI use.

There's obviously a lot more that could be said, but I've tried to keep it minimal so people are likely to read the whole thing. Please discuss on macports-dev in order to reach a wider audience.

@pmetzger

pmetzger commented Aug 4, 2026

Copy link
Copy Markdown
Member

I like most of this, but I would suggest clarifying that asking your AI to pull something is not the same as having it do it without supervision and is okay, i.e. "okay, now that we've tested this, please push it to our fork and then do a pull request" should be explicitly fine and is not the same as having someone turn on a slop cannon. The problem is having someone mindlessly run an AI against the repo without supervision and inundate us with low quality requests, and it should probably be explained that that is the real underlying problem, that is to say, creating work for human beings rather than saving them work.

I think we should also finally get rid of Trac; it just makes running the project harder by dividing attention and making it less obvious how to do requests. But that is a distinct question. I think the work could now be done in under two days using AI assistance and scripting, for what it's worth, possibly in less than a single day. Everything that Trac provides can be provided by GitHub.

@herbygillot

herbygillot commented Aug 4, 2026

Copy link
Copy Markdown
Member

I think we should also finally get rid of Trac
Everything that Trac provides can be provided by GitHub.

I agree with @pmetzger here. The modern user is much more likely to engage with Github rather than Trac.

Overall, I think the proposed guidelines are reasonable, and make adequate allowances for AI use.

@mascguy mascguy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks great to me!

@neverpanic neverpanic left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good to me as well.

I think we should even remove the references to Trac — it requires login with GitHub anyway, so probably everybody that knows how to create a patch and attach it to a Trac ticket can also open a PR, in which case we shouldn't even advertise the alternative method.

As for getting rid of Trac, I'm not opposed, but it's a discussion we should have on the mailing list.

@pmetzger

pmetzger commented Aug 5, 2026

Copy link
Copy Markdown
Member

+1 on eliminating references to Trac.

Comment thread CONTRIBUTING.md

The preferred method for contributing changes to the MacPorts code bases
is by opening a pull request on GitHub. Alternatively, patches may be
attached to a ticket on our [Trac][1] instance.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Per @neverpanic , it is probably best to remove the Trac references entirely.

Comment thread CONTRIBUTING.md
`Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]`

If contributing via Trac, include this information in the ticket. Please
see the [kernel documentation][2] for more details.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Again, see @neverpanic's comment, we should probably just not mention Trac any longer.

Comment thread CONTRIBUTING.md
your contributions.

Please do not use agents or similar software to open pull requests or
tickets without human supervision.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Add, perhaps, "(Using AI systems to open requests is acceptable if they are closely supervised. Again, you are responsible for your agents' actions.)"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

5 participants