HELP WANTED: we need an appveyor sponsor
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
This a very unusual issue and probably violates our own issue guidelines. But I'm one of the maintainers, so... ;-)
Anyway, Paket has always been a very active project and recently got a lot of pull requests. Together with our big (and therefore slow) integration test suite we hit CI server limits almost all the time.
This has become a real issue for paket's development speed and so we're here begging our user base to sponsor us a real commercial appveyor account. See https://www.appveyor.com/pricing/
Please note: we're not begging for money since we are not a legal entity yet and I would have no idea how handle it. We are asking for a company to buy an account and allow us to use it.
We would probably also share it with related projects like FAKE and we would definitely create a sponsor page on the paket docs to mention the sponsor.
We are not completely sure if appveyor would still give us the one free OSS account, but in order to really help we would need to end up with at least 2 concurrent jobs.
If your company is a happy Paket user and is interested in supporting us then please contact me at sforkmann at gmail or here in this issue so that we can try to discuss details.
Tbh we don't have a concrete plan how this can work out, but we do hope we find a way to get CI speed back to normal.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the AppVeyor pricing and the project's current CI limits, then contact the maintainer to discuss sponsorship details. Done means securing a commercial account with at least two concurrent jobs and confirming that it restores normal CI speed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100