Giraffe
Giraffe copied to clipboard
giraffe-fsharp
Project status
Hey, admittedly it's not been under active development for a while and I'm sorry for that. I can see how that is disruptive and I'm open for suggestions and I will consider all options presented to keep this project alive if that is the interest of the community
Personally I'm finding giraffe more enjoyable than bare asp.net core with c# and I want to see it thrive. I would love to participate in further maintenance/development of this project, so Please let me know how I can contribute. Thanks!
@dustinmoris can we start with removing you as the bottleneck for accepting PRs and doing releases? I know i'm a maintainer but we can't merge without 2 approvals and I don't think I can release to nuget.
After that, I can do some of the grunt work about making it easier to merge/release updates.
That being said, I cannot be the full maintainer on this project, I already have enough on my plate with regards to other repositories I maintain, but I'll do the work to getting it ready to hand off.
That would be great! Even if the project would only receive the occasional bug fix, it would at least keep it usable for existing projects in production. I don't have time to maintain it either, but I would be happy to review a PR every now and then. Maybe there's motivation of the Saturn maintainers to chip in as well? (cc @Krzysztof-Cieslak @NinoFloris @baronfel @64J0)
@TheAngryByrd I have sent you an invite to become an Admin and made the admin group capable of pushing to main and releases themselves. I have also started to talk to someone about the longevity prospect of this project and finding some time to work on it. I'll post an update if there is more to say. However if anyone has an interest to help here out and devote some time then please let me know and I can invite you to this repo!
@dustinmoris Thanks! I went ahead and merged a few things. I figured out the release process (documenting it when I'm finished). Looks like we need a new nuget key.
Run dotnet nuget push ./nupkg/*.nupkg --source $NUGET_FEED --skip-duplicate --api-key $NUGET_KEY
Pushing Giraffe.6.1.0-beta001.nupkg to 'https://www.nuget.org/api/v2/package'...
PUT https://www.nuget.org/api/v2/package/
Forbidden https://www.nuget.org/api/v2/package/ 591ms
error: Response status code does not indicate success: 403 (The specified API key is invalid, has expired, or does not have permission to access the specified package.).
Can you add me to that set of repos/nuget organization as well? Otherwise we'll have to pester you for new nuget keys every year.
I've updated the NuGet key for now to not block anything and will look into how to add mroe people to the Nuget repo a little later today.
Hi, It's a really nice project! I would like to help somehow too. My main experince is C#. I wrote several pet projects in F#
I could update Giraffe's templates. Upgrade them to .net7 version and update build scripts
ping)
By the way, is there any communication channel to discuss PRs and hole project? Slack channel seems more dead, than alive
@Trigun27 Help would be much appreciated. If you really want to get involved then perhaps you could start by helping out with some PRs and we can take it from there and see how much you want to get involved in the future?
@Trigun27 Help would be much appreciated. If you really want to get involved then perhaps you could start by helping out with some PRs and we can take it from there and see how much you want to get involved in the future?
Should I take already open PRs or something from the issue?
Hey guys, ping. We have some open PRs waiting for review, and AFAIK, @TheAngryByrd lost the permissions to review and merge them. If possible (or necessary), I'd like to become a maintainer here as well, so we would have another person to help.
is this project under active development ?
It is. I'm working on it during my free time along with other maintainers.
I'll close this issue now. Please keep opening new issues, starting new discussions and sending your PRs so we can review your ideas. It could take some time, but eventually we'll take care of it.