Akademy talk proposal

[Vladislav Blanton]

Great idea Marta!

my two cents:

1) I think it is important that commits not become annoyances for devs. On
one hand there are things that would be helpful for us and improve the
completeness of the digest, but on the other hand I'd want to make sure
that devs don't feel stymied in their workflow by having to worry about
formatting their commit text. Thus, I suggest some basic guidelines as to
what makes a good commit text *for us* a two-way discussion about what
would work *for devs and us*. It would be cool if a few of us could get out
to the aKademy for the talk.

2) a callout to improve kde/git technology (easy way to tag?).

also I second roger, it would be great for devs to fill in stats!

Vlad

On Mon, Feb 6, 2012 at 9:17 AM, Roger Pixley <skreech2 at gmail.com> wrote:

> I've been having pretty good success with asking devs and having them be
> happy about the chance to speak more on their project. I've only met with
> one person who wasn't thrilled and that was because they had a great deal
> of work surrounding them (And indeed they have not come back to me with an
> article).
>
> However I can't say wht the response would be when they would like to
> request an article from a particular commit and we don't deem that as
> necessary. however I do like the idea if it could be tuned.
>
> Marta, It's a good idea for a talk and once that I'm sure will be
> interesting. It could outlay the role of the digest in the community and
> help people to see all the ways that everyone could benefit from their
> involvement :-) Could you drop a mention about filling in the profile for
> stats? it's a nice way to round out the coding community's knowledge of
> itself.
>
>
> On Sun, Feb 5, 2012 at 2:36 PM, mutlu_inek <mutlu_inek at yahoo.de> wrote:
>
>> Marta,
>>
>> This is a great initiative. :) I just want to contribute some rather raw
>> ideas, before your email gets dusty in the archives. Feel free to tear it
>> all apart.
>>
>> As all of us will probably know, some developers already add notes to
>> their feature commits. Some seem to be using FEATURE and some DIGEST as
>> keywords. We should probably define how to use these keywords and propose
>> their wider adoption. An update to Enzyme that would mark such commit
>> messages in a way similar to bug fixes would make us not overlook them by
>> accident. I would propose that FEATURE means that a new feature has been
>> added to a KDE program. DIGEST on the other hand does npt need to concern a
>> feature, but could be meant to raise the reviewers awareness and call for
>> more detailed description in the digest. Alternatively, even something like
>> ARTICLE could be proposed, prompting a request to write a few lines for a
>> feature article for the digest. However, I think the latter keyword would
>> be used rarely if ever, since few devs are really thrilled when we want
>> them write something up.
>>
>> If at least the FEATURE keyword would be taken up by all developers, the
>> reviewing would get quite a bit easier. I don't think it would ever become
>> obsolete, since too much interesting stuff, especially in "playground" (for
>> example, all the work on conqueire over the past weeks) would be overlooked.
>>
>>
>> Any other ideas?
>>
>> Cheers, mutlu
>>
>>
>>
>>
>> ----- Ursprüngliche Message -----
>> Von: Marta Rybczynska <kde-i18n at rybczynska.net>
>> An: digest at kde.org
>> Cc:
>> Gesendet: 21:31 Samstag, 4.Februar 2012
>> Betreff: Akademy talk proposal
>>
>> Hello all,
>> The Akademy Call for Papers is out. I have an idea of a talk with the
>> working
>> title of "How to make your commit seen?" about the ways developers may
>> make our life easier.
>>
>> When I think more about it, it is about commit message
>> writing, dividing feature set into commits (and git workflow in general),
>> special tags, comments in the code etc etc.
>>
>> I'm going to make some research for the talk, but I'd like to hear your
>> impressions, esp. the things you'd like to pass to the developers.
>>
>> Thanks,
>> Marta
>> _______________________________________________
>> Digest mailing list
>> Digest at kde.org
>> https://mail.kde.org/mailman/listinfo/digest
>>
>> _______________________________________________
>> Digest mailing list
>> Digest at kde.org
>> https://mail.kde.org/mailman/listinfo/digest
>>
>
>
> _______________________________________________
> 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/20120206/7ae4947b/attachment-0001.html>