Re: Let's use issues instead of projects

2017-10-30 Thread Edward K. Ream
On Sun, Oct 29, 2017 at 4:13 PM, Terry Brown wrote: I think the direction both Edward and I were leaning was just away from > GitHub Projects and towards GitHub Issues, not to actually use Leo > itself for issue tracking. > ​Yes. Leo is not at present a great tool for collaborative online work.

Re: Let's use issues instead of projects

2017-10-30 Thread Edward K. Ream
On Sun, Oct 29, 2017 at 3:21 PM, Terry Brown wrote: > On Sun, 29 Oct 2017 12:59:17 -0700 (PDT) > "Edward K. Ream" wrote: > 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: > ht

Re: Let's use issues instead of projects

2017-10-29 Thread Offray Vladimir Luna Cárdenas
On 29/10/17 16:13, Terry Brown wrote: > On Sun, 29 Oct 2017 16:06:13 -0500 > Offray Vladimir Luna Cárdenas wrote: > >> 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 docume

Re: Let's use issues instead of projects

2017-10-29 Thread Terry Brown
On Sun, 29 Oct 2017 16:06:13 -0500 Offray Vladimir Luna Cárdenas wrote: > 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

Re: Let's use issues instead of projects

2017-10-29 Thread Offray Vladimir Luna Cárdenas
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 j

Re: Let's use issues instead of projects

2017-10-29 Thread Terry Brown
On Sun, 29 Oct 2017 12:59:17 -0700 (PDT) "Edward K. Ream" 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

Let's use issues instead of projects

2017-10-29 Thread Edward K. Ream
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