afeld/magickly

Get single-convert into master

Open

#16 opened on Feb 19, 2013

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Ruby (34 forks)github user discovery
featurehelp wanted

Repository metrics

Stars
 (179 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The performance gain in the single-convert branch is huge, but the factory specifications are still too complex. I believe this can be pushed down a layer to wrap Dragonfly, or moved into Dragonfly itself, or maybe it just makes sense to move off Dragonfly.

Contributor guide

Research direction
Compare the 'single convert' branch with master to identify the performance gains. Analyze the factory specifications complexity and evaluate if the logic can be moved into Dragonfly or if a migration off Dragonfly is needed. Consider the impact on the plugin system.
Tech stack
ruby
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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
RubyGitDragonfly
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30