The differentiation in "core" and "peripheral" roles has been established and largely accepted within the Free/Libre/Open Source Software (FLOSS) development approach, assigning to each role different responsibilities and productivity patterns. A further, cross-cutting characterization of developers within the FLOSS approach could be formulated clustering developers into "time slots", and different patterns of activity and effort assigned to such slots. Such analysis, if replicated, could be used not only to compare different FLOSS communities, or to evaluate their stability and maturity, but also to determine how the effort is distributed in a given period, and to estimate future needs in proximity of key points (e.g., major releases).This study analyses the activity patterns within the Linux kernel project, at first focusing on the overall distribution of effort and activity within weeks and days; then, dividing each day into three 8-hour time slots, and around major releases. Such analyses have the objective to evaluate effort, productivity and types of activity globally and around major releases, compare these patterns with traditional software products and processes, in turn identifying company-driven projects (i.e., working mainly during office hours) among FLOSS endeavors.The results of this research show that, overall, the effort within the Linux kernel community is constant (albeit at different levels) throughout the week, signalling the need of updated estimation models, different from those used in traditional 9am-5pm, Monday to Friday commercial companies. It becomes also evident that the activity before a release is vastly different from after a release, and that the code quality decreases in specific time slots (notably in late night hours), which later will require additional maintenance efforts.