Dne 25.6.2018 v 20:03 Till Maas napsal(a):
> On Tue, Jun 19, 2018 at 01:18:04PM +0200, Vít Ondruch wrote:
>
>> Although still, the FESCo meeting agenda used to be place, where it was
>> obvious, that something probably happened with the ticket and it needs
>> FESCo (and possibly my) attention. Th
On Tue, Jun 19, 2018 at 01:18:04PM +0200, Vít Ondruch wrote:
> Although still, the FESCo meeting agenda used to be place, where it was
> obvious, that something probably happened with the ticket and it needs
> FESCo (and possibly my) attention. The notification of new issues would
> not replace th
On Tue, Jun 19, 2018 at 2:56 PM Langdon White wrote:
>
>
>
> On Tue, Jun 19, 2018 at 2:42 PM Matthew Miller
> wrote:
>>
>> On Tue, Jun 19, 2018 at 10:57:17AM -0400, Randy Barlow wrote:
>> > I also believe we would be willing to reconsider this policy if it
>> > doesn't work out in practice. We'r
On Tue, Jun 19, 2018 at 2:42 PM Matthew Miller
wrote:
> On Tue, Jun 19, 2018 at 10:57:17AM -0400, Randy Barlow wrote:
> > I also believe we would be willing to reconsider this policy if it
> > doesn't work out in practice. We're really just looking for ways for us
> > to operate more efficiently
On Tue, Jun 19, 2018 at 10:57:17AM -0400, Randy Barlow wrote:
> I also believe we would be willing to reconsider this policy if it
> doesn't work out in practice. We're really just looking for ways for us
> to operate more efficiently here.
For that matter, if a decision is made and it later becom
On 06/18/2018 10:28 PM, Kevin Kofler wrote:
> With the previous policy, any issues for FESCo would be tabled for a meeting
> and announced on this list before the actual meeting. That gave a chance to
> the community to comment on the ticket and/or attend the meeting to join the
> discussion. Th
On Tue, Jun 19, 2018 at 01:18:04PM +0200, Vít Ondruch wrote:
>
>
> Dne 19.6.2018 v 12:37 Josh Boyer napsal(a):
> > On Tue, Jun 19, 2018 at 3:48 AM Vít Ondruch wrote:
> >>
> >>
> >> Dne 19.6.2018 v 04:28 Kevin Kofler napsal(a):
> >>> Stephen Gallagher wrote:
> * Most FESCo votes will be perf
On Tue, Jun 19, 2018 at 12:37 PM, Josh Boyer wrote:
> On Tue, Jun 19, 2018 at 3:48 AM Vít Ondruch wrote:
>>
>>
>>
>> Dne 19.6.2018 v 04:28 Kevin Kofler napsal(a):
>> > Stephen Gallagher wrote:
>> >> * Most FESCo votes will be performed in the tickets. FESCo members will
>> >> have one week[1] fro
Dne 19.6.2018 v 12:37 Josh Boyer napsal(a):
> On Tue, Jun 19, 2018 at 3:48 AM Vít Ondruch wrote:
>>
>>
>> Dne 19.6.2018 v 04:28 Kevin Kofler napsal(a):
>>> Stephen Gallagher wrote:
* Most FESCo votes will be performed in the tickets. FESCo members will
have one week[1] from the creatio
On Tue, Jun 19, 2018 at 3:48 AM Vít Ondruch wrote:
>
>
>
> Dne 19.6.2018 v 04:28 Kevin Kofler napsal(a):
> > Stephen Gallagher wrote:
> >> * Most FESCo votes will be performed in the tickets. FESCo members will
> >> have one week[1] from the creation of the ticket to vote. So long as at
> >> least
Dne 19.6.2018 v 04:28 Kevin Kofler napsal(a):
> Stephen Gallagher wrote:
>> * Most FESCo votes will be performed in the tickets. FESCo members will
>> have one week[1] from the creation of the ticket to vote. So long as at
>> least three members have voted, the majority of votes at the end of tha
Stephen Gallagher wrote:
> * Most FESCo votes will be performed in the tickets. FESCo members will
> have one week[1] from the creation of the ticket to vote. So long as at
> least three members have voted, the majority of votes at the end of that
> week will be counted as the result. If three vote
12 matches
Mail list logo
