On Thu 07 Aug 2014 12:12:26 PM PDT, Brandon Logan wrote:
It's just my own preference. Others like webex/hangouts because it can
be easier to talk about topics than in IRC, but with this many people
and the latency delays, it can become quite cumbersome. Plus, it makes
it easier for meeting
On 08/07/2014 01:41 PM, Eoghan Glynn wrote:
My point was simply that we don't have direct control over the
This is not correct and I've seen it repeated too often to let it go
uncorrected: we (the OpenStack project as a whole) have a lot of control
over contributors to
On 08/08/2014 02:37 AM, Thierry Carrez wrote:
I agree with Eoghan here. The main goal of an agile/lean system is to
maximize a development team productivity. The main goal of Open source
project management is not to maximize productivity. It’s to maximize
contributions. I wrote about that a
On 08/13/2014 07:33 AM, Ian Wells wrote:
I have no great answer to this, but is there a way - perhaps via team
sponsorship from cores to ensure that the general direction is right,
and cloned repositories for purpose-specific changes, as one example -
that we can get an audience of people to
On 08/12/2014 06:46 PM, Wuhongning wrote:
I couldn't have been at the IRC meeting for the time difference, are
there any conclusion for this topic, or is it still open?
I, the PTL, some core reviewers and many in the GBP team are actively
working on a proposal to send to the list for quick
Thanks for the summary Trevor.
On 08/18/2014 01:25 PM, Trevor Vardeman wrote:
1) Discuss future of Octavia in light of Neutron-incubator project proposal.
a) There are many problems with Neutron-Incubator as currently described
Let's be specific, enumerate the problems and address them,
On 08/19/2014 08:39 AM, Eichberger, German wrote:
Just to be clear: We all think the incubator is a great idea and if
some things are ironed out will be a good way to onboard new projects
to Neutron. What bothers me is the timing. Without warning we were
put in an incubator in the span of like
On 08/19/2014 07:37 AM, Jay Pipes wrote:
All of these projects should be able to live in the Program, in the
openstack/ code namespace, for as long as the project is actively
developed, and let the contributor communities in these competing
projects *naturally* work to do any of the following:
On Wed 20 Aug 2014 11:33:47 AM PDT, Szépe Viktor wrote:
Thank you for your answer.
That workflow seems a huge job for me.
I leave this patch up to you.
thanks for sending this fix. You've stumbled upon one of the known
issues of OpenStack's way to deal with small patches like
On 08/21/2014 10:14 AM, Doug Wiegley wrote:
We made the voice/IRC decision in the very format that favors voice. So
in the interest of putting the discussion to bed, voice your opinions here
in a non-voice way:
I was about to voice (ha!) my opinion there but I stopped because I
don't think we
On 08/21/2014 08:00 AM, thomas.pessi...@orange.com wrote:
Sorry if I am not on the right mailing list. I would like to get some
No problem, this is the correct mailing list as this message is about
discussing the future of an openstack component.
I would like to know if I am a
I think we can't throw Ceilometer and Triple-O in the same discussion:
they're two separate issues IMHO, with different root causes and
therefore different solutions.
On 08/21/2014 06:27 AM, Jay Pipes wrote:
The point I've been making is
that by the TC continuing to bless only the Ceilometer
On 08/25/2014 02:36 PM, Joshua Harlow wrote:
So to see if we can get something useful from this thread.
not on this mailing list. Move it somewhere else: this thread is off
OpenStack-dev mailing list
On Mon 25 Aug 2014 03:38:18 PM CDT, Zane Bitter wrote:
I'd say we've done fairly well, but I would attribute that at least in
part to the fact that we've treated the PTL as effectively the
temporary release management contact more than the guy who will
resolve disputes for us. In other words,
On 08/22/2014 08:19 PM, John Dickinson wrote:
I think Anne makes some excellent points about the pattern being
proposed being unlikely to be commonly implemented across all the
programs (or, at best, very difficult). Let's not try to formalize
another best practice that works many times and
On 08/21/2014 03:12 AM, Ihar Hrachyshka wrote:
I wonder where discussion around the proposal is running. Is it public?
Yes, it's public, and this thread is part of it. Look at the dates of
the wiki: this is a recent proposal (first appearance Aug 11), came out
to address the GBP issue, quickly
On 08/28/2014 03:04 PM, Susanne Balle wrote:
Just for us to learn about the incubator status, here are some of the
info on incubation:
These are not the correct documents
On Fri 29 Aug 2014 12:47:00 PM PDT, Elizabeth K. Joseph wrote:
This list is the new place to request the creation or modification of
your third party account. Note that old requests sent to the
openstack-infra mailing list don't need to be resubmitted, they are
On Fri 29 Aug 2014 03:03:34 PM PDT, James E. Blair wrote:
It's the best way we have right now, until we have time to make it more
self-service. We received one third-party CI request in 2 years, then
we received 88 more in 6 months. Our current process is built around
the old conditions. I
On 08/29/2014 11:17 AM, John Garbutt wrote:
After moving to use ZNC, I find IRC works much better for me now, but
I am still learning really.
There! this sentence has two very important points worth highlighting:
1- when people say IRC they mean IRC + a hack to overcome its limitation
Thanks Daniel for taking the time to write such deep message. Obviously
you have thought about this issue for a long time and your opinion comes
from deep personal understanding. I'm adding tags for neutron and
cinder, as I know they're having similar conversations.
I don't have a strong opinion
This is the wrong email list: we use openstack-dev only to discuss
future development of OpenStack project. Use the General mailing list
or the one for Operators (check http://lists.openstack.org).
Alternatively search for answers (and if you don't find any, ask
The DefCore project is moving forward and needs more and more eyes on
it. The next meetings are on Sept 9 and 10, with the same agenda to
facilitate global access.
I'm sharing the details below. All members of OpenStack ecosystem should
follow this process closely as it is going to define what an
On 09/05/2014 07:07 PM, James Bottomley wrote:
Actually, I don't think this analysis is accurate. Some people are
simply interested in small aspects of a project. It's the scratch your
own itch part of open source. The thing which makes itch scratchers
not lone wolfs is the desire to go the
On 09/09/2014 06:55 AM, James Bottomley wrote:
CLAs are a well known and documented barrier to casual contributions
I'm not convinced about this statement, at all. And since I think it's
secondary to what we're discussing, I'll leave it as is and go on.
I've done both ... I do prefer the patch
On 09/05/2014 12:36 PM, Tim Bell wrote:
How can the average deployer know whether a stackforge is
a. An early prototype which has completed (such as some of the
early LBaaS packages)
b. A project which has lost its initial steam and further
investment is not foreseen
On 09/10/2014 02:27 AM, Sylvain Bauza wrote:
Well, both proposals can be done : we can create subteams and the
Subteam-Approval Gerrit label right know before Kilo, and we could split
the virt repos by later once the interfaces and prereqs are done.
That's what I mean in fact: create sub team
On 09/10/2014 12:56 PM, Monty Taylor wrote:
I reject soundly and fundamentally the idea that Open Source projects
NEED a commercial ecosystem to provide solid quality software.
That's not what I said. I said that assuring the quality of code on a
public repository is not necessarily something
On 09/15/2014 03:56 PM, Sean Dague wrote:
A few of us have decided to pull together a regular (cadence to be
determined) video series taking on deep dives inside of OpenStack,
looking at code, explaining why things work that way, and fielding
questions from anyone interested.
For lack of a
Thank you Daniel, great job.
On 09/17/2014 09:03 AM, Daniel Izquierdo wrote:
* Further work
- Add Juno release information
It's coming :)
- Allow to have projects navigation per release
This is interesting
- Add Askbot data per release
This is really not needed, don't spend
On Fri 19 Sep 2014 09:25:10 AM PDT, Jeremy Stanley wrote:
Here we'll just have to agree to disagree. I think core reviewers
hiding behind an automated process so that they don't have to
confront contributors about stalled/inadequate changes is inherently
less friendly. Clearly you feel that
On 09/24/2014 10:05 AM, Jay Pipes wrote:
Whatever it ends up being, it needs to have some teeth to it. Otherwise,
we're going to end up in the exact same place we're in now, where each
project does something slightly different.
I think getting started and produce some material to discuss
On 12/06/2013 02:19 AM, Jaromir Coufal wrote:
We are growing. At the moment we are 4 core members and others are
coming in. But honestly, contributors are not coming to specific
projects - they go to reach UX community in a sense - OK this is awesome
effort, how can I help? What can I work on?
I wrote a blog post today after noticing again that reporters take the
data published on Activity Board and Stackalytics as true, without
asking questions to the protagonists. The problem is that at the moment
none of the systems we have can guarantee that the data is presenting at
On 12/12/2013 07:49 AM, Ilya Shakhat wrote:
Stackalytics team is happy to announce the release of version 0.4.
Good job Ilya, congratulations on the release. I may not be able to join
the meeting (too early for me) so I leave here some feedback for you.
I like the new punchcards in the
On 12/18/2013 07:01 AM, Dolph Mathews wrote:
Options 2 and 3 sound identical to me, when realistically applied.
Option 3 just makes the common sense aspect mandatory.
Indeed, Option 3 gets my vote. One aspect I'd like to mention regarding
diversity of contributors in any open source project is
On Mon 13 Jan 2014 11:04:01 PM PST, Ashwini Babureddy wrote:
I have added all the configurations mentioned below in the mail but
getting the same error while executing the command
Please move this thread to the General mailing list or the Operators
list or https://ask.openstack.org. Reserve
A few minutes ago we sent the first batch of invites to people who
contributed to any of the official OpenStack programs from 00:00 UTC
on April 4, 2014 (Grizzly release day) until present.
We'll send more invites *after each milestone* from now on and until
feature freeze (March 6th,
we're almost ready to import all questions and asnwers from LP Answers
into Ask OpenStack. You can see the result of the import from Nova on
the staging server http://ask-staging.openstack.org/
There are some formatting issues for the imported questions and I'm
trying to evaluate
On Wed 29 Jan 2014 01:49:04 PM CET, Swapnil Kulkarni wrote:
Getting lauchpad bus in ask.openstack would really help people and
this looks really nice.(just saw some question-answers) I was not able
to search for questions though
Yes, we know, search is disabled on staging.
If you're going to talk about anything related to OpenStack at PyCON
US/Canada this year, please let me know. We're collecting the list of
talks related to the project.
Ask and answer questions on https://ask.openstack.org
On Thu 30 Jan 2014 09:36:56 PM CET, Jarret Raim wrote:
Paul Kehrer and I are talking about the state of crypto in Python. The
talk isn't specifically about OpenStack, but we will be talking about
various OpenStack related issues including the Barbican service.
Thanks Jarret, that's exactly the
we're ready to import the answers from Launchpad into Ask OpenStack. A
script will import all questions, answers, comments (and data abou user
accounts) from LP into Ask, tag them as the project of origin (nova,
swift, etc). You can see the results of the test runs on
On Tue 11 Feb 2014 08:01:48 AM CET, Sergey Lukjanov wrote:
Stefano, is it possible to import savanna's answers@launchpad to ask.o.o?
Yes, indeed. I apologize for not putting you explicitly in the cc list.
The full list of projects we'll work on is on the bug itself:
On 02/17/2014 05:21 PM, Steve Kowalik wrote:
I found it completely non-obvious too, and had to go back and look for
the link. If the promotion code text box was always visible with the
Apply button grayed out when the text box is empty, I think that would help.
Unfortunately the site is
On 03/01/2014 03:30 PM, John Griffith wrote:
I just wanted to send out a quick note on a topic that came up recently.
Unfortunately the folks that I'd like to read this most; don't
participate on the ML typically, but I'd at least like to raise some
Answers. I'll contact the PTLs to edit the
On 01/28/2014 04:38 PM, Stefano Maffulli wrote:
we're almost ready to import all questions and asnwers from LP Answers
into Ask OpenStack. You can see the result of the import from Nova on
the staging server http
-1 to the switch from me.
this question from Sean is of fundamental value:
On 03/03/2014 03:19 PM, Sean Dague wrote:
#1) do we believe OFTC is fundamentally better equipped to resist a
DDOS, or do we just believe they are a smaller target? The ongoing DDOS
on meetup.com the past 2 weeks is a
On the topic of 'always improving our community', here is the
announcement I promised
On 03/03/2014 01:52 PM, Stefano Maffulli wrote:
[...] We'll have a first
edition of this program in Atlanta. Some more details on the wiki
On 03/08/2014 09:34 AM, Sylvain Bauza wrote:
As I only requested for hotel+travel support, I was supposed to use my
ATC badge for the registration, *but* it is clearly explained that the
coupon code is only valid until March 21...
Thanks for bringing it up, indeed I think we can
On 03/17/2014 11:14 AM, Ben Nemec wrote:
First, please don't use all caps in your subject. Second, please do use
tags to indicate which projects your message relates to. In this case,
that appears to be nova.
third (actually, zero: this is the most important part of all)
Don't use the
Hello Kurt, all,
On 03/07/2014 01:56 PM, Kurt Griffiths wrote:
There have been a variety of instances where community members have
expressed their ideas and concerns via email or at a summit, or simply
submitted a patch that perhaps challenges someone’s opinion of The Right
Way to Do It, and
On 03/10/2014 04:10 PM, Edgar Magana wrote:
A have a few arguments why I believe this is not 100% inclusive
I think by 100% inclusive you mean getting the right people for the
problem to solve in the room. I would support that objective. Do you
think there are some key people who would need help
On 03/20/2014 03:50 PM, Jay Lau wrote:
It is better that we can have some diagram workflow just like
Gerrit_Workflow https://wiki.openstack.org/wiki/Gerrit_Workflow to
show the new process.
Indeed, I think it would help.
While I'm here, and for the records, I think that creating a new
On 03/22/2014 03:14 AM, Sean Dague wrote:
Honestly, I largely disagree. This is applying some process where there
clearly wasn't any before.
We have a different perception evidently. I'm assuming you're
exaggerating for the sake of clarity because assuming there was no
process before means that
On 03/24/2014 09:20 AM, Russell Bryant wrote:
Another critical point of clarification ... we are *not* moving out of
blueprints at all. We're still using them for tracking, just as before.
We are *adding* the use of gerrit for reviewing the design.
That changes things, thank you for the
On 03/25/2014 01:30 AM, Russell Bryant wrote:
I really don't see why this is so bad. We're using a tool specifically
designed for reviewing things that is already working *really* well,
right, for code reviews.
not just for code, but also for TC governance documents.
I disagree: that's
the lists for the OpenStack project are hosted on
http://lists.openstack.org. You can see the full roster on that page.
If you need a special list for the users of OpenStack PHP SDK you can
propose a change to the lists manifest on
we've been hearing a lot about the incredible growth of the OpenStack
community but we don't hear much about the incredible amount of pressure
that comes with such growth. One huge problem that growth brings with is
that new comers have not had time to assimilate the culture of
On 03/27/2014 06:25 PM, Anita Kuno wrote:
Back to my point, when newcomers come into an opensource project with no
understanding of what opensource means or how to communicate in an
opensource project, that creates additional learning demand that might
not have been in evidence previously.
Thank you Daniel.
On 10/15/2013 11:07 AM, Daniel Izquierdo wrote:
ps: not sure if it's a good idea to resend this to the general list
without the topic [metrics]
nah, I don't think it's needed.
This is useful
first of all: congratulations to all developers, testers, users,
translators, tech writers for the new release: Havana is out of the gate
with impressive numbers.
Speaking of numbers, a lot of you have noticed mistakes in the reported
numbers, from misspelling of names to
On 10/18/2013 05:33 AM, Sean Dague wrote:
I'm not sure it is well understoond that all members have to join the
foundation. We don't make that a requirement on someone slinging a
I believe we do make it a requirement: you can't sign the CLA if you are
not also a member of the
On 10/20/2013 06:00 AM, Jeremy Stanley wrote:
I know the Foundation's got work underway to improve the affiliate
map from the member database, so it might be possible to have some
sort of automated job which proposes changes to a copyright holders
list in each project by running a query with
On 10/22/2013 06:04 AM, S Sridhar wrote:
But getting following error while posting for review.
sridhar@ubuntu:~/repo/neutron$ git review
remote: Resolving deltas: 100% (4/4)
remote: Processing changes: refs: 1, done
On 10/23/2013 12:03 PM, Adrian Otto wrote:
Along with eBay, RedHat, Ubuntu/Canonical, dotCloud/Docker, Cloudsoft,
and Cumulogic, we at Rackspace are happy to announce we have started
project Solum as an OpenStack Related open source project. Solum is a
community-driven initiative currently in
On 10/23/2013 08:33 AM, Russell Bryant wrote:
At the last Nova meeting we started talking about some updates to the
Nova blueprint process for the Icehouse cycle. I had hoped we could
talk about and finalize this in a Nova design summit session on Nova
Project Structure and Process , but I
as it's now an established tradition of OpenStack Summits, we'll have 30
minutes every day in Hong Kong for people to present their projects in 5
minutes or less. The projects can be about anything, really, from
building furniture to 3D printing to cloudy stuff. People that want to
On 10/28/2013 10:28 AM, Russell Bryant wrote:
2) Setting clearer expectations. Since we have so many blueprints for
Nova, I feel it's very important to accurately set expectations for how
the priority of different projects compare. In the last cycle,
priorities were mainly subjectively set
On Wed 30 Oct 2013 03:29:32 AM PDT, Thierry Carrez wrote:
(1) Rating blueprints low priority doesn't mean they won't make it. It
means we have no idea if they will make it. Maybe the proposer doesn't
have a proven track record of hitting promised deadlines, maybe we don't
have core reviewers
On 10/30/2013 12:08 PM, Adrian Otto wrote:
The Solum team has agreed to use openstack-dev, and has closed its
project-specific mailing list.
Welcome. There is now also a topic on the Dev list: people can subscribe
to receive only messages tagged [Solum] or [solum] in the subject.
On 10/30/2013 03:44 PM, Adrian Otto wrote:
So, that's working. My concern is that the topic is listed as
OpenStack Solum and should be listed as Solum because this
project is not incubated, and should not use the OpenStack brand.
Indeed, it was a copy-paste mistake on my side. Fixed now.
On 10/31/2013 07:05 AM, Kyle Mestery (kmestery) wrote:
If we want to grow the committer base and help people to become
better reviewers, taking the time to show them the ropes is part of
hijacking the thread using Kyle's comment as an excuse.
It's not an 'if' but a 'since':
On 10/31/2013 03:45 PM, Romain Hardouin wrote:
Adding a message for new comers is a good idea.
I am a new Horizon contributor, some of my fixes have been merged
(thanks to Upstream University :-)
Indeed :) Can you share with us briefly what you found interesting in
the sessions of Upstream
On 11/01/2013 05:33 AM, Jaromir Coufal wrote:
I was wondering, since there is a lot of people who cannot attend Design
Sessions, if we can help them to be present at least in some way.
We tried in the past to setup systems to enable remote participation in
a generic way (give a URL per each
On Fri 01 Nov 2013 12:40:44 PM PDT, Jaromir Coufal wrote:
Since I have quite good experience with using these hangouts on air, I
wanted to propose it as a general way how to get our sessions more
accessible. Lot of people are asking how they can get more involved
and I received very positive
On 11/12/2013 01:58 AM, Thierry Carrez wrote:
This proposal raises several questions.
(1) Is it a good idea to allow giving credit to patch sponsors
On one hand, this encourages customers of OpenStack service companies to
fund sending back bugfixes and features upstream.
Does it? I'm
On 11/14/2013 09:03 AM, David Ripton wrote:
I don't think it's worth the bother. openstack-dev would still receive
most of the traffic. Once you add back the traffic from people
cross-posting, posting to the wrong list, yelling at people
cross-posting or posting to the wrong list, etc. I'd
On 11/14/2013 11:46 AM, Clint Byrum wrote:
Now, choose which city will grow faster and produce more innovation.
This is not about welcoming newcomers. It's about teaching newcomers the
tools, habits, culture of an established community that keeps growing.
If questions about usage need to be
On 11/14/2013 11:52 AM, Joe Gordon wrote:
This may be a silly question, but what is the best way to filter out
stackforge and related projects? Should I make a local filter and
whitelist all integrated projects?
Not a silly question at all, quite the opposite. One way to filter
traffic is to
On 11/15/2013 02:06 AM, Thierry Carrez wrote:
Arguments in favor of splitting openstack-dev / stackforge-dev
* People can easily filter out all non-openstack discussions
* Traffic would drop by about 25%
I'm not so convinced about this figure, as others pointed out.
* Removes confusion as to
On 11/19/2013 08:19 AM, Julie Pichon wrote:
I've been thinking about the AskBot UX website  and its lack of
visibility, particularly for new community members.
Indeed, it's one of the drawbacks of splitting groups: information tends
not to flow very well.
I think it would be valuable to
On 11/19/2013 09:33 PM, Boris Pavlovic wrote:
The idea of this proposal is that every OpenStack project should have
story wiki page. It means to publish every week one short message that
contains most interesting updates for the last week, and high level road
map for future week. So reading
On 10/31/2013 11:49 AM, Stefano Maffulli wrote:
Another idea that Tom suggested is to use gerrit automation to send back
to first time committers something in addition to the normal 'your patch
is waiting for review' message. The message could be something like:
Tom sent a patch
On Thu 12 Jun 2014 03:53:35 PM PDT, Morgan Fainberg wrote:
I understand your concerns here, and I totally get what you’re driving
at, but in the packaging world wouldn’t this make sense to call it
python-bash8? Now the binary, I can agree (for reasons outlined)
should probably not be named
we're working on a quarterly report of activities in all our git and
gerrit repositories to understand the dynamics of contributions across
different dimensions. This report will be similar to what Bitergia
produced at release time.
I'd like to discuss more widely the format of how
On 06/13/2014 05:57 AM, Doug Hellmann wrote:
That section of the file used to be organized in to separate lists
for incubated, integrated, and other repositories. We changed it
when we started tracking the incubation and integration dates. So it
seems like just listing them under sahara as
On Fri 13 Jun 2014 10:51:24 AM PDT, Stangel, Dan wrote:
You can also refer to the example of Stackalytics, who have created
their own hierarchy and groupings for metrics reporting:
It's a very neat grouping. It seems
sorry for this. I suspect there is something going on with gerrit which
throws the inappropriate error message (more below).
On 06/17/2014 12:57 AM, Sami J. Mäkinen wrote:
For several weeks now, I just always get an error message included below.
In these cases and in general, don't
[trimming reply-to to OpenStack Development since I don't think that
infra is the right venue to discuss this]
On 06/13/2014 10:08 AM, trinath.soman...@freescale.com wrote:
I have two scenarios to deal with.
 A change takes two months or more to get merged into the master
On 06/17/2014 10:45 AM, Sami J. Mäkinen wrote:
Yay. I really just had to become a new OpenStack Foundation Member.
The error message I got is just not too informative, I could not
help thinking there is something really broken.
Right, unfortunately the error message from gerrit cannot be
On 06/16/2014 12:25 PM, Ilya Shakhat wrote:
Most of groups are created from the official programs
http://programs.yaml.yaml. Every program turns into item in the module
list (colored in violet), for example 'Nova Compute' is a group
containing 'nova', 'python-novaclient' and 'nova-specs'.
Looks like something we can add to Activity reports, if you think it's
At the moment there are fairly simple charts for bugs but querying the
database to find stale bugs and their reviews shouldn't be too hard.
If I understand correctly, you're querying LP to get the bugs in status:
On 07/03/2014 03:34 PM, Sumit Naiksatam wrote:
Is this still the right repo for this:
No. The right repo is:
github is used only as copy for convenience and things may break there.
The contents of this message and any attachments to it are
confidential and may be legally privileged. If you have received this
message in error you should delete it from your system immediately
and advise the sender.
To any recipient of this message within HP, unless otherwise stated,
On 07/07/2014 11:30 PM, Monty Taylor wrote:
Also, CLA's are pointless.
Let's be clear: this is your personal opinion, not that of the OpenStack
project nor of the OpenStack Foundation.
From OpenStack project's perspective, CLAs are not pointless, they're
mandated by bylaws and by years of
On Mon 14 Jul 2014 09:14:38 AM PDT, Dat Tran wrote:
I install openstack icehouse, then install sahara. I create cluster,
This is the wrong list to report problems while using openstack.
use openstack-dev only to discuss the future of OpenStack, even if you
On 07/15/2014 09:02 AM, Dugger, Donald D wrote:
Unfortunately, much as I agree with your sentiment (Death to MS
Outlook) my IT overlords have pretty much forced me into using it.
It's been a while since I had to deal with really awful software but
since the is a common problem, shall we
On 07/23/2014 06:22 AM, Kyle Mestery wrote:
Thanks for sending this out Salvatore. We are way oversubscribed,
and at this point, I'm in agreement on not letting any new
exceptions which do not fall under the above guidelines. Given how
much is already packed in there, this makes the most
In the lead up to the next round of the GNOME Outreach Program for Women
(application deadline 10/22/2014), the group is hosting a series of
meetups around getting involved in free and open source software
Given OpenStack's committment to Outreach Program for Women, we're
1 - 100 of 197 matches
Mail list logo