Marked Defibrillator Challenge (alpha) #1107

joshbruce · 2018-03-02T17:21:14Z

Marked version: 0.3.17

Description

We don't actually know how many users we really have. Our contributors have kinda bailed on us. This should help us gauge interest beyond the core team in keeping marked around. We're getting some feedback (new issue submissions and whatnot), but not a lot of help, which is unsustainable.

We know we have 3,000+ dependents - don't know how many of those are actually active projects.
We know we get about 1M downloads a month - don't know how many sites that equates to, whether they've been updated in the last few years (I built the US Popclock page a few years ago and it is still using a now dead SVG package, Raphael)
We know we have 2000+ forks and no real contributions back to the mainline.

But, we don't know how many individual users we have and how interested they are in marked sticking around.

The plan

Given the possible implications (getting overrun by PRs), a rolling wave approach is proposed:

Start with this PR, once full consent is given from the committers + @intcreator, I will tag a few folks I think might be interested in the badge (and give them a note on why I tagged them). (Might be good if we each submitted a PR as well, you know?)
Committers will then tag folks they think would be interested in the badge and helping out.
We merge to update the README on GitHub (smaller audience than NPM, I think). Leave it there for at least 30 days.
If we still need tests to cover the spec, and we're still driven to keep marked going, we push a release to (NPM) primarily to notify our users (kind of our only real communication channel to them).

Ps. For committers, can y'all please start actually putting all merged PRs in the draft release?? I'm guilty myself, to be fair. I think it will help me (and our users) when publishing releases to know what all went into that release and modify marketing and communication language accordingly without having to step through commit and PR history. (Users also get the opportunity to opt-in to the most esoteric details of the release, if they want to.)

Contributor

Test(s) exist to ensure functionality and minimize regresstion (if no tests added, list tests covering this PR); or,
no tests required for this PR.
If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

Draft GitHub release notes have been updated.
CI is green (no forced merge required).
Merge PR

davisjam · 2018-03-02T17:23:57Z

For committers, can y'all please start actually putting all merged PRs in the draft release?

Could require an update to a "News" file as part of each PR; Travis can check for this.

That's what cpython (implementation of Python) does.

joshbruce · 2018-03-02T17:29:47Z

Could require an update to a "News" file as part of each PR; Travis can check for this.

Sounds interesting. I'm unfamiliar. Create an issue - tag @UziTech?

@davisjam: Did you get the two invites? One to the org and one to the super secret squirrel hideout?

davisjam · 2018-03-02T17:31:56Z

Did you get the two invites?

Yes. My regex paper is due in a week though so I'm laying low.

joshbruce · 2018-03-02T17:32:51Z

Fair. And good luck!

davisjam · 2018-03-02T17:34:31Z

#1108

intcreator · 2018-03-02T19:50:49Z

README.md

