mojotech/torch

Look into migrating from Scrivener to Flop

Open

#479 opened on Aug 25, 2024

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Elixir (84 forks)batch import
discussionhelp wantedmore info needed

Repository metrics

Stars
 (1,163 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Scrivener/Scrivener_Ecto are in low maintenance mode and no longer being updated/supported.

https://github.com/woylie/flop https://github.com/woylie/flop_phoenix

UPDATE

We have taken over maintenance of Scrivener and Scrivener.Ecto so this should be exploratory. If it makes sense to transition to Flop and keep Scrivener in low maintenance mode, we should look into it. Otherwise, we can/should do some updates on Scrivener and take it out of low maint mode.

Contributor guide

Research direction
Compare Scrivener and Flop features, evaluate migration effort, and decide whether to migrate or update Scrivener.
Tech stack
elixir
Domain
backend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ElixirEctoPhoenix
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40