Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reboot awesome ipfs #478

Merged
merged 12 commits into from
Sep 21, 2023
Merged

reboot awesome ipfs #478

merged 12 commits into from
Sep 21, 2023

Conversation

2color
Copy link
Member

@2color 2color commented Sep 14, 2023

What kind of PR is this?

  • Reboot the list while reducing the maintenance overhead
  • Kill zombies (dead links and ancient and unmaintained projects)
  • Use markdown only with no static site
  • Update the workflows to only run against readme.md

Notes

  • datasets and articles have been removed to keep this focused on projects/services
  • Many of the projects here are long inactive and probably not working and take the thunder away from actively maintained awesome stuff — those have been removed. The repo still has the full history for those interested.
  • The workflow to remove broken links has been removed as it won't work with the simple README.md format. This is not a problem because we will still get the results from the awesome_bot in the comments of PRs via danger (example).

@welcome
Copy link

welcome bot commented Sep 14, 2023

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

  • The context for this PR is clear, with relevant discussion, decisions
    and stakeholders linked/mentioned.

  • Your contribution itself is clear (code comments, self-review for the
    rest) and in its best form. Follow the code contribution
    guidelines

    if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

  • A maintainer will triage and assign priority to this PR, commenting on
    any missing things and potentially assigning a reviewer for high
    priority items.

  • The PR gets reviews, discussed and approvals as needed.

  • The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

@bmann
Copy link
Collaborator

bmann commented Sep 14, 2023

Looking good! I think we can create a website again later but that’s a step 2.

can we kill this bot, too?

@meandavejustice
Copy link
Collaborator

Link to line that reports for README edits on pull requests https://github.com/ipfs/awesome-ipfs/blob/master/dangerfile.js#L10

@ipfs ipfs deleted a comment from ipfs-gui-bot Sep 18, 2023
@2color 2color marked this pull request as ready for review September 18, 2023 16:52
Copy link
Member

@SgtPooki SgtPooki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, no approval because CI is still failing.

POLICY.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
- 2015-09-08: [HTTP is obsolete. It's time for the distributed, permanent web](https://ipfs.io/ipfs/QmNhFJjGcMPqpuYfxL62VVB9528NXqDNMFXiqN5bgFYiZ1/its-time-for-the-permanent-web.html)
- [Downloading nodejs versions with nvm/n over IPFS](https://ipfs.io/ipfs/QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/example#/ipfs/QmUx363UFtgiQqkHHsPK3TSDmwoALDo2hrbMWbcxjH2vFc)

## Datasets
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be useful to mention a place where these items can go in the future. IIRC there was a filecoin/ipfs datasets website somewhere

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. I'm unsure where these belong and who's in charge of pinning them.

Do you happen to know?

README.md Outdated Show resolved Hide resolved
@2color
Copy link
Member Author

2color commented Sep 21, 2023

Thanks for the review @SgtPooki. CI is failing because this PR breaks some of the old workflow/danger config. After this PR is merged, it should be sorted.

2color and others added 3 commits September 21, 2023 15:43
@ipfs-gui-bot
Copy link
Collaborator

ipfs-gui-bot commented Sep 21, 2023

Fails
🚫 Please do not edit the README directly. It is generated from the data in the data/ directory.
Messages
📖 Changes were made within the .github folder.

Generated by 🚫 dangerJS against 256ca86

@2color 2color merged commit 04c72a8 into master Sep 21, 2023
@2color 2color deleted the reboot branch September 21, 2023 16:14
@2color 2color mentioned this pull request Sep 26, 2023
11 tasks
@patcon
Copy link

patcon commented Dec 7, 2023

Thanks for doing this cleanup!

I think we can create a website again later but that’s a step 2. -- @bmann

Big +1 from me, as a fan of that website! The flow of how this repo worked (in the past when it was being maintained) was one that I redirected probably 50 ppl to over the years. The prior markdown/yaml/html example was a beauty to behold and I hope it comes back as an example of how great documentation can be :)

I'll go back in history and extract out a template, and I'll be sure to share that here if I get it cleaned up, so that others like me can keeping demonstrating the documentation flow to others 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants