Add DeSci

[gingerheart86]

Hello! Just added the awesome-desci repo on your list.

[https://github.com/DeSciWorldDAO/awesome-desci#readme]

[(De)centralized (Sci)ence is a nascent movement in the web3 space, where scientists are looking for blockchain-based solutions to structural issues we've got in traditional science. We are a community project that aims to be the global hub for the DeSci community. We would be very thankful if you add our list to your repo! ]

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

unicorn

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 2 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List.
  • ✅ Add Swift
  • ✅ Add Software Architecture
  • ❌ Update readme.md
  • ❌ Add Awesome Swift
  • ❌ Add swift
  • ❌ add Swift
  • ❌ Adding Swift
  • ❌ Added Swift
• Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
  • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
  • ✅ - [Framer](…) - Prototyping interactive UI designs.
  • ❌ - [iOS](…) - Resources and tools for iOS development.
  • ❌ - [Framer](…)
  • ❌ - [Framer](…) - prototyping interactive UI designs
• Your entry should be added at the bottom of the appropriate category.
• The title of your entry should be title-cased and the URL to your list should end in #readme.
  • Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
• It's the result of hard work and the best I could possibly produce. If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • The image should link to the project website or any relevant website.
  • The image should be high-DPI. Set it to maximum half the width of the original image.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
  • Must not feature Contributing or Footnotes sections.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. Casing is up to you.
  • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
  • The section should not appear in the Table of Contents.
• All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Doesn't use hard-wrapping.
• Doesn't include a Travis badge.
  You can still use Travis for list linting, but the badge has no value in the readme.
• Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

[Jogai]

Rules 4, 5 & 7 are not followed, which makes me think you didnt read 1 & 3 closely neither...

[gingerheart86]

Hey Jogai I have read. Maybe I didn't understand. Those rules you mention, do they have numbers? What are you referring to?

I'm sorry for the inconvenience. I'm quite new to Github, just learning. Thanks!

[gingerheart86]

I will read again in detail. Sorry about you feeling I'm waisting your time. Far from my intentions. I'm just a marine biologist trying to get into this world. Thanks for the patience!

[Jogai]

Hey, no problem, and welcome to github! Its not that you are wasting my time, I'm just a bystander basically, its the maintainers' time. You can imagine when there are lots of submissions that it takes a lot of time.

[gingerheart86]

Yes! I do. Well, I think I now integrated he requested features. Would you please take a look?

[Jogai]

title in the format Add Name of List

the URL to your list should end in #readme

[gingerheart86]

Hey Jogai.

I corrected most errors from the lint, but I don't know they are still showing, One is related to the badge. I don't understand since I copied the link badge from other listed list. Also, I made the changes you asked for. Would you let me know?

Thank you!

[gingerheart86]

Hey Jogai, All done. I don't understand which is the problem related to the header. Thanks

[tomByrer]

• Has been around for at least 30 days.

FAIL: 1st commit is Nov 18, 2022 not that big yet either IMHO

[gingerheart86]

• Has been around for at least 30 days.

FAIL: 1st commit is Nov 18, 2022 not that big yet either IMHO

Hey, Thanksg for your feedback. It's not that big because the space is very new. But is one of the most expanding spaces in web3, that's why is awesome and it deserves a list.

[gingerheart86]

Hey @ademidun! why the job is still failing?

[gingerheart86]

Hey @Zackaryjacob would you mind review it again? Thanks!

[gingerheart86]

Hey @waleedsadek-panx I corrected the duplicates. The list does have a contents header! why is that error still showing up? Thanks!

[gingerheart86]

@waleedsadek-panx oh! Just corrected those. Now?

[gingerheart86]

Lint OK. I put the list under decentralized systems, I think it's a more appropriate classification.

[gingerheart86]

Done! Thank you :)

It's linting all is good! The only thing left I can see now is changing the commit title from Add Awesome DeSci to Add DeSci and removing the extra line you've added on line 811.

[ademidun]

Lint OK. I put the list under decentralized systems, I think it's a more appropriate classification.

@gingerheart86

I think the previous section you had originally was more appropriate. We have to think about who is more likely to be interested in DeSci and who do we want to attract. People interested in science and health or people interested in decentralized systems?

If a decentralized systems person sees desci but is not interested in science, they won’t get much value.

While a science person would find desci useful even if they’re not interested in decentralization. Because an interest in decentralization is not a prerequisite for finding value in desci, all you need is an interest in better ways to do science.

[gingerheart86]

Hey @ademidun I see your point and it's valid. I do believe on the contrary that is it's through decentralization (not necessarily on chain) that we will get over the pain points of traditional science. I changed it because DeSci as you said is focused on get science better. And Science goes far beyond health and social sciences. Under that classification, you don't take the hard sciences and other natural sciences which are not related to human health into account. Although it's true that most DeSci projects now are from the latter, we are just getting started and the idea is to cover all scientific disciplines.

However I don't see any problem to keep it under the former classification for now.

Lint OK. @I put the list under decentralized systems, I think it's a more appropriate classification.

@gingerheart86

I think the previous section you had originally was more appropriate. We have to think about who is more likely to be interested in DeSci and who do we want to attract. People interested in science and health or people interested in decentralized systems?

If a decentralized systems person sees desci but is not interested in science, they won’t get much value.

While a science person would find desci useful even if they’re not interested in decentralization. Because an interest in decentralization is not a prerequisite for finding value in desci, all you need is an interest in better ways to do science.

[gingerheart86]

Hey @ademidun what should I do then? Is it mandatory to change it back or do you accept the changes?

[gingerheart86]

Thanks @Zackaryjacob! @sindresorhus Would you merge the pull request?

[sindresorhus]

The formatting for the "Scientific papers" is a bit messy. The title should come first. It should be a proper list using - . A short summary of each paper would also be useful.

---

In the "Articles" section, the title should come first.

---

The items in the "Blogs" section need a description.

---

Every Cure For Every Community- The Podcast - VibeBio.

These entries need better description. "VibeBio" says nothing to me.

---

Awesome lists are English. Resources for other languages should be a separate Markdown file.

---

https://github.com/DeSciWorldDAO/awesome-desci#channels

Needs descriptions.

---

The repo and heading of the list does not match the title used in the entry here.

[gingerheart86]

Hey! @sindresorhus

1. The formatting for the "Scientific papers" is a bit messy. The title should come first. It should be a proper list using - . A short summary of each paper would also be useful. Formatting follows usual scientific citation, it wouldn't be ok to list them under the title nor giving a summary of each paper. The list resembles a scientific bibliography
2. In the "Articles" section, the title should come first. Similar to point 1.
3. Awesome lists are English. Resources for other languages should be a separate Markdown file. In reference to other languages, the idea is to provide a broad list of DeSci content, incluiding content in other languages as it's still very scarse. Would we be able to keep them anyway? we would ppl to know these content exists.
4. The repo and heading of the list does not match the title used in the entry here. I changed the title to "Add DeSci" because I was asked to. Does it need to be changed back to "Add Awesome DeSci"?

about the descriptions you are asking...I think I'm not following you. Isn't kind of obvious that under "Blogs" you can see a list of blogs? same with channels.

Thank you so much for your time Kind regards Carolina

[sindresorhus]

Formatting follows usual scientific citation, it wouldn't be ok to list them under the title nor giving a summary of each paper. The list resembles a scientific bibliography

This is not a science paper, it's an Awesome list. It should be user-friendly.

Would we be able to keep them anyway? we would ppl to know these content exists.

No. This is the same for all Awesome lists. You could create a combined secondary page called other-languages.md with content from any other language and link to it from the readme.

[sindresorhus]

about the descriptions you are asking...I think I'm not following you. Isn't kind of obvious that under "Blogs" you can see a list of blogs? same with channels.

Each item in the "blog" section should have a description about what the blog is about.

[sindresorhus]

Closing for lack of activity.