How to specify previous maintainer in the updated copyright?

[chshersh]

We moved our co-log-related packages to a separate organization. So I would like to update maintainership with headroom automatically to something like that:

Copyright : (c) 2018-2020 Kowainik, 2021 Co-Log

However, what I currently see is the following:

• https://github.com/co-log/co-log-core/pull/6/files#diff-55c170b927df2a963aa739d01f068fc8880667f51c955ba54a0d3a900191ccd3R3

Do you know if there's a way to update the copyright in the desired way?

Corresponding PR:

• Prepare 0.3.0.0 release co-log/co-log-core#6

I'm using the following headroom version:

$ headroom --version
headroom, v0.4.2.0 :: https://github.com/vaclavsvejcar/headroom

[vaclavsvejcar]

Hi @chshersh,

so if I got it right, you need to combine the existing Copyright field value detected from source code (if exists) and the new one from .headroom.yaml variables, right? Not sure if there's easy way to do at this moment, maybe using some conditions in Mustache template, but I'll need to check Headroom's code briefly and will get back to you asap with more details.

[chshersh]

Hi @vaclavsvejcar,

Yes, you understood my question correctly 👍🏻

I'm thinking that maybe headroom can give access to the previous copyright so in my .headroom.yaml I can write something like this:

_haskell_module_copyright: "(c) {{_previous_copyright}}, {{ _current_year }} {{ author }}"

[vaclavsvejcar]

Hi @chshersh,

sorry for late reply, I was really busy at work. I think at this moment there's no way how to achieve this in current Headroom, now it only allows you to use the existing Copyright field extracted from the source code file, or new one defined either in template file or the default one in _haskell_module_copyright dynamic template variable. I think it would be cool feature to have, however, at this moment, I'm not exactly sure how to achieve that in some nice, straightforward and non-hacky generic way. It would be probably necessary to add some smart logic that can compare the headers. I'll also try out the approach you proposed and I'll be happy if you have any other ideas how this could be done. Sorry if this blocks you from using Headroom on this particular use case.

[chshersh]

Hi @vaclavsvejcar,

No need to apologise! OSS can be very demanding 😞 Headroom is already improving my workflow by a great deal!

I realized that my suggested solution doesn't really work. I'm afraid that the `{{_previous_copyright}}`` might lead to infinite recursion when applied carelessly. Also, if it's empty (e.g. for new files) then there will this annoying comma after the empty text. Maybe a better solution would be to use list templating capabilities in Mustache or and have something like

{{#authors}}{{.}} {{/authors}}

(maybe also with a combination of some special variable _has_multiple_authors). But smart logic on the headroom side is still required here.

For now, I can just run headroom and edit files manually. It's not a blocker 👍🏻
Thanks for your work on headroom so far! 🔝