Please *do* create issues for any purpose

[Edward K. Ream]

In the Markdown Recipe thread we have been discussing Leo issues. Should we try to limit their number? Are open issues a "blight" on Leo?

On the contrary, I think we should regard Leo's issues as a sign of our community's vitality. There is excellent precedent for this attitude. IPython has thousands of issues, including more than 1300 open issues. Python itself has over a million issues. Iirc, GvR stated that issues were the one way of communicating re type checking, and possibly for Python itself.

Github issues are a convenient place to do drafts of documentation. In particular, I am going to do prewriting for the leoAst.py project directly in #1565. I should have seen this before: I enjoy the fonts and other features of Github issues. Somehow it makes writing easier. And I enjoy not having a long list replies. Confining the latest draft to the first (or second) comment of an issue keeps things simple.

Summary

Imo, we all would do well to think of new ways to use more Leo issues.

Using issues as the basis of communication is the standard for several very successful projects. However, I think this leo-editor forum still has a place.

We can easily disabuse people of the notion that issues are synonymous with bugs.

All comments welcome.

Edward

P.S. Imo, issues are superior to Leo's wiki. However, I won't discourage the use of Leo's wiki, at least for now.

EKR