From: Russell Coker <russell@coker.com.au>
To: refpolicy@oss1.tresys.com, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: [refpolicy] ANN: Reference Policy moved to GitHub
Date: Sun, 15 Jun 2014 00:43:24 +1000 [thread overview]
Message-ID: <2636249.DlHTzmdgM2@xev> (raw)
In-Reply-To: <CAH5b-BVg7Kif9V_8b+TnrQmkMnMpTQnBZz2jvce8=VoSgKF63Q@mail.gmail.com>
On Sat, 14 Jun 2014 09:20:29 Elia Pinto wrote:
> > http://www.cultureoffset.org/
> >
> > Are you sure that GitHub is a good choice?
>
> Every one know GitHub. Also the git book talk about it. No perfect as a
> platform but as project you can Gain more visibility.
The SE Linux project has been active for 14 years. People have given lectures
about it at many (all?) major Linux conferences (I've done OLS, LCA, and Linux
Kongress). Articles have been written about it in many (all?) major Linux
magazines (I've done Linux Journal). It's a default feature in Fedora and
RHEL and available in other distributions as well. Blog posts about it can be
seen on most of the major Linux Planet feeds.
I don't think that we have a lack of visibility.
Judging by names I've seen on these mailing lists and people I've met it seems
obvious to me that the proportion of female developers in the SE Linux project
is significantly lower than what you see in proprietary software development.
I think this is a problem we should try to solve.
Also this isn't just about female developers, when one minority group is
treated badly members of others won't expect to be treated well either.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
WARNING: multiple messages have this Message-ID (diff)
From: russell@coker.com.au (Russell Coker)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] ANN: Reference Policy moved to GitHub
Date: Sun, 15 Jun 2014 00:43:24 +1000 [thread overview]
Message-ID: <2636249.DlHTzmdgM2@xev> (raw)
In-Reply-To: <CAH5b-BVg7Kif9V_8b+TnrQmkMnMpTQnBZz2jvce8=VoSgKF63Q@mail.gmail.com>
On Sat, 14 Jun 2014 09:20:29 Elia Pinto wrote:
> > http://www.cultureoffset.org/
> >
> > Are you sure that GitHub is a good choice?
>
> Every one know GitHub. Also the git book talk about it. No perfect as a
> platform but as project you can Gain more visibility.
The SE Linux project has been active for 14 years. People have given lectures
about it at many (all?) major Linux conferences (I've done OLS, LCA, and Linux
Kongress). Articles have been written about it in many (all?) major Linux
magazines (I've done Linux Journal). It's a default feature in Fedora and
RHEL and available in other distributions as well. Blog posts about it can be
seen on most of the major Linux Planet feeds.
I don't think that we have a lack of visibility.
Judging by names I've seen on these mailing lists and people I've met it seems
obvious to me that the proportion of female developers in the SE Linux project
is significantly lower than what you see in proprietary software development.
I think this is a problem we should try to solve.
Also this isn't just about female developers, when one minority group is
treated badly members of others won't expect to be treated well either.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2014-06-14 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 14:54 ANN: Reference Policy moved to GitHub Christopher J. PeBenito
2014-06-09 14:54 ` [refpolicy] " Christopher J. PeBenito
2014-06-14 1:46 ` Russell Coker
2014-06-14 1:46 ` [refpolicy] " Russell Coker
2014-06-14 7:20 ` Elia Pinto
2014-06-14 7:20 ` Elia Pinto
2014-06-14 14:43 ` Russell Coker [this message]
2014-06-14 14:43 ` Russell Coker
2014-06-26 20:07 ` Luis Ressel
2014-06-27 14:45 ` Christopher J. PeBenito
2014-06-27 17:56 ` Luis Ressel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2636249.DlHTzmdgM2@xev \
--to=russell@coker.com.au \
--cc=refpolicy@oss1.tresys.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.