[meecast.spec] Fix typos in comments and changelog

[Olf0]

Sorry, was too tired to get this minimal fix right on first try: Please squash-merge.

[vasvlad]

Olf0, can I add your name as maintainer of rpm packaging?

[Olf0]

Sure, that is fine. Side note: Initially I hesitated a bit to say "yes", because I perceive such a public attribution as a duty to really perform at least minimal maintenance, but I am aware that this is primarily my perception. As you already experienced, sometimes I lack time for this task for multiple weeks.

Actually it is more than only the RPM packaging I do care about, contributed to and intend to continue to contribute to. You may call it: Co-maintaining RPM packaging and project infrastructure (CI configuration, SailfishOS:Chum configuration etc.)

---

Much more important is IMO to ensure continuity of MeeCast regardless of the availability of a single person: Any of us may be temporarily (due to private duties, illness etc.) or permanently (e.g. a fatal accident) unable to access this repository (not to mention the political turmoil this world is slipping into further and further, which already has some ugly, divisive effects on the FOSS ecosystem, e.g. barring some long time contributors and subsystem maintainers of Linux to continue their work). The necessity to ensure continuity of MeeCast is exacerbated by the fact that Jolla's "Weather" app (by Foreca) ceased working more than a year ago and was ultimately removed in SailfishOS 4.6.0, hence MeeCast is the only weather forecast app with eventview widget for SailfishOS since then (and always has been the best generic weather forecast app for SailfishOS since MeeCast started supporting SailfishOS).

Consequently I would really appreciate if you invite me to the GitHub-"organisation" Meecast using GitHub's web-frontend: https://github.com/orgs/Meecast/people I already take care of the infrastructure maintenance for the GitHub-organisations sailfishos-chum, sailfishos-patches, storeman-developers and sailfishos-applications, so the main developers can focus on coding (which I cannot for complex C++, QML, Python etc. code; I originally ceased coding in the 1990ties after having acquired some skills in writing C for microcontrollers and shell-scripts for UNIX at university, and before that BASIC and Pascal at high-school in the 1980ties; I obtained a M.sc. degree in electrical engineering, not computer science).

---

P.S.: Loosely related to both topics, collaborating and infrastructure: Please mind that you have full access to MeeCast in the SailfishOS:Chum Testing OBS-repository. Hence, if you created a new MeeCast release at GitHub (and maybe after some testing of the binaries), can you please put the git-tag name of this release into the <revision> parameter field in MeeCast's OBS service file and click on the Save button in the toolbar of the mini-editor. Then switch to MeeCast's "Overview" page there and after MeeCast has been complied successfully for all targets, please use the Submit package button to submit this new release to sailfishos:chum (do leave all other fields empty). Thanks!

Rationale: Currently there is usually a delay of many days between a new MeeCast release being available at OpenRepos and the SailfishOS:Chum community repository, because it takes a while for me to see that you created a new release. Hence IMO it is better, if you publish a new MeeCast release at both community repositories.

[vasvlad]

I've sent to you an invitation to the MeeCast Organization. Please check it. And should I use only your nickname (Olf0) or I can put your real name ( I don't know it) in AUTHORS information. P.S. See file AUTHORS

[Olf0]

I've sent to you an invitation to the MeeCast Organization. Please check it.

Thank you. Done, i.e. I accepted the invitation. Please consider switching my role from "member" to "owner", see this GitHub-page for reasoning (basically the same considerations I denoted in my prior message) and how to do that. Well, this assumes that you trust me sufficiently and that none of the other project owners is still active or willing to salvage the MeeCast project in case something unfortunate happens (all their GitHub accounts seem to be dead).

And should I use only your nickname (Olf0) or I can put your real name ( I don't know it) in AUTHORS information.

For all my programming and SailfishOS-related work, I use simply "olf" as "real name". "Olf0" is my account handle at GitHub and GitLab, because "olf" was already taken. BTW, "I don't know it" is not true, I sent you a reminder by email, but I do want to be solely "olf (Olf0)" for these activities.

P.S. See file AUTHORS

I suggest to simplify and shorten my entry in the AUTHORS file, see PR #73.

P.S.: BTW, how do you prefer the visibility setting of my project membership: "private" (as all others), "public" or "I don't care"? I tend to "public" so others can contact me in case you are not responding, but basically I don't care (I expect GitHub to contact all project owners in case that is necessary).

[vasvlad]

I've sent to you an invitation to the MeeCast Organization. Please check it.

Thank you. Done, i.e. I accepted the invitation. Please consider switching my role from "member" to "owner", see this GitHub-page for reasoning (basically the same considerations I denoted in my prior message) and how to do that. Well, this assumes that you trust me sufficiently and that none of the other project owners is still active or willing to salvage the MeeCast project in case something unfortunate happens (all their GitHub accounts seem to be dead).

Done.

[Olf0]

P.S.: Loosely related to both topics, collaborating and infrastructure: Please mind that you have full access to MeeCast in the SailfishOS:Chum Testing OBS-repository. Hence, if you created a new MeeCast release at GitHub (and maybe after some testing of the binaries), can you please put the git-tag name of this release into the <revision> parameter field in MeeCast's OBS service file and click on the Save button in the toolbar of the mini-editor.

Thank you for doing that for v1.11.8. Though I had the impression, that you missed to:

Then switch to MeeCast's "Overview" page there and after MeeCast has been complied successfully for all targets, please use the Submit package button to submit this new release to sailfishos:chum (do leave all other fields empty). Thanks!

Thus I created build.sailfishos.org/request/show/3556.

You may wonder why I ask you do perform these steps, although I generally try to offload infrastructure work from you:

Rationale: Currently there is usually a delay of many days between a new MeeCast release being available at OpenRepos and the SailfishOS:Chum community repository, because it takes a while for me to see that you created a new release. Hence IMO it is better, if you publish a new MeeCast release at both community repositories.

[vasvlad]

Ok. I forgot do this actions.

[Olf0]

I forgot do this action.

Don't worry, I know it is a hassle to publish new releases for SailfishOS in two places. Unfortunately both, OpenRepos and the SailfishOS:Chum community repository have their merits and drawbacks. Originally there was the expectation that SailfishOS:Chum would supersede OpenRepos, but that did not happen, some developers are using one, some the other and some both. Personally I like SailfishOS:Chum better, because it builds the packages from the source for each SailfishOS target release, but a target for SailfishOS 5.0.0 is still missing which is a regularly occurring drawback after each new SailfishOS release.

BTW, in hindsight most of my advice WRT MeeCast-Eventview at OpenRepos was wrong, only that the original page should be kept at the original URL was valid. I will provide more details and suggestions (hopefully proper ones, that time) when I have time for that.