Component Maintainers

[David Edmundson]

On Thu, Jun 21, 2012 at 6:21 PM, David Edmundson
<david at davidedmundson.co.uk> wrote:
> On Thu, Jun 21, 2012 at 5:53 PM, Vishesh Handa <me at vhanda.in> wrote:
>>
>>
>> On Thu, Jun 21, 2012 at 4:11 AM, David Edmundson
>> <david at davidedmundson.co.uk> wrote:
>>>
>>> As part of my new hobby of meddling in plasma, we decided they need to
>>> work on is a list of "who is the maintainer for which component", so
>>> I'm having a trial run with KTp.
>>>
>>>
>>> http://community.kde.org/Real-Time_Communication_and_Collaboration/Components/Overview#Component_Overview
>>>
>>> Could everyone look over this and check you agree with everything there.
>>
>>
>> I can't seem to find ktp-ontology. As its maintainer I should checkout the
>> code!
>>
>> $ git clone kde:ktp-ontology
>> Cloning into 'ktp-ontology'...
>> fatal: The remote end hung up unexpectedly
>>
> It's bugzila component based. It's part of a different repo.
>
> There's no chat-plasmoid either, it's part of the text-ui. We just
> split it here.
> Makes it easier to say "Lasath is in charge of the message plugins in
> the text-ui", but I'm in charge of the text-ui.
>
Edit: If you want to merge them in this wiki, go for it!

>
>>>
>>> To anyone who's not on this list, this doesn't mean you're work isn't
>>> valued -  Puneet G, Dominik K,  Rohan G and Thor to name just a few.
>>
>>
>> Whoa! You have a contributor called "Thor". That's so cool!
>>
> He once got banned from Ryan Air for taking a hammer in his hand
> luggage on his way to a conference.
> Here's a picture of him bug triaging at the last sprint:
> http://tinyurl.com/ch33mw5
>
>
>>>
>>> It really is, just not what in the category of "senior dev" who can
>>> make large design choices (yet!). Obviously if you disagree, let me
>>> know. Also lets try to keep this up to date, as people leave and
>>> others take over more things.
>>>
>>> I think it's quite interesting to see which components don't have a
>>> large number of maintainers, these are places where it's probably a
>>> good idea to focus on bringing in different developers and making sure
>>> they're "trained" on it.
>>
>>
>> I agree :)
>>
>>>
>>>
>>> Dave
>>> _______________________________________________
>>> KDE-Telepathy mailing list
>>> KDE-Telepathy at kde.org
>>> https://mail.kde.org/mailman/listinfo/kde-telepathy
>>
>>
>>
>>
>> --
>> Vishesh Handa
>>
>>
>> _______________________________________________
>> KDE-Telepathy mailing list
>> KDE-Telepathy at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-telepathy
>>