On 06/27/18 11:43, Richard Hipp wrote:
On 6/27/18, Andy Goth <andrew.m.g...@gmail.com> wrote:
Would you be okay with me creating feature requests to track my own
Fossil development ideas, or would you prefer I keep them in wiki pages
or somewhere else?
I prefer them on this mailing list for now. What advantage do you
hope to gain from moving feature requests to tickets and/or wiki?
I don't fully know. I'm trying to explore alternatives right now, in
this thread. That's why I started it.
My concern about putting everything in email is I have too much
accumulated to dump all at once, and I wanted a way to not lose track.
Instead my thought was to archive it all somewhere permanent then open
individual items for discussion in the order I want to talk about and
possibly implement them. Then I can later see what I've covered and
what I haven't and choose new topics, time permitting, or reconsider in
light of other developments, all the while keeping track of the thought
process. The discussion would be predominantly on this mailing list,
but it would be indexed and summarized by the ticket tracker.
Others can do the same thing and independently pick from the list of
open feature requests (also bugs, I have those to report as well) to
write/code about even if I haven't written emails about them yet.
Plus, check-ins can reference tickets quite a bit more easily than they
can reference emails, and check-ins show backreferences from tickets but
of course not from emails.
I also thought about (and wrote about) additionally having a wiki page
to group all my ideas and bug reports together, but honestly the ticket
tracker's report capability can already do that.
Returning to the wording of your original question: "moving feature
requests". I do not propose to "move" at all. Discussion would still
continue on this mailing list, same as always, and in the vast majority
of cases it's fine for the first mention of an idea to be in an email.
The ticket tracker (or wiki) wouldn't become the new, preferred place to
talk about ideas, only a means to keep track of the overall collection.
But since I have a big pile of ideas, I can't dump them all at once on
the list, so instead I'd create tickets, marked as enhancement
(sometimes bug), with general descriptions. And there they would sit
idle until someone (me) writes an email about them to the list,
whereupon discussion commences. I'd then add ticket comments linking to
the list archives. Then, should implementation occur, we include ticket
numbers in the initial branch check-ins and the merges to trunk so that
everything be cross referenced.
Thus, the ticket tracker and wiki don't get pressed into forum duty,
since email is already handling that for us. The ticket tracker would
track tickets, with discussion limited to highly technical comments
directly targeted to the implementation. The wiki would hold documents
of the sort that can be versioned independently of the project.
--
Andy Goth | <andrew.m.goth/at/gmail/dot/com>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
