Hi all, I started using projects for the tox issues: https://github.com/tox-dev/tox/projects Github projects are simple boards to provide additional views on the issues and organize the flow of issues. It basically turns issues into virtual post its, which then can be priritized and move along the different stages of realization, it has very little overhead and I like that way of getting organized. the first "official" project is to prioritize the open bugs by severity to be grabbed from the top for motivated bug squashers :) - see https://github.com/tox-dev/tox/projects/1 I don't know if it is a good idea for a project like tox, but I will start using this to get my own maintenance/OSS gardening work organized and maybe it is interesting or helpful for other contributors as well. Cheers Oliver
Hi,
I just realized that pushing cards around and reorganizing on the boards
creates notifications every single time (
https://github.com/tox-dev/tox/issues/454)
I apologize for the noise and will try to keep it down, now that I know
that this occurs.
Cheers,
Oliver
On Fri, 10 Mar 2017 at 13:59 Oliver Bestwalter
* Oliver Bestwalter
I just realized that pushing cards around and reorganizing on the boards creates notifications every single time ( https://github.com/tox-dev/tox/issues/454)
Do you think GitHub sends out mails for everything it shows in that log? Because that's not true - only comments trigger mails. Florian -- http://www.the-compiler.org | me@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
Hey Oliveira :)
It has proven useful to me today already to get a better idea about the
bugs we need to squash.
Where it also might be useful is that if not many contributorswonder
through the whole issues before they tackle something, but when I do that
in tox the feeling emerges that there are certain "themes" or "clusters" of
enhancement proposals that would profit from grouping and being consedered
as a unit. We might around 100 enhancement ideas but they all belong to a
much more limited set of themes. This might help deciding the direction the
project should take and lead to better informed PRs as the contributors
who do not have that birds eye view have those patterns visualized for them
in projects. Very fuzzy thoughts yet. Let's se how it develops.
Cheers
Oliver
On Fri, 10 Mar 2017 at 16:06 Florian Bruhin
* Oliver Bestwalter
[2017-03-10 13:07:46 +0000]: I just realized that pushing cards around and reorganizing on the boards creates notifications every single time ( https://github.com/tox-dev/tox/issues/454)
Do you think GitHub sends out mails for everything it shows in that log? Because that's not true - only comments trigger mails.
Florian
-- http://www.the-compiler.org | me@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
Hi Florian,
On Fri, 10 Mar 2017 at 16:06 Florian Bruhin
I just realized that pushing cards around and reorganizing on the boards creates notifications every single time ( https://github.com/tox-dev/tox/issues/454)
Do you think GitHub sends out mails for everything it shows in that log? Because that's not true - only comments trigger mails. No, that would be horrible (and hopefully configurable then) :) What I meant was the visual clutter that piled up in some issues, when I was setting up the board and pushed things around, while making my mind up about the swimlanes. See under this comment for an example: https://github.com/tox-dev/tox/issues/454#issuecomment-284369359 Cheers, Oliver
Hi Walter,
Nice initiative! I was wondering if that feature would be useful for
pytest, but was not sure how to properly use it. I will watch closely how
you use it for tox and see if I can get some ideas. :)
Cheers,
Bruno.
On Fri, Mar 10, 2017 at 11:09 AM Oliver Bestwalter
Hi all,
I started using projects for the tox issues: https://github.com/tox-dev/tox/projects
Github projects are simple boards to provide additional views on the issues and organize the flow of issues. It basically turns issues into virtual post its, which then can be priritized and move along the different stages of realization, it has very little overhead and I like that way of getting organized.
the first "official" project is to prioritize the open bugs by severity to be grabbed from the top for motivated bug squashers :) - see https://github.com/tox-dev/tox/projects/1
I don't know if it is a good idea for a project like tox, but I will start using this to get my own maintenance/OSS gardening work organized and maybe it is interesting or helpful for other contributors as well.
Cheers Oliver _______________________________________________ tox-dev mailing list tox-dev@python.org https://mail.python.org/mm3/mailman3/lists/tox-dev.python.org/
participants (3)
-
Bruno Oliveira
-
Florian Bruhin
-
Oliver Bestwalter