+
+In case you haven't noticed, and judging by attendance you haven't&hellip; (Movie. Major League. No? Anyway.)
+
+In case you haven't noticed, after years of [being mostly dead](https://github.com/markedjs/marked/issues/1106) (not to be confused with stable), Marked is trying to come back to life. We're about at the "You just wiggled your finger" stage ([The Princess Bride](https://youtu.be/yokQ0_8__ts). No? Come on!)


I'm not the biggest fan of the conversation fluff. It makes me take the project less seriously.

intcreator · 2018-03-02T19:51:42Z

README.md

+
+There are four of us on the core team and we have one curious contributor helping us make moves (see [AUTHORS](https://github.com/markedjs/marked/blob/master/AUTHORS.md) page).
+
+We've stirred the tanks a bit and, Houston, we have a problem. ([Apollo 13](https://youtu.be/Bti9_deF5gs). No? Where have y'all been!? Seriously, we haven't talked in a while, where have you been? Oh, right, better question, where has the *marked* community been? Again, mostly dead&hellip;)


Still trying to figure out if there's anything important in this README...

intcreator · 2018-03-02T19:55:40Z

I like the idea of inviting people to add simple test cases, but I think the description is a bit noisy. Maybe make it a bit more concise before we commit it. I think it's good for projects to be fun and casual, but this is a bit over the top for me.

So our number one priority is to be 100% CommonMark compliant for 1.0?

joshbruce · 2018-03-02T20:12:20Z

@intcreator: Want to wait for more feedback before responding further. Check out the CommonMark Compliance project and description (or let me know if you can't see it) and related epic (#1109) regarding priority. Think this is more information gathering and getting help from our friends in that endeavor.

styfle · 2018-03-02T20:27:05Z

but I think the description is a bit noisy. Maybe make it a bit more concise before we commit it.

I get the same feeling with a lot of the docs.

joshbruce · 2018-03-02T21:56:41Z

@intcreator and @styfle: Thank you for the feedback. In all honesty, I could be overcompensating.

I'm a pretty big believer in Conway's Law - probably why I focus a lot on the "individuals and interactions" piece of Agile Software Development.

So, let me ask the question - especially, but not limited to @intcreator and @davisjam:

What made you show up in the first place (never saw you in the comments, or not enough to be noticeable at least)?
What made you want to help?

Note: I've read literally hundreds of issues and PRs and have a pretty decent understanding of the history of the community for the project, I think...that's why I don't remember seeing a lot of these names or faces there.

[edit] Also might be why I could be overcompensating with the relaxed or "not so serious" side of things.

joshbruce · 2018-03-02T22:15:54Z

Also, by approving this via review, we are not committing to a merge...only me tagging a bunch of folks as a first wave test case. (Just want to be clear.)

joshbruce · 2018-03-04T14:26:18Z

Maybe this LOTR reference would be more appropriate... https://youtu.be/jDBPmEAheCY - granted, given what the community devolved into...not sure where the marked brand stands right now.

joshbruce · 2018-03-05T13:05:47Z

Closing. Scaling too soon.

intcreator · 2018-03-05T20:32:48Z

I started looking at Marked because I'm using Polymer's <marked-element> to display Markdown on some of my sites (such as my Web Audio API tutorial) and I wanted to fix a certain bug. It looks like that's a long ways away though because I'd have to understand the entire 5 year old implementation first.

Because the cost is so high, I may instead create my own Polymer element that implements the Commonmark.js parser. If it works, then I'll start focusing more on my web audio API project again.

This leads me to a question—is there anything that Marked does that Commonmark.js doesn't?

styfle · 2018-03-05T20:39:43Z

@intcreator Yes. I don't believe commonmark.js supports GitHub Flavored Markdown (GFM)

Initial pass

23a78bb

joshbruce added the proposal label Mar 2, 2018

joshbruce requested review from UziTech, styfle and davisjam March 2, 2018 17:21

Josh Bruce added 4 commits March 2, 2018 12:24

Typo

93b7106

Typo

9a619bf

clarification

739a316

Typo

83711c1

Typos and minor phrasing

ec83908

intcreator reviewed Mar 2, 2018

View reviewed changes

joshbruce closed this Mar 5, 2018

joshbruce deleted the defibrillator-challenge branch March 5, 2018 13:05

ekmixon mentioned this pull request Jul 8, 2022

[Snyk] Security upgrade rollup-plugin-license from 2.3.0 to 2.8.0 ekmixon/marked#100

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Marked Defibrillator Challenge (alpha) #1107

Marked Defibrillator Challenge (alpha) #1107

joshbruce commented Mar 2, 2018 •

edited

Loading

davisjam commented Mar 2, 2018

joshbruce commented Mar 2, 2018 •

edited

Loading

davisjam commented Mar 2, 2018

joshbruce commented Mar 2, 2018

davisjam commented Mar 2, 2018

intcreator Mar 2, 2018

intcreator Mar 2, 2018

intcreator commented Mar 2, 2018

joshbruce commented Mar 2, 2018 •

edited

Loading

styfle commented Mar 2, 2018

joshbruce commented Mar 2, 2018 •

edited

Loading

joshbruce commented Mar 2, 2018

joshbruce commented Mar 4, 2018

joshbruce commented Mar 5, 2018

intcreator commented Mar 5, 2018 •

edited

Loading

styfle commented Mar 5, 2018


		In case you haven't noticed, and judging by attendance you haven't… (Movie. Major League. No? Anyway.)

		In case you haven't noticed, after years of [being mostly dead](https://github.com/markedjs/marked/issues/1106) (not to be confused with stable), Marked is trying to come back to life. We're about at the "You just wiggled your finger" stage ([The Princess Bride](https://youtu.be/yokQ0_8__ts). No? Come on!)


		There are four of us on the core team and we have one curious contributor helping us make moves (see [AUTHORS](https://github.com/markedjs/marked/blob/master/AUTHORS.md) page).

		We've stirred the tanks a bit and, Houston, we have a problem. ([Apollo 13](https://youtu.be/Bti9_deF5gs). No? Where have y'all been!? Seriously, we haven't talked in a while, where have you been? Oh, right, better question, where has the marked community been? Again, mostly dead…)

Marked Defibrillator Challenge (alpha) #1107

Marked Defibrillator Challenge (alpha) #1107

Conversation

joshbruce commented Mar 2, 2018 • edited Loading

Description

The plan

Contributor

Committer

davisjam commented Mar 2, 2018

joshbruce commented Mar 2, 2018 • edited Loading

davisjam commented Mar 2, 2018

joshbruce commented Mar 2, 2018

davisjam commented Mar 2, 2018

intcreator Mar 2, 2018

Choose a reason for hiding this comment

intcreator Mar 2, 2018

Choose a reason for hiding this comment

intcreator commented Mar 2, 2018

joshbruce commented Mar 2, 2018 • edited Loading

styfle commented Mar 2, 2018

joshbruce commented Mar 2, 2018 • edited Loading

joshbruce commented Mar 2, 2018

joshbruce commented Mar 4, 2018

joshbruce commented Mar 5, 2018

intcreator commented Mar 5, 2018 • edited Loading

styfle commented Mar 5, 2018

joshbruce commented Mar 2, 2018 •

edited

Loading

joshbruce commented Mar 2, 2018 •

edited

Loading

joshbruce commented Mar 2, 2018 •

edited

Loading

joshbruce commented Mar 2, 2018 •

edited

Loading

intcreator commented Mar 5, 2018 •

edited

Loading