Publish AI guidelines on make #13

Activity

1. karmatosed

   self-assigned this

   on Jan 23, 2026
2. victorstack-ai commented on Feb 5, 2026

   

   victorstack-ai

   on Feb 5, 2026

   More actions

   Thanks for publishing this v0 guide — it’s clear, practical, and sets a good bar without over-policing. A few suggestions after review:

   • Consider adding a short “quick checklist” at the top (Disclosure, License compatibility, Tests run) to make compliance easy to scan before submitting.
   • The disclosure section could include a second example tailored to Trac patches (ticket comment format) and one for non-code contributions (docs/media), since many contributors won’t be on GitHub.
   • In “Minimal checks,” you already list tests and standards for code; maybe add a one‑liner for documentation/media submissions (e.g., “verify all links/hook names; confirm asset licenses are GPL‑compatible/CC0”) to mirror the code checklist.
   • The “meaningful assistance” threshold is helpful; a tiny table of examples (e.g., “AI drafted outline = disclose” vs “AI renamed variable = optional”) could reduce ambiguity for new contributors.

   Happy to help iterate further if useful.
3. 4thhubbard commented on Feb 18, 2026

   

   4thhubbard

   on Feb 18, 2026

   More actions

   Thanks @karmatosed Now that the handbook is live and has had time for feedback, let's move forward with project wide policy. One that aligns with our existing Code of Conduct and has the following:

   1. Scope definition: where it applies (core, docs, support, GitHub, Make, etc.).
   2. Disclosure expectations. For example, when AI assistance should be noted and when it does not need to be.
   3. An enforcement path.
4. annezazu commented on Apr 21, 2026

   

   annezazu

   on Apr 21, 2026

   More actions

   @karmatosed has there been a chance to move on with a project wide policy?