Skip to content
This repository has been archived by the owner. It is now read-only.

Open vs Closed Issues #99

Closed
RichardLitt opened this issue Mar 10, 2016 · 10 comments
Closed

Open vs Closed Issues #99

RichardLitt opened this issue Mar 10, 2016 · 10 comments
Labels

Comments

@RichardLitt
Copy link
Contributor

RichardLitt commented Mar 10, 2016

Currently, we have some closed issues. I don't think this is the right thing to do. All issues should be open, permanently.

I propose we unclose all issues, so it is easier to search. Issues that are 100% answered can be locked.

@RichardLitt
Copy link
Contributor Author

RichardLitt commented Mar 10, 2016

Also, added a meta label.

@ghost
Copy link

ghost commented Apr 5, 2016

Generally agree, but I think we should still close duplicates, just to avoid clutter

@RichardLitt
Copy link
Contributor Author

RichardLitt commented Apr 5, 2016

@daviddias
Copy link

daviddias commented Apr 6, 2016

We should close duplicates and curate the content of the ones we keep.

@hackergrrl
Copy link

hackergrrl commented Apr 6, 2016

I agree with @diasdavid -- remove dupes but maintain a high quality control on the ones that we do leave open. I think promoting organic questions to /proper FAQ questions and answers/ as we go is really important.

@Kubuxu
Copy link

Kubuxu commented Apr 6, 2016

What do you think about deleting, moderating comments that are unclear out of topic for given issue (FAQ question)?

It might be controversial but if we want to keep high standard of the FAQ.

@hackergrrl
Copy link

hackergrrl commented Apr 6, 2016

@Kubuxu: if the question is poorly worded but not deduplicated, we could edit it to be more concise, and still provide a solid answer.

@RichardLitt
Copy link
Contributor Author

RichardLitt commented May 2, 2016

I added an 'answered' label. #112

Now I've gone through and put 'answered' on all of the issues I thought were pretty much done. Curating is really hard; but it is something we'll need to do. Closing duplicates, badly worded questions, and pointing to well-done answers is something I think we should do organically as we go along. At some point, I should write a doc that goes through and makes good answers for questions, too; that will probably be what happens to the FAQ section on the website (still forthcoming).

Anyway, step in the right direction.

@RichardLitt
Copy link
Contributor Author

RichardLitt commented May 2, 2016

I've added a note to the Readme: check it out? Maybe then we can close this issue. #115

@madavieb
Copy link

madavieb commented May 23, 2017

This issue has been moved to https://discuss.ipfs.io/t/open-vs-closed-issues/429.

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

No branches or pull requests

5 participants