Mailing List Archive

I think this is a good idea. However, reading the bugwash IRC logs and the
associated tickets is pretty simple and I usually can catch up and get a
good idea of things. Personally, I think only 1% of bugwashed tickets
matter for me. So for me, since my focus is more on the commercial end of
Varnish Software, I dont plan on participating much. But if there is a
issue (with a previously discussed ticket or a ticket I introduced), it
would make sense to have the ability to do a bugwash on it and hash out the
details. So as you said, I, and possible others, would participate in the
evening bugwash? Then I guess the AM bugwash people can read up on our
bugwash and get all the details.

As I said before, I dont plan on regularly participating because reading
over the mornings bugwash is good enough and im usually in 99% agreement.
So maybe during the day, I or you will ping each other and say, lets have
an evening bugwash and talk about tickets X, Y, and Z? Otherwise, if no one
speaks up, just assume there will be no evening bugwash? So its opt in with
a default of it wont be held if no one opts in.

--
Reza Naghibi
Varnish Software

On Sun, Dec 11, 2016 at 8:29 AM, Poul-Henning Kamp <phk@phk.freebsd.dk>
wrote:

> This week is going to be pretty busy for me, and I'll not be able
> to participate in the monday bugwash.
>
> Speaking of bugwashes, I have been pondering how we can make them
> less EU-centric, and starting after X-mas I will try to do a two-shot
> bugwash.
>
> Unless there are better ideas, we will keep the bugwash we already
> have, mondays at 13:00 EU time.
>
> But as an experiment I will also do a bugwash monday evening (EU time)
> to make it possible for other continents to chime in.
>
> Being an experiment, nothing is nailed down yet, and I'm very open
> to suggestions as to what time suits people best ?
>
> --
> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG | TCP/IP since RFC 956
> FreeBSD committer | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>
> _______________________________________________
> varnish-dev mailing list
> varnish-dev@varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
>