eugenp/tutorials

Prefer upstream unless you specifically need an archived legacy snapshot or want to salvage a few custom examples from the fork. For adopters, this fork is too stale and too far behind to be a good default base for current Spring/Java work.

Choose this fork only if the security/OAuth and architecture-specific customization is the point. If you want current Java/Spring tutorial coverage, upstream is the better default.

Prefer this fork only if you want a stable, course-oriented snapshot. If you need current tutorials, newer JDK coverage, or ongoing maintenance, upstream is the better choice.

Choose this fork only if you need the older REST-focused tutorial snapshot and are comfortable owning maintenance. If you want current Spring/Java examples or broad upstream coverage, the upstream repo is the better base.

Prefer upstream unless you explicitly want a frozen 2024 snapshot. This fork adds no apparent capabilities and is far behind upstream, so it is a poor choice for active development or current tutorial work.

Choose this fork only if you want a frozen, course-centered snapshot and do not need current upstream coverage. For general reuse, the upstream repo is substantially more complete and actively maintained.

Choose this fork only if you specifically want an older, frozen tutorial corpus. For anyone adopting a maintained base, upstream is the better fit because it is much more current and has far broader recent coverage.

Choose this fork only if you want a frozen, heavily customized tutorial corpus and are willing to own modernization. If you want current Spring/Java coverage and active maintenance, upstream is the better base.

Prefer upstream for anything current. Choose this fork only if you specifically need the older REST With Spring course snapshot or a frozen 2017-era teaching repo; otherwise the fork is too stale and diverged to be a good adoption target.