I'm doing something similar with Grafoscopio. I keep a "Dev's notebook"[1] with a Kanban[2] like subtree to organize development. You can get the last version of all documents inside Grafoscopio. So yes, I think that using Leo to organize and document Leo development can be pretty superior to use just plain Github projects.
[1] http://mutabit.com/repos.fossil/grafoscopio/artifact/9bab02aba13b38e4 [2] https://en.wikipedia.org/wiki/Kanban Cheers, Offray On 29/10/17 15:21, Terry Brown wrote: > On Sun, 29 Oct 2017 12:59:17 -0700 (PDT) > "Edward K. Ream" <[email protected]> wrote: > >> Imo, Google's projects pages are poor. There is insufficient >> organization and formatting features. >> >> Instead, let's use Leo's existing issues page for branch notes and >> for project notes. If necessary, we can split existing issues into >> as many sub-issues as necessary. The great advantage of using issues >> for "everything" is that the formatting capabilities are good. >> >> I have added Branch-Notes and Sub-Project labels. > Ok that's hilarious, crossed emails with the same conclusion, at least > for the value of GitHub projects. 8-) > > A sub-project label is a good idea - then this url: > https://github.com/leo-editor/leo-editor/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20-label%3ASub-Project > excludes all of them at once. > > So I think my question's answered? Labeling my issues > > LEP and Sub-Project > > makes them acceptable in the main issue tracker? > > Cheers -Terry > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
