You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tooling.apache.org by "dave2wave (via GitHub)" <gi...@apache.org> on 2026/10/01 15:28:34 UTC
[I] Discuss email template storage (tooling-trusted-releases)
dave2wave opened a new issue, #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704
Referencing a question in https://github.com/apache/maven-invoker-plugin/pull/780
> is there a chance to get such email templates stored centrally, so ATR project can point at them instead of copy/paste? or perhaps in the .asf.yaml to ATR automation?
We currently have default templates, but we could have either an ATR wide or committee specific choice of templates.
Let's discuss and choose a method to allow PMC's with 10s of projects an easy way to be consistent.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5942233304
> To think how changes in such url (template_path) will be tracked and applied to ATR project? Now change in .asf.yml simply apply on each push.
Well that's an interesting bit. Then we'll need to make that directory path part of the project configuration and use it to get the current templates when the release is started or the phase is started.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-6000547910
@alitheg thanks for fix
When do you have a plan to deploy version with this fix?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5941621694
We already allow reading of DOAP files. We could have a special feature under `policy:` called `template_path: <template_dir_url>` that could point to a directory containing each template file with a standard name. Then asfyaml feature can fill in each missing email template from its corresponding file if the file is missing then a blank will be pushed and the ATR default will be used..
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5941409449
Some of my thinking ...
It can be a complicated task.
We can have groups of project which share the same templates, so we need to store information which template should be used for specific project.
Some of projects can have own template.
Question: where to store templates?
Git repo looks like natural place, we have history, notifications, PRs and so on. But it is next question - should we have a dedicated repository per PMC for templates?
I assume that templates will be change very rarely, so simply have a copy of it in each project in .asf.yml will be the simplest, one disatventure is size of .asf.yml in such cases.
We can think about dedicated files for templates stored in each project, like .atr/vote-template.txt
Even many projects will have the same content it can be easier to update, read files by name in projects.
Todays using AI tools we can simply update such in many repository at once, so I not for complicate such feature in ATR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5941932370
@dave2wave can you point to documentation for `policy: template_path`? Where can be used?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5942176116
To think how changes in such url (template_path) will be tracked and applied to ATR project?
Now change in .asf.yml simply apply on each push.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "alitheg (via GitHub)" <gi...@apache.org>.
alitheg commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5947917722
I think if we pull it from a repo content (as opposed to sync from .asf.yaml which is push rather than pull), we would check on each release/phase start whether the hash has moved since our last check and if so then update it. That way it's *always* what's in the repo (so no need to log refresh date or have manual refresh).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5942106406
> [@dave2wave](https://github.com/dave2wave) can you point to documentation for `policy: template_path`? Where can be used?
It is a proposed solution in response to your questions. By having a URL the templates could be in your main repository or even on your website.
I plan to discuss this with the team tomorrow morning.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "alitheg (via GitHub)" <gi...@apache.org>.
alitheg commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5956623132
Following a call, we think the best approach is that for each type of template (vote, announce, etc) you have a URL setting which you can optionally use *instead of* the template content. The two fields would be mutually exclusive, and we would fetch that URL at the point the template is rendered out for confirmation within ATR. So this would mean every project still has a duplicate of this setting, but it's just the URL, not an entire email.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "alitheg (via GitHub)" <gi...@apache.org>.
alitheg commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-6012625680
Pushing it out now @slawekjaranowski
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "alitheg (via GitHub)" <gi...@apache.org>.
alitheg closed issue #1704: Discuss email template storage
URL: https://github.com/apache/tooling-trusted-releases/issues/1704
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5942261889
We would like require the url to be an `*.apache.org/` or `GitHub.com/apache/` uri
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Discuss email template storage (tooling-trusted-releases)
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #1704:
URL: https://github.com/apache/tooling-trusted-releases/issues/1704#issuecomment-5947077083
we can also show on UI source url with last refreshed and provide a button to refresh on demand
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org