<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Eli and all,<br>
<br>
I agree we can't be voting on a changing document and like that you
linked to a specific commit for the motion. If the motion was still
live, I would suggest that the motion/vote would be approving the
text in that commit and not following the changes in the PR. But, I
think it was right to retract it.<br>
<br>
I would classify the new changes as more cleanup work (adding/fixing
links) than changes to the core policy text. What would the process
be if these changes were proposed after the motion hypothetically
passed? Would they trigger the need for another motion/vote? This
particular file is a little strange to me because it is in the gm3
repo (by necessity of making it more visible to new users and modern
tooling) but where we generally don't have this level of formality
generally reserved for RFCs.<br>
<br>
There are further changes I think we should include in a
CONTRIBUTING.md file, such as going into more detail about how to
write a helpful issue or PR. Also, the process of the author
attesting that they have the right to release the code under the
GeoMoose license is murky at the moment and should probably be made
more concrete. RFC-4 covers committers/maintainers making such a
declaration and being listed in the AUTHORS file, but leaves the
process of determining if outside contributed code is properly
licensed to the individual committers.<br>
<br>
My view is that we have an emergent need to publish an AI/LLM
policy. Given current norms, this needs to live in the code repo if
it is going to be seen by the people/agents that we want to be aware
of it. My goal here isn't getting to a perfect CONTRIBUTING.md file
before we move forward with publishing an AI policy. I am trying to
make the CONTRIBUTING.md file useful its own right (because once it
exists, people will assume it is authoritative) and for it to be
aligned with the existing official policies in the RFCs, docs, and
website. I don't think CONTRIBUTING.md is the proper place to
create policy.<br>
<br>
My current thinking is that we should make the AI/LLM policy section
from the CONTRIBUTING.md file as it is currently in the PR into a
short RFC that applies to the whole GeoMoose project (not just the
gm3 code base) and put that RFC up for a vote. Then assuming the
RFC is approved, the CONTRIBUTING.md file could just state/reference
that AI policy along with the other established policies. And then
because CONTRIBUTING.md is just referencing existing policy (instead
of creating policy), we are free to make it more complete/helpful in
the future without triggering a whole process.<br>
<br>
Also, I noticed that as per RFC-4:<br>
* we need to update the AUTHORS file. Two members of the PSC are
committers but are not currently listed in the AUTHORS file.<br>
* Changes like adding the COGs and GeoParquet support probably
should've been RFCs and not just votes on the PSC list as they seem
like they might qualify as "larger changes".<br>
* or we could change RFC-4 to match how we are operating in
practice. I am happy either way about what rules we want to have in
place, I just think we should be following our own rules.<br>
<br>
Jim<br>
<br>
<div class="moz-cite-prefix">On 8/27/26 3:51 PM, Eli Adam via
geomoose-psc wrote:<br>
</div>
<blockquote type="cite"
cite="mid:PH0PR09MB86357DF4B826BB0ACA42E84BCAAD2@PH0PR09MB8635.namprd09.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Jeff and all,</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
There is no motion to vote on (I retracted it/-1 it). <a
href="https://lists.osgeo.org/pipermail/geomoose-psc/2026-August/001266.html"
moz-do-not-send="true" class="moz-txt-link-freetext">
https://lists.osgeo.org/pipermail/geomoose-psc/2026-August/001266.html</a></div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Pertaining to process, there can't be changes and votes
happening at the same time. People now have an opportunity to
discuss or make more changes
<a href="https://github.com/geomoose/gm3/pull/1016"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/geomoose/gm3/pull/1016</a> .
Once there appears to be stability with the pull request, I will
make a new motion. </div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof"
style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Best regards, Eli</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif"
style="font-size:11pt" color="#000000"><b>From:</b>
geomoose-psc <a class="moz-txt-link-rfc2396E" href="mailto:geomoose-psc-bounces@lists.osgeo.org"><geomoose-psc-bounces@lists.osgeo.org></a> on
behalf of Jeff McKenna via geomoose-psc
<a class="moz-txt-link-rfc2396E" href="mailto:geomoose-psc@lists.osgeo.org"><geomoose-psc@lists.osgeo.org></a><br>
<b>Sent:</b> Thursday, August 27, 2026 12:29 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:geomoose-psc@lists.osgeo.org"><geomoose-psc@lists.osgeo.org></a><br>
<b>Subject:</b> Re: [geomoose-psc] MOTION: adopt guidelines
for contributing to GeoMoose</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span
style="font-size:11pt;">
<div class="PlainText">(I added another change into that
pull request: <br>
<a href="https://github.com/geomoose/gm3/pull/1016"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/geomoose/gm3/pull/1016</a>
)<br>
<br>
+1 jeff<br>
<br>
<br>
<br>
<br>
On 2026-08-27 3:40 p.m., Eli Adam via geomoose-psc wrote:<br>
> Hi all,<br>
> <br>
> We discussed this some at the last PSC. Dan and Jim
have a draft <br>
> completed and it is ready for voting. Here it is for
review, https:// <br>
>
github.com/geomoose/gm3/blob/499fd5bef4817bcb56e2b9b0f62050063212fe6e/
<br>
> CONTRIBUTING.md <<a class="moz-txt-link-freetext" href="https://github.com/geomoose/gm3/">https://github.com/geomoose/gm3/</a>
<br>
>
blob/499fd5bef4817bcb56e2b9b0f62050063212fe6e/CONTRIBUTING.md><br>
> <br>
> Please review and vote (making sure to include the
email list).<br>
> <br>
> I'll start the voting:<br>
> +1 Eli<br>
> <br>
> Best regards, Eli<br>
> <br>
> <br>
> A note on process: I'm making this motion on the
email list and will <br>
> let it run for at least two business days and then
declare a clear <br>
> result. The subject line also makes this very
clearly a MOTION.<br>
> <br>
<br>
<br>
<br>
_______________________________________________<br>
geomoose-psc mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a><br>
</div>
</span></font></div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
geomoose-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a>
</pre>
</blockquote>
<br>
</body>
</html>