search for: neurotype

Displaying 5 results from an estimated 5 matches for "neurotype".

2020 Feb 16
6
Code of Conduct Next Steps - Community feedback needed
LLVM Community, The LLVM Code of Conduct has been in draft mode for several years now. In order to finalize the Code of Conduct, there are 3 steps left to complete: Draft an Incident Response Guide. This guide is intended for someone who is considering reporting a potential code of conduct violation. You can view and comment on the proposed guide here (or by email if you prefer):
2019 Oct 05
2
CentOS 8 network-scripts
On Fri, 4 Oct 2019 at 18:11, Japheth Cleaver <cleaver at terabithia.org> wrote: > > On 10/4/2019 8:17 AM, Lamar Owen wrote: > > On 10/4/19 10:40 AM, Valeri Galtsev wrote: > >> My impression is younger generation doesn't value rules that > >> programmers were following 2-3 decades ago. One of which is: > >> > >> Do not make any changes [in
2015 Oct 16
4
[cfe-dev] Buildbot Noise
On 16 October 2015 at 19:10, Robinson, Paul <Paul_Robinson at playstation.sony.com> wrote: > That part is cultural. It is... :) > Which ones are "will never work" and which are "ought to get fixed soon"? In theory, the ones that have bugs associated with it, which is not easy to find unless someone adds a comment with the XFAIL, which not many people do.
2019 Oct 04
4
CentOS 8 network-scripts
On 10/4/19 10:40 AM, Valeri Galtsev wrote: > My impression is younger generation doesn't value rules that > programmers were following 2-3 decades ago. One of which is: > > Do not make any changes [in the program] unless they are absolutely > necessary. > I have in the past agreed with this assessment more than once.? And I _am_ somewhat of an old hand at this, having run
2015 Oct 14
11
RFC: Second draft of an LLVM Community Code of Conduct
Greetings all, First off, thanks to everyone who contributed to the initial discussion thread. Judging by the responses from that thread, there seems to pretty broad interest in pursuing this. There also seem to be a few concerns. =] I'm including an updated draft based on the feedback, and I'll also try to break down the major points I've seen of discussion. Sorry for the long email,