newbie guide for Enzyme and commit digest?

[Roger Pixley]

The Writeup is either from some series of significant commits or something
that is relatively topical. So your choice may come from either a series of
commits that you noticed, a blog post that can be explained with a more
technical eye or a more thorough followup on the commit digest or something
that you know of personally. An example could be a project moving into
Extragear on KDE's repo from an external repo. They can do an introduction
of why they are doing the move and what it will mean when their commits
start turning up (and how YOU can help ) So something topical may not
necessarily have to do with a commit that happened this week but should be
about a project which currently has meaningful activity going on even if a
particular commit or series of commits didn't stand out this week, However
easily something that closes numerous bugs or opens up new uses would be a
good candidate to ask for a write up on what those commits mean.

The Standard text was posted earlier (today not earlier than your mail) in
the mailing list.

I recall Danny had a post on those stats on his blog maybe three years ago.
I think it's pulled from the profile information for the people who have
done commits in the time period. Not sure if there is a simple way to get
the ones that have missing information.

On Sat, Dec 11, 2010 at 5:49 AM, Alexander van Loon <
a.vanloon at alexandervanloon.nl> wrote:

> Hello,
>
> Finally I have been able to find a substantial amount of free time this
> weekend (and I assume, in the future also on workdays) to get some work
> done for the digest. First steps for me were to read Stuart Jarvis’ blog
> post – http://www.asinen.org/2010/10/one-hour-to-save-the-commit-digest/
> – and the ‘Using Enzyme’ and the ‘Inclusion Guidelines’ help documents
> in Enzyme itself. Unfortunately it’s still not very clear to me how I
> can help:
>
>     1. The guidelines for reviewing are evident, but it’s not possible
>        to undo an inclusion or exclusion if I’m correct? This makes me
>        reluctant to review.
>     2. What does ‘Insert’ do? It isn’t explained anywhere.
>     3. So in ‘Digests’ I can apparently type the introductory text with
>        a summary of all the activity that week for each of the
>        unfinished digests. But how do I see the commits belonging to
>        that week, so I can summarize them?
>     4. Stuart Jarvis’ blog post describes e-mailing developers to ask
>        them for input on a story for the commit digest. I assume such a
>        story needs to be related to the activity of that specific week
>        like in the case of [3], or isn’t that necessary?
>     5. How am I going to figure out which developers I need to e-mail
>        to ask for their input on a story for the digest? I assume I’m
>        going to be able figure that out by looking at the commit
>        activity, so I need to get some experience for a week or so by
>        looking at the commit activity? Or does anyone have any
>        suggestions on whom I should contact to write a story for a
>        specific commit digest? Are the suggestions by the last
>        commenter on Stuart Jarvis’ blog post any good?
>     6. In his blog post he mentions a standard e-mail text, what would
>        that standard text be?
>
> Another question regarding to the commit digest itself, the statistics
> displaying nationality and sex, volunteer/commercial occupation and age
> of the committers display respectively 28,76%, 24,06%, 44,07% and 51,17%
> unknown as of the most recent commit digest. I love these statistics and
> I’d like them to be reliable, how would we make them more reliable?
> E-mail all committers for which the data is unknown and ask them to give
> the information? Might be a lot of work, but I’m willing to do it.
>
> Greetings,
> Alexander van Loon
>
> _______________________________________________
> Digest mailing list
> Digest at kde.org
> https://mail.kde.org/mailman/listinfo/digest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/digest/attachments/20101212/7d248a50/attachment.htm