Re: Transition of OProfile maintainership
Maynard Johnson <[email protected]>
| Newsgroups | gmane.linux.oprofile |
|---|---|
| Message-ID | <[email protected]> |
On 10/17/2014 11:30 AM, Maynard Johnson wrote:
> To the whole OProfile community:
>
> After 6 years of serving in the role of lead maintainer for the OProfile project, it's time for me to pass the baton to someone else. I'll be retiring in late December, so I would like to have this transition completed by early December. Currently, the project is in pretty stable condition, with just a few open bugs and feature requests. The primary task of the lead maintainer is to ensure submitted patches are well-reviewed and tested before being committed. Sometimes those reviews are handed off to other community members who have the necessary expertise (in particular, architecture-specific patches are usually reviewed by one of the architecture sub-maintainers on cc). For arch-independent patches, reviews from any community members are helpful, but in reality, the lead maintainer
has the final say and so must also review such patches. Another part of the job is to help answer questions that are posted to the mailing list. Traffic on the list is pretty low these days!
, !
> so not a lot of time is required for this.
>
> I encourage all who are interested in this opportunity to contact me, and we can discuss it. Feel free to do so in a private response if you prefer. Thanks.
Unfortunately, there haven't been any offers to take over the oprofile maintainership yet. At the very least, we need someone to act as caretaker of the project (i.e., a "minimalist" maintainer role) or it will simply fade away. I see a caretaker role as follows:
1) Ensures architecture-specific patches are reviewed by an appropriate community member
2) Reviews architecture-independent patches or enlists someone else to do the review
3) Pushes approved patches upstream
4) Once a year (or so), puts out a new release (or enlists someone else to do it).
This is a lot easier than it sounds. The process is fully documented in
oprofile-www/releasechecklist.
It's assumed that a project caretaker would *not* usually have time to answer questions
on IRC or on the mailing list. The rest of the community would have to help out in that
regard in order to keep the project viable -- to attract and keep new members.
So if oprofile is important to you, or your company and its clients, please consider
volunteering.
Thanks.
-Maynard
>
> -Maynard
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> oprofile-list mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oprofile-list
>
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk