goatslacker/alt

Underdash with martyjs?

Open

#337 opened on Jun 18, 2015

View on GitHub
 (45 comments) (0 reactions) (0 assignees)JavaScript (337 forks)batch import
enhancementhelp wantedquestion

Repository metrics

Stars
 (3,451 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Opening this ticket to present the thought of merging with martyjs.

I'm thinking marty because both marty and alt have evolved into a state where they share a lot more in common than not so this presents a good opportunity to converge.

Why?

  • Get more contributors on board.
  • Better documentation.
  • More examples.
  • Increase usage of the library.

Why not?

  • Because we might have to make some breaking changes.

This won't be an easy road but we can figure it out.

Thoughts? Concerns?

cc @jdlehman @justjake @spikebrehm

Contributor guide

Research direction
Read the discussion thread and understand the motivations for merging alt with martyjs. Contribute your thoughts on benefits and challenges.
Tech stack
javascript
Domain
frontend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70