From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============1911286857811625494==" MIME-Version: 1.0 From: Chris Ferron Subject: [Powertop] [Announcement] General PowerTOP Announcement Date: Fri, 31 Aug 2012 10:55:41 -0700 Message-ID: <5040FA9D.8090003@linux.intel.com> To: powertop@lists.01.org List-ID: --===============1911286857811625494== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hello, There are some new enhancements to the PowerTOP project coming, so = it's time to take a moment and send out an update. The project has seen = a steady increase in activity, and as such this is a good time to get = things kicked off. UPDATES: Community Meetings - There are plans to attempt community meetings over = IRC or GOOGLE+ hangout shortly after each release. The point of the = meeting is to communicate about what matters to the community for the = next release. In this meeting members will contribute to what is added = to PowerTOP's TODO list, discuss what PowerTOP needs for the next = release. The first meeting attempt will be held the second week of = September. A notice and more details will be sent in a separate email to = discuss and finalize. Releases - Back in May PowerTOP v2.0 was released, and three months = later in August a minor release of v2.1 was completed. There is an = intent to execute a minor release every 3 months going forward. See = schedule below. Email List - The PowerTOP project at this time uses the mailing list for = all communications. Starting ASAP it would be appreciated if all members = use categorize subject headings, as it is important to title your mail = for organization. Example: [Patch] - used to signify a patch or patch set [Feature Request] - used to request a feature [Bug] - used to report a Bug [RFC] - used to request comments from the community on a patches or ideas [Announcement] - used by maintainers to send announcements This way the content of messages can be tracked more accurately. Non-Intel Hardware - There has been some great additions to PowerTOP as = of late. Mostly work on getting ARM more enabled. This is fantastic, and = appreciated. But as a note, the current maintainers don't spend much = time working on non Intel Architecture for obvious reasons. BUT we (the = maintainers) are happy to accept work to enable non Intel Architectures, = and in fact encourage it. That said, members can also expect that = maintainers will not be doing a lot of testing or triage on areas not = evolving Intel Architecture. With that said, there will be some scouting = of participating members to possibly be trusted reviewers to help out = here. More about this below. Roles - The PowerTOP project is growing, and we have some interesting = ambitions on PowerTOP's future. As needed rolls will be added and = scouting for prospective active members to fill those roles will also = happen as needed. As needs increase, so will the roles when it becomes = applicable. One of the roles we would like to start with is "Trusted = Reviewer". Please also note that roles are not going to be added without = good reason, the intent is not to build a huge hierarchy here. A "Trusted Reviewer" is someone who maintainers trust to sign-off on = patches. For instance we will be scouting for someone to be a "Trusted = Reviewer" for ARM-specific patches. This person will be someone who = works and has experience with ARM architecture, and has been a solid = contributor to PowerTOP. "Trusted Reviewers" will not have commit rights = at this time, but patches will accepted or denied based on a "Trusted = Reviewers" comments. I'm hoping that this will help increase the quality = of code accepted while shortening the time it takes to review and accept = submissions. With that explained, Sergey Senozhatsky has been named one of the first = Trusted Reviewers of PowerTOP. His high quality code, consistent = communication, and efforts towards PowerTOP has earned him trust with = the maintainers. Current Roles - The current roles and persons are; Project Owner / Maintainer - Arjan Van de ven Maintainer - Chris Ferron Transifex Project Owner - Margie Foster General Trusted Reviewer - Sergey Senozhatsky Arm Trusted Reviewer - TBD Tentative Schedule - Here is the tentative schedule for the next nine = months. Nov 1st (string freeze) Nov 15th (release v2.2) Nov 22nd (community meeting about v2.3) Feb 1st (string freeze) Feb 15th (release v2.3) Feb 22nd (community meeting about v2.4) May 1st (string freeze) May 16th (release v2.5) May 23nd (community meeting about v2.6) Cheers, Chris --===============1911286857811625494==--