Displaying 8 results from an estimated 8 matches for "recrimination".
2018 Nov 30
2
[PATCH RFC 00/15] Zero ****s, hugload of hugs <3
...cuments.
>
> Yeah, definitely sheds light. Why the documents could not be merged
> to single common sense code of conduct?
The fact that we've arrived at essentially an original CoC
reinterpreted to the point where it's effectively a new CoC has been
the source of much debate and recrimination over the last few months
... you can read it in the ksummit-discuss archives, but I really think
we don't want to reopen that can of worms.
James
2018 Nov 30
0
[PATCH RFC 00/15] Zero ****s, hugload of hugs <3
...definitely sheds light. Why the documents could not be merged
> > to single common sense code of conduct?
>
> The fact that we've arrived at essentially an original CoC
> reinterpreted to the point where it's effectively a new CoC has been
> the source of much debate and recrimination over the last few months
> ... you can read it in the ksummit-discuss archives, but I really think
> we don't want to reopen that can of worms.
Got you... Well I now read the 2nd amendment now through, and yeah, kind
of way I work/function anyway.
Thank you for the patience...
/Jarkko
2014 Oct 31
0
Paul Albrecht
...ate, as the project no longer benefits from their opinions and
insight. However, one of the few things worse than this loss of
participation is to have a hostile environment where people are afraid
to voice opinions. If we cannot discuss ideas ? even radical ones ?
openly and freely without fear of recrimination, then we are dead as
an open source project.
In the Asterisk Developer Community, we often have disagreements about
technical decisions and the direction of the project. Sometimes those
disagreements are quite passionate. That's a good thing. We are all
only human, and sometimes we all make mi...
2018 Nov 30
5
[PATCH RFC 00/15] Zero ****s, hugload of hugs <3
On Fri, 30 Nov 2018 14:12:19 -0800
Jarkko Sakkinen <jarkko.sakkinen at linux.intel.com> wrote:
> As a maintainer myself (and based on somewhat disturbed feedback from
> other maintainers) I can only make the conclusion that nobody knows what
> the responsibility part here means.
>
> I would interpret, if I read it like at lawyer at least, that even for
> existing code you
2006 Aug 13
10
does rails enforce referential integrity???
Hi,
Is rails supposed to support referential integrity? That is rails
either support to be able to ensure that when a new contact is created
this can only happen if a valid suberb is associated with it, and which
mechanisms of the below are supposed to do this?
(a) using DB foreign key constraints information as a basis?
(b) using the "has_one" line in the model file to enfore?
If
2014 Oct 31
0
asterisk-users Digest, Vol 123, Issue 38
...no longer benefits from their opinions and
> insight. However, one of the few things worse than this loss of
> participation is to have a hostile environment where people are afraid
> to voice opinions. If we cannot discuss ideas ? even radical ones ?
> openly and freely without fear of recrimination, then we are dead as
> an open source project.
>
> In the Asterisk Developer Community, we often have disagreements about
> technical decisions and the direction of the project. Sometimes those
> disagreements are quite passionate. That's a good thing. We are all
> only human,...
2010 Sep 01
2
HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Everyone,
On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their
End of Life and will no longer be supported by the FreeBSD Security Team.
Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD
6.x stable branch, support for the FreeBSD 6.x stable branch will also
cease at the same point. Users of either of
2010 Sep 01
2
HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Everyone,
On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their
End of Life and will no longer be supported by the FreeBSD Security Team.
Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD
6.x stable branch, support for the FreeBSD 6.x stable branch will also
cease at the same point. Users of either of