[rdo-list] Website reorg
by Rich Bowen
Petr, sorry, I had to go into a meeting, and our conversation on IRC was
left unfinished.
You said:
pkovar: it would be best to have a single place where we describe the
community channels, events, etc. but since we have /community *and*
/events, its kinda difficult
/events is just the calendar, and is generated from the yml files in
https://github.com/OSAS/rh-events I think that /community is probably
the place to consolidate everything else, with more descriptive prose,
and have the /events page just be the calendar.
We've also got the split between docs days (which is under
/events/docdays) and test days, (which is under /testday) and this
inconsistency is irritating. Those, too, should be in the same place, as
they are different ways for the community to engage at scheduled times.
If we want to reorg the site to make the information tree more sensible,
we can absolutely do that. The structure we have now has grown
organically, and if a different/better organization makes sense to you,
let's figure out what that needs to be, and make the change.
--Rich
--
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity
7 years, 7 months
[rdo-list] RDO Docs Day, June 8, 9
by Rich Bowen
Following up on the Contributor Survey, we discussed in today's IRC
meeting what we can do to address some of the concerns expressed by
contributors. The number one thing, of course, is docs.
To this end, we're planning to do a Docs Day on June 8/9th, one week
before the Pike M2 Test Day.
The specific items discussed that we want to address, I'll be adding
issues to the docs repository issue tracker -
https://github.com/redhat-openstack/website/issues - and adding more
information to the doc days page at
https://www.rdoproject.org/events/docdays/
I encourage you to open tickets about any aspect of our
website/documentation which you feel is inadequate, confusing, outdated,
or wrong.
--
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity
7 years, 7 months
[rdo-list] [Meeting] RDO meeting (2017-05-24) Minutes
by Alfredo Moralejo Alonso
==============================
#rdo: RDO meeting - 2017-05-24
==============================
Meeting started by amoralej at 15:04:30 UTC. The full logs are
available at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_05_24/2017/rdo...
.
Meeting summary
---------------
* roll call (amoralej, 15:04:42)
* [dmsimard] review.rdoproject.org maintenance: software-factory upgrade
@ friday may 25th 00:00 UTC (thursday may 24th 8PM EST) (amoralej,
15:09:20)
* https://www.redhat.com/archives/rdo-list/2017-May/msg00050.html
(amoralej, 15:09:30)
* [jpena] RDO Infra service continuity plan (amoralej, 15:11:33)
* LINK: https://www.rdoproject.org/infra/service-continuity/
(amoralej, 15:11:57)
* trunk.registry.rdoproject.org is live: container images for TripleO
based on Kolla (amoralej, 15:22:27)
* Results of contributors survey published, what should we improve?
(amoralej, 15:36:16)
* LINK:
https://www.redhat.com/archives/rdo-list/2017-May/msg00051.html
(amoralej, 15:36:26)
* ACTION: Rich to announce docs day to list, and start list of
specific things we want to work on. (rbowen, 15:43:08)
* chair for next meeting (amoralej, 15:49:56)
* ACTION: jpena to chair next meeting (amoralej, 15:50:31)
* open floor (amoralej, 15:50:41)
Meeting ended at 15:54:42 UTC.
Action items, by person
-----------------------
* jpena
* jpena to chair next meeting
People present (lines said)
---------------------------
* amoralej (50)
* dmsimard (32)
* rbowen (19)
* jpena (16)
* apevec (14)
* Duck (7)
* openstack (6)
* adarazs (5)
* rdogerrit (2)
* trown (1)
* ykarel (1)
* hrw (1)
* number80 (1)
* chandankumar (1)
Generated by `MeetBot`_ 0.1.4
7 years, 7 months
[rdo-list] RDO Contributor Survey - results
by Rich Bowen
A while ago we asked you to participate in a contributor survey for RDO.
I've written up the results here:
https://www.rdoproject.org/blog/2017/05/rdo-contributor-survey/
Below I've included the full responses to the open-format questions.
First, we asked how difficulties were overcome when encountered. The
responses were:
Asked on IRC
With the great help of the community
Asking other members
I didn't, gave up. Contribute directly to TripleO now.
asking on IRC
Ask on IRC
With patience
Discuss with people
Helpful engineers in IRC
Packstack
Have had to learn by hard knocks for getting packaging changes figured
out how to get them in and how to get them reviewed and merged
Discussing on freenode, #rdo
Generally just ping enough folks on IRC, or hack and slash my way
through packaging contributions.
Next, a more open-ended "Do you have further comments on the
contribution process?" got the following results:
Some use cases for packagers are not totally straightforward
Would love to help with documentation and see and participate in a
dedicated group to provide great RDO documentations
Make clearer where repos are located, how changes procedure works (need
bugs, backport policies, etc)
The RDO website needs paring down to a minimum. Too much old information.
the processes seem to change very often. no value in learning the
process, it's necessary to read the docs for each contribution (and then
ask, because docs are outdated)
I'll mostly comment on the process to add a new package to RDO because
that's the area where my experience was not so great. The documentation
was fine, the tools also, the only thing that bothered me was the slow
review process. I think most of the frustration boils down to the lack
of reviewers with only 2 peopleo who could approve new packages changes
at the time (I was told this has changed).
The biggest mystery to me is packaging. I'm trying to learn, but it's
like drinking from a firehose. So far I've had to rely on others to do
all packaging tasks.
Some maybe less frequent processes could receive a bit more of
documentation (just an example: how to handle same version of RPM tagged
in more repositories, etc)
Reviewing the current set of documentation, and making it clear where to
start, and how to contribute from start to end, would be a huge
improvement. A lot of the time the issue is less around the actual RPM
building, and more around the tooling and finding where the start point is.
--
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity
7 years, 7 months
[rdo-list] OpenStack Day France 2017: Call for presentations
by Rich Bowen
FYI - forwarding this message from over on the OpenStack-Community
mailing list. If you're in or near France, please consider submitting a
presentation for this event - OpenStack Day France, Paris, November 21st
<Forwarded message follows>
Hello,
OpenStack-fr is organizing the second edition of OpenStack Day France,
held in Paris, following the success of the 2016 edition.
Please mark your calendar for November 21st, 2017!
Call for sponsors and call for speakers are now open.
The event website has a link to the call for speakers form:
https://openstackdayfrance.fr/
Regarding sponsors, details are included in this document:
https://openstackdayfrance.fr/wp-content/uploads/2017/05/OpenStack-Day-Fr...
Please note that right now all sponsorship opportunities are available
(with or without booth, with or without keynote). All sponsorship
applications received by June 1st will be considered together, and
first-come first-serve will be applied afterwards.
More infomations, including opening of registraton, will be available in
the coming weeks!
If necessary, you can reach the organizing team at
openstackdayfrance(a)listes.openstack.fr.
Adrien
--
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity
7 years, 7 months
[rdo-list] [infra] RDO Infra service continuity plan ready for discussion
by Javier Pena
Hi all,
We are migrating most of our infrastructure, previously scattered around multiple providers, to the RDO Cloud. This is a good opportunity to rethink were our services are placed, and our plans for a recovery in case something goes wrong on the RDO Cloud.
So, we have a service continuity draft at https://www.rdoproject.org/infra/service-continuity/ . If you have some time, please have a look at it and propose ideas. Just be aware that our budget for infrastructure is tight, so we cannot afford unlimited resources... unless someone is willing to donate them :).
Thanks,
Javier
7 years, 7 months
[rdo-list] Speakers wanted, St. Louis
by Rich Bowen
If you are in, or near, the St Louis area, the StL OpenStack meetup
group is once again looking for speakers. They're primarily interested
in technical presentations, not product/sales presentations.
If you're nearby and interested, please contact me off-list and I'll
make the necessary intros. Thanks.
--
Rich Bowen - rbowen(a)redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity
7 years, 7 months
