Request for Additional Links List Maintainers

[markerikson]

Per my post at Redux, Writing, Responsibilities, Burnout, and a Request for Help, trying to keep this list updated on a weekly-ish basis has become too much of a mental weight for me.

I still read a ton of articles anyway, but trying to catalog them every week isn't something I want to deal with at this point.

I've seen many people say that this list has been a huge benefit for them as they try to learn React, so I don't want to just abandon the list completely. I would really appreciate it if some members of the React/Redux community could step up and offer assistance in maintaining the list.

There's two main aspects of maintaining this:

• Evaluating and cataloging links to new articles
• Reviewing older articles and pruning ones that are no longer relevant

If you are interested in assisting with maintaining the list, please comment here, and we can figure out the best way to handle this.

(I've dumped the existing backlog of potential links from my queue over into #98 , if anyone would like to help reviewing and cataloging them.)

Thanks in advance!

[thecog19]

I'd love to help with this, but I'm not super knowledgeable about React/Redux.

[john-d-pelingo]

Hello!

I would love to help as well although these days, I am a little bit busy. It's not a problem though if work is shared. If there are insufficient people then consider me in.

[ImmanuelSegol]

Hi I would love to help out.

[joshhogg]

I'd be happy to hop in. Is it as simple as submitting a PR or is there an organization you use?

[josefbetancourt]

I can help. What is the process, just a PR? I looked at the first link you have in #98, Compound Components. Excellent resources, however not particularly relevant directly to Redux. What would be great is an article that shows how Compound Components can make Redux easier to use. So, should this resource be in the resource links?

[markerikson]

Basically just PRs, yes. If you're interested in helping out over the long term, it would be good if we can come up with a more defined workflow.

In general, my own process was roughly:

• Read lots of articles during the week. Bookmark anything that looked potentially useful using Pocket
• Periodically (mostly on weekends), go through the backlogged queue of bookmarks in Pocket. Pop open several articles. For each article:
  • Evaluate the overall content
  • Determine if it seemed worth including in the list. This step is highly subjective, and I generally based it on things like "how useful is the info?", "what's the quality of the writing?", "how much does this overlap with existing links?", etc.
  • If the article was worth including, then determine what category page and sub-category it belonged to
  • Add a Markdown list entry with the title, URL, and a hand-written 2-3 sentence summary of the content
• Remove all evaluated articles from my Pocket queue.

[markerikson]

As I said in the original issue comment, there's two main aspects to maintaining the list:

• Adding new links
• Weeding out links that are outdated, dead, etc

Adding new links was taking up so much time that I really never did much weeding out and cleanup. I'd say that's actually the higher priority atm - looking through existing links in the list, and clearing out anything that's out of date or dead.

Since I stopped actively maintaining this list, I have done a couple "link dumps". I wrote a Markdown script to take Pocket links that I'd tagged as "linkslist", and spit out a list with the page titles and links. I've run that a couple times and dumped the results into issues like #106 . So, there's a bunch of links I've found that might be worth including, but I haven't done the evaluation and adding steps.

[betaflag]

I think that this process won't scale up with collaborators because everyone would duplicate the most longer step of cataloging and going through all articles...

Maybe we can use a subreddit to share article instead of pocket, upvote (based on the quality criteria above), then somehow automate the process of publishing the result weekly here.

Just a thought :)

[josefbetancourt]

@betaflag I like that idea. Also, each reference could have multiple categories and/or tags.

[betaflag]

More thoughts:

1. Someone share a link in the subreddit (so it's crowdsourced, community driven or curator driven)
2. Community and curators discuss/upvote based on estbalished criteria
3. Articles with > x votes get selected
4. They are catalogued in a system (like this repo or maybe more data oriented)
5. A mailing list sends a weekly email to the community with the top articles

This solution would:

• require a small investment in tech (and I'm offering to help)
• scales to multiple curators (I think many ppl here would be willing to help)
• avoids burn out
• involves the community

[deyan-a]

I'd love helping out if you are still looking for contributors. @betaflag great idea!

[virajkulkarni14]

@markerikson, @betaflag: Any update on the approach we were trying to adopt? I would also like to help :)

[definoob]

Where can I vote for the links? @betaflag