[EXTERNAL] Using dates on the X-axis

[Tormod Volden]

Hi Nicolas,

SF access (or someone uploads the package for me there) would be a
step forward. I also have some patches that should go into the git
repository afterwards. If I understand correctly, the main repo is at
kde.org, and there is a github mirror (mostly to get the CI builds).
Actually I wonder if it is manually synced since it is currently a bit
behind. So, I could either
1) get a developer account on kde.org and commit directly. Not sure
how easy it is to get such an account.
2) send you patches (are you familiar with "git am"?)
3) push patches to a fork on github, and you fetch and apply them to
kde.org (are you familiar with multiple git remotes?)

Regards,
Tormod

On Wed, Mar 18, 2020 at 5:32 PM BRISSET, Nicolas
<nicolas.brisset at airbus.com> wrote:
>
> Hi Tormod,
>
> Sorry for the long time without answer, but I first wanted to try a couple of things. In the end, I was not able (yet) to remember my sourceforge password but I'm nicodev and I should be able to do something to grant you access. However, I don't fully understand the automatic builds and in particular the travis part to build for Windows. It seems it is clear(er) to you, so if you think sf access is all you need, I'll try to sort this out for you.
>
> Nicolas
>
> -----Message d'origine-----
> De : Kst [mailto:kst-bounces at kde.org] De la part de Tormod Volden
> Envoyé : dimanche 1 mars 2020 22:53
> À : Kst mailing list <kst at kde.org>
> Objet : Re: [EXTERNAL] Using dates on the X-axis
>
> Hi all,
>
> The travis CI setup for kst on github is meant to generate fresh Windows builds whenever there is a new commit. However, at the moment it is broken, and the latest build is around 13 months old and probably misses later e.g. HDF5 fixes. The build problem is due to outdated 3rdparty (getdata) library packages that are downloaded as part of the build. I sorted this out, generated newer libraries, and by some curious CI setup artifact I am responsible for that last Windows binary. However to fix it properly for the project setup, my (or another updated) package needs to be uploaded to the sourceforge project and some other fixes can be applied to the build scripts. I was in contact with Barth at the time, he was not so familiar with git so my patches were only partly applied by manual regeneration, and my package was not uploaded, although I tried to give precise instructions. I didn't hear from him again, he might have moved on or lost interest or gone missing in action for other reasons.
>
> I would love to help out on this. The easiest is if you trust me access to the sourceforge project. I think either bnetterfield, nicodev, or syntheticpp can grant this access, or they can themselves upload my package, or generate it on their own. I am not at all well versed in kst internals but I know sourceforge and git well, and some build infrastructures.
>
> I fully understand not having time to maintain a project in your spare time. I am myself guilty of badly (or at least way too slowly) maintaining a number of spare-time open-source projects. In the case of kst we are relying on it at work so I can easier justify spending some time on it. I also understand reluctance to letting in other people who doesn't know the project as well as you do yourself, but it would be sad to let the project die out when there are people willing to help.
>
> Best regards,
> Tormod
> The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.