Merge project directory with awesome-ipfs? about ipfs HOT 14 CLOSED

Good point! We're working on revamping project-directory (mostly by just removing it entirely) and putting it into the main README and ipfs/community/contributing.md. If you want a long slog, see #125.

Linking awesome-ipfs in the README here makes sense.

from ipfs.

+1 for linking or including the contents of awesome-ipfs directly within README

Separately proposing (for the same reasons as project-directory.md) consolidation of awesome-ipfs into appropriate repos. We have a lot of repos (with very little content) which requires a lot of context switching and confusion about what goes where.

from ipfs.

I think awesome-ipfs should remain a separate list. It is specifically a thing on its own (the "awesome lists" thing)

I only want to highlight a few here in the main repo. Maybe we could even remove most of the apps from here (except webui, station, and things used for IPFS itself / to build ipfs)

from ipfs.

You could always move awesome-ipfs to the wiki.

from ipfs.

@dali99 i hear generally ipfs discourages wiki as it has less stringent and granular code review + version control process.

I personally think the awesome list should just be merged with the correct repos, but the real priority is the main readme is fresh.

from ipfs.

@mekarpeles I thought wiki's were git repos themselves, like https://github.com/ipfs/ipfs.wiki.git I don't think it's as easy to see changes online on these, but git history should let you see the entire commit log.

from ipfs.

@dali99 I believe it's more the code review element (being able to branch, more easily collaboratively edit, etc)

from ipfs.

I agree about not moving to a wiki, for the reasons mentioned above.

I don't think merging the awesome-list completely is a good idea: as Juan stated, it is a separate thing. CF sindresorhus/awesome for more about that. I'm in charge of a few awesome lists, so I know that ecosystem very well; I'd not feel comfortable with it having an awesome-* tag if it didn't match their standards.

I only want to highlight a few here in the main repo. Maybe we could even remove most of the apps from here (except webui, station, and things used for IPFS itself / to build ipfs)

This sounds right to me.

from ipfs.

I only want to highlight a few here in the main repo. Maybe we could even remove most of the apps from here (except webui, station, and things used for IPFS itself / to build ipfs)

I think this is the best approach. Also we need a link to awesome-ipfs in the README here I guess, we wouldn't want to lose potential users because they didn't find awesome-ipfs 👍

from ipfs.

Agree, having to update 2 lists is hard and confusing.

from ipfs.

Hmm. Maybe I can explain this better: awesome-ipfs should not be comprehensive, by it's definition as an awesome-* list. Awesome-lists should only be for things that are awesome - however, some resources, while cool, may not satisfy, hence why we have project directories elsewhere.

In the meantime since this issue was opened, we've overhauled the project directory - it is now directly in the README, and there is a link to awesome-ipfs: see this commit and line or check out https://github.com/ipfs/ipfs directly.

We could display the awesome list more prominently? I think directly under Project and Community, to highlight cool stuff the community has made.

from ipfs.

@fazo96 How does that look?

from ipfs.

Very nice! Exactly what I was suggesting 👍 Also I really like the new README structure overall!

from ipfs.

Awesome.

from ipfs.