oVirt Weekly Meeting
by Mike Burns
The following is a new meeting request:
Subject: oVirt Weekly Meeting
Organizer: "Mike Burns" <mburns(a)redhat.com>
Location: #ovirt of oftc.net
Time: Wednesday, April 25, 2012, 10:00:00 AM - 11:00:00 AM GMT -05:00 US/Canada Eastern
Required: danken(a)redhat.com; oschreib(a)redhat.com; ykaul(a)redhat.com; sgordon(a)redhat.com; dfediuck(a)redhat.com
Optional: arch(a)ovirt.org; board(a)ovirt.org
*~*~*~*~*~*~*~*~*~*
Weekly Sync Meeting for the oVirt Project
* This meeting will take place at 10:00 AM EDT and follow US DST.
* A call for agenda items will be sent out weekly on Monday or Tuesday
Standing Agenda items:
* Next Release status
* Sub-Project report
Required Attendees:
* The maintainer or a delegate from each of the core projects (node, engine, vdsm)
* Docs representative
* QE Representative
* Release Manager
* Anyone who proposes a topic for discussion for the meeting
12 years
oVirt Weekly Sync Meeting cancelled due to lack of attendence
by Mike Burns
There was a distinct lack of attendance today at the weekly sync
meeting, so we ended without discussing anything.
We really need to get people to start attending this meeting so that we
can make sure we're still on target for upcoming releases.
Thanks
Mike
12 years
Resources for automated builds and testing
by Mike Burns
Are there any plans to have additional resources for Jenkins? There is
an almost constant queue of builds waiting to run. If we continue to
develop automated testing, then this will only continue to get worse.
We've already had to disable all gerrit integration which is not an
ideal situation for continuous testing. Additional resources, whether
they're EC2 or some other public cloud offering, or provided by one of
the sponsor companies, would be a huge help.
Thanks
Mike
12 years
Meeting minutes :: Weekly sync 2011-04-04
by Karsten 'quaid' Wade
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Minutes:
http://ovirt.org/meetings/ovirt/2012/ovirt.2012-04-04-15.01.html
Minutes (text):
http://ovirt.org/meetings/ovirt/2012/ovirt.2012-04-04-15.01.txt
Log:
http://ovirt.org/meetings/ovirt/2012/ovirt.2012-04-04-15.01.log.html
==============
#ovirt Meeting
==============
Meeting started by quaid at 15:01:05 UTC. The full logs are available at
http://ovirt.org/meetings/ovirt/2012/ovirt.2012-04-04-15.01.log.html .
Meeting summary
- ---------------
* Agenda (quaid, 15:04:19)
* LINK: http://www.ovirt.org/wiki/Meetings#Weekly_project_sync_meeting
(quaid, 15:04:28)
* Meeting timing (quaid, 15:06:15)
* AGREED: Weekly meetings are a good thing, just make them quick if
there isn't much to discuss (quaid, 15:12:20)
* AGREED: Keep meetings at 1400 UTC starting 11 Apr (quaid, 15:12:36)
* ACTION: quaid and rbergeron to sort out the mass invite (quaid,
15:13:07)
* AGREED: Decide on DST plans in 4 months when it comes around again
... (quaid, 15:13:28)
* ACTION: quaid to circle with pilhuhn on an oVirt shared calendar,
then get back to infra@ for approval (quaid, 15:14:45)
* Release status (quaid, 15:15:08)
* ACTION: oschreib to take VDSM-libvirt-F17 target discussion to arch@
(quaid, 15:31:14)
* ACTION: oschreib to bring spec file changes decision to arch@
(quaid, 15:42:43)
* ACTION: oschreib to make sure sgordon_ has manual steps for upgrade
for release notes (quaid, 15:42:56)
* Infrastructure team (quaid, 15:43:21)
* ACTION: quaid to prepare thoughts about infra team for next meeting
(quaid, 15:43:51)
* DCO for all sub-projects (quaid, 15:44:34)
* http://kerneltrap.org/files/Jeremy/DCO.txt (rharper, 15:46:56)
* ACTION: rharper Settle DCO topic on arch@ (quaid, 15:53:06)
* AGREED: We don't see any objection to using DCO (quaid, 15:53:17)
* Do we want some more formal information from sub-projects in the
weekly sync? (quaid, 15:54:40)
* ACTION: quaid to pester arch@ to send a representative from each
oVirt component project to the weekly sync (quaid, 15:57:21)
* anything else? (quaid, 15:57:43)
Meeting ended at 15:58:38 UTC.
Action Items
- ------------
* quaid and rbergeron to sort out the mass invite
* quaid to circle with pilhuhn on an oVirt shared calendar, then get
back to infra@ for approval
* oschreib to take VDSM-libvirt-F17 target discussion to arch@
* oschreib to bring spec file changes decision to arch@
* oschreib to make sure sgordon_ has manual steps for upgrade for
release notes
* quaid to prepare thoughts about infra team for next meeting
* rharper Settle DCO topic on arch@
* quaid to pester arch@ to send a representative from each oVirt
component project to the weekly sync
Action Items, by person
- -----------------------
* oschreib
* oschreib to take VDSM-libvirt-F17 target discussion to arch@
* oschreib to bring spec file changes decision to arch@
* oschreib to make sure sgordon_ has manual steps for upgrade for
release notes
* quaid
* quaid and rbergeron to sort out the mass invite
* quaid to circle with pilhuhn on an oVirt shared calendar, then get
back to infra@ for approval
* quaid to prepare thoughts about infra team for next meeting
* quaid to pester arch@ to send a representative from each oVirt
component project to the weekly sync
* rharper
* rharper Settle DCO topic on arch@
* sgordon_
* oschreib to make sure sgordon_ has manual steps for upgrade for
release notes
* **UNASSIGNED**
* (none)
People Present (lines said)
- ---------------------------
* quaid (80)
* oschreib (41)
* mburns (34)
* rharper (23)
* abaron (13)
* ovirtbot (5)
* sgordon_ (4)
* READ10 (1)
* cdub (1)
* fsimonce (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
- --
name: Karsten 'quaid' Wade, Sr. Community Architect
team: Red Hat Community Architecture & Leadership
uri: http://communityleadershipteam.org
http://TheOpenSourceWay.org
gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFPfHAi2ZIOBq0ODEERAguPAJwMdvPh/WlxbPnq35aaDHCfibTaMACcCxAr
N65OEJdqZ84Arg0HHvNK+io=
=bnjl
-----END PGP SIGNATURE-----
12 years
code sign-off/DCO for ovirt projects
by Ryan Harper
I see that this was discussed in the past on the board list[1] and there
didn't seem to be any disagreement with doing DCO sign-off for code
contributions. However, not all of the ovirt projects are doing
DCO/Sign-off. There are a few commits in vdms.git that have a SoB,
ovirt-node seems to be using DCO completely. Nothing in ovirt-engine
either. I didn't check all of the ovirt subprojects, but I think
it's safe to assume that's not being applied across all of the
projects consistently.
Can we get that added to the commit process for these projects moving
forward? Is there anything else needed beyond maintainers enforcing the
need for SoB in patches?
1. http://lists.ovirt.org/pipermail/board/2011-October/000168.html
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh(a)us.ibm.com
12 years
