"Summary of ..." issue items as wiki pages?

57 views
Skip to first unread message

Matt Wilkie

unread,
Oct 22, 2019, 4:21:27 PM10/22/19
to leo-editor
Issues like "Summary of Info items" gives me a a kind of jarring feeling. They can never be closed if we want them easily found, and, for me anyway, there's a strong ever present subtle tension to fix and close everything possible. Perhaps items like these would be better served as wiki pages? Just wondering out loud. There maybe features of issues that are desirable (like typing `#` and having a list of things to refer to suggested).


-matt

Edward K. Ream

unread,
Oct 23, 2019, 1:18:53 AM10/23/19
to leo-editor
On Tue, Oct 22, 2019 at 3:21 PM Matt Wilkie <map...@gmail.com> wrote:

Issues like "Summary of Info items" gives me a a kind of jarring feeling. They can never be closed if we want them easily found, and, for me anyway, there's a strong ever present subtle tension to fix and close everything possible.

I don't feel any such "tension".  Issues are just tools.  I want to fix bugs, but not all bugs can actually be fixed, and the Can'tFix or Won'tFix labels are useful, regardless of whether they are open or closed.
Perhaps items like these would be better served as wiki pages?


I like the look of the wiki page, but I my work flow depends only on issues, and I want all info items to be accessible via issues.

Another idea would be to copy issues to LeoDocs.leo, and (maybe) from there to Leo's web pages.

Edward

Edward K. Ream

unread,
Oct 24, 2019, 4:07:40 AM10/24/19
to leo-editor
On Wednesday, October 23, 2019 at 12:18:53 AM UTC-5, Edward K. Ream wrote:

On Tue, Oct 22, 2019 at 3:21 PM Matt Wilkie <map...@gmail.com> wrote:

Issues like "Summary of Info items" gives me a a kind of jarring feeling. They can never be closed if we want them easily found, and, for me anyway, there's a strong ever present subtle tension to fix and close everything possible.

I don't feel any such "tension".  Issues are just tools. 

Let me say a few more words. I've been doing a lot of planning lately, so this topic has been on my mind a lot.

Some projects use issues for all communication.  I don't want to go that route.  Imo, the leo-editor forum is useful as a separate channel. Some Leo issues have the "Help" label. They could have been discussed in leo-editor, but it's ok with me that they weren't.

Issues are in no way synonymous with "defects".  The Jupyter project has 1500+ open issues and1700+ closed issues. That's an indication of vitality, not low quality :-)

An ongoing question is whether to close issues with the "Info" label.  I have closed such issues when they get the "OutOfDate" label.  I also removed the "Info" label, but seems like a mistake, so just now I've added the "Info" label back.

Issue #1420 illustrates another use case for closing an issue.  It now has the following labels: Bug, Can'tFix, Help, Info, BuildInfo. It's not "OutOfDate", but imo there isn't much reason for keeping it open.

Summary

Issues and labels cost nothing. They are the "secret" to effective work flow and project management.

I never want to remember anything relating to Leo.  I am happy to make issues even for the smallest items.  Such issues are like electronic post-it notes :-)

Labels are crucial to organizing (and retrieving!) goals, projects and action items.

Edward

Matt Wilkie

unread,
Oct 25, 2019, 12:53:45 PM10/25/19
to leo-editor
Issues and labels cost nothing. They are the "secret" to effective work flow and project management.

After reflection I realize this is really about how many clicks it takes me to get to my preferred issues views. If I rely only on Github's default presentation (click on [Issues] tab) I see too much, it's noisy. Well there's a cure for that: bookmarks of the `label:keyword` and exclude `-label:keyword` I'm after on that day.

Thanks for your comments.

-matt

Edward K. Ream

unread,
Oct 26, 2019, 11:54:32 AM10/26/19
to leo-editor
On Fri, Oct 25, 2019 at 11:53 AM Matt Wilkie <map...@gmail.com> wrote:
Issues and labels cost nothing. They are the "secret" to effective work flow and project management.

After reflection I realize this is really about how many clicks it takes me to get to my preferred issues views. If I rely only on Github's default presentation (click on [Issues] tab) I see too much, it's noisy. Well there's a cure for that: bookmarks of the `label:keyword` and exclude `-label:keyword`

Yes.  I have almost two dozen such bookmarks.

Edward
Reply all
Reply to author
Forward
0 new messages