What's the recommended way to start a new calagator project in 2022?

[evolve2k]

Hi folks

I've attempted to setup calagator a few ways:

1. With the latest preview release
2. With the current stable release but specifying Rails 5 as my desired rails.

Both methods generated errors in the installation process (I can list more details if useful).

Can you recommend the best way to get started currently?

I'm a ruby dev helping to strengthen our local sustainability and climate action ecosystem in my home town and calagator looks like a great tool to help bring together all the events in my town, just need to get it set up though!

[SoundRisk]

I tried to implement this a few months ago also and ran into errors upon errors. I feel like many of the dependencies and the base OS this was tested on have been updated but the source code has not. I would love to implement this as well. Can any of the contributors/maintainers help us out?

[evolve2k]

Quick update: So far I've had the most luck getting @ryanwi's rails-6-upgrade branch mostly working.
https://github.com/ryanwi/calagator/tree/rails-6-upgrade

Also I'm looking for anyone interested to get this project back on it's feet.

Starter plan:

• Get a working version of Calagator running (likley on Rails 6 at this stage)
• Get the test suite passing
• Work in another repo (with the hope that the maintainers here might still return)
• Setup a new CI tool
• Update instructions so others can start easily with a working app
• Consider new features after this

I'd be happy to do some pairing over the next month or two. Just shout out if you have any interest.
Maybe we help each other get our respective calendar projects moving!

More context here: #699

Ps. I also randomly ran into a friend of one of the maintainers at a party in Australia. My party friend said they'd chat to the maintainer once they were back in Portland. See how that goes 🤷‍♂️.

[evolve2k]

Update: March 2023

I've now got a stable version of Calagator working.

My theory was that any of a number of destructive or potentially risky commits was the main cause of the current unstable state of the code base.

On my first attempt I hunted around for a working rails 6 branch, and ryanwi's branch (mentioned earlier) was the closest fit. Despite fixing more bugs and attempting to build on ryanwi's work, this turned out to be still unstable with unreliable functionality when I finally did get the app running locally. In short it was still brittle.

My new approach, was to realise that the app running at calegator.com is likely using a stable moment in time, so I set about winding back to an earlier moment.
Specifically I found the commits upgrading to rails 5 then skipped forward through minor commits until I was at a "more risky/destructuve commit" (in my opinion).

I then picked the last commit before the risk increased as my kick off point. I used one of Audrey's commit's from 31 December 2021 as my base, specifically commit 003e2ef. Thanks for all your efforts Audrey! So much work here!!

Building from there once I versionsed a few gems and resolved some minor error reports, I've been able to get everything running.

For anyone following along:
Here is a working rails 5 branch that is stable with specs passing:
https://github.com/demingfactor/calagator/tree/working-rails-5

Im working forward from that branch now towards a Working Rails 6 branch.
My approach has been to git cherry-pick minor commits onto my Stable Working branch, and skip past any I deem risky/destrutive.

This branch is also in a working state, you can follow along here, it's still on Rails 5 at time of writing.
https://github.com/demingfactor/calagator/tree/working-rails-6

[evolve2k]

April 2023 update:

My main branch here now works for making a new calagator project:
https://github.com/demingfactor/calagator

1. Clone down this repo
2. Then follow these steps to build the gem locally and make your own project from that.
   https://github.com/calagator/calagator/pull/731/files

[evolve2k]

March 2024 update:

Back onto calagator! Happy to announce we've now got calalagor running on Rails 6.1 and Ruby 3.0
To date we've attempted to code in a low opinion way and not change much except for applying the rails upgrades and minor project improvements towards being merged back here.

We're pretty clear now that the current maintainers are not looking for contribution to this repo, so coming soon our new team are planning to relaunch the project with a different name. The existing core team have said they are supportive of community forks.

If you have interest in joining in on development on a revived calagator project in 2024 running on the latest rails and ruby, please reach out.

Access the latest here
https://github.com/demingfactor/calagator