[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Regarding development of an application for KDE
From: Atri Sharma <atri.jiit () gmail ! com>
Date: 2012-03-01 3:49:21
Message-ID: CAOeZVidohfeKWwsAKjY++_j+TjxO-Y3odT+TMc9BTnidYQjVJQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi all,
I think we have nearly finalized some of the features that can be included:
1)BUGS list.
2)Synchronization between TODO and IDE.
3)A commiters list(and their commits and their availablity)
4)Probably,a feature that sends a diff as an patch email to the relevant
list.
I think these features would be great on the plasma dashboard.
Milian:finally I understand what you meant.You mean that we should
integerate small parts,that make sense.Sure,I'll do that.
Please let me know your comments.
Atri
On Thu, Mar 1, 2012 at 3:48 AM, Kevin Krammer <kevin.krammer@gmx.at> wrote:
> On Wednesday, 2012-02-29, Milian Wolff wrote:
> > On Wednesday 29 February 2012 22:03:24 Kevin Krammer wrote:
>
> > > For example assume that you access to KDE's committer list (I think
> there
> > > is an Akonadi resource for that) and also access to Telepathy. The
> > > git/svn blame view/annotation could display the respective committers
> IM
> > > availability.
> > >
> > > Or sending the current diff as a patch email to the author or
> mailinglist
> > > the code is associated with.
> >
> > yes, showing such info is fine but as soon as one wants to interact with
> > some person a designated app like kopete or telepathy or kmail or ...
> > should be opened.
>
> In general I would agree but it depends largely on the feature.
> For example for collaborative editing (e.g. like Google docs) or just
> letting
> the other user having a passive view of what you are doing (e.g. like most
> webinar viewers) might benefit from having the messaging channel to that
> person
> inline.
>
> Cheers,
> Kevin
> --
> Kevin Krammer, KDE developer, xdg-utils developer
> KDE user support, developer mentoring
>
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>
>
[Attachment #5 (text/html)]
<div>Hi all,</div>
<div> </div>
<div>I think we have nearly finalized some of the features that can be \
included:</div> <div> </div>
<div>1)BUGS list.</div>
<div>2)Synchronization between TODO and IDE.</div>
<div>3)A commiters list(and their commits and their availablity)</div>
<div>4)Probably,a feature that sends a diff as an patch email to the relevant \
list.</div> <div> </div>
<div>I think these features would be great on the plasma dashboard.</div>
<div> </div>
<div>Milian:finally I understand what you meant.You mean that we should integerate \
small parts,that make sense.Sure,I'll do that.</div> <div> </div>
<div>Please let me know your comments.</div>
<div> </div>
<div>Atri</div>
<div> </div>
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">On Thu, Mar 1, 2012 at 3:48 AM, Kevin Krammer <span \
dir="ltr"><<a href="mailto:kevin.krammer@gmx.at">kevin.krammer@gmx.at</a>></span> \
wrote:<br> <blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px \
0.8ex;PADDING-LEFT:1ex" class="gmail_quote"> <div class="im">On Wednesday, \
2012-02-29, Milian Wolff wrote:<br>> On Wednesday 29 February 2012 22:03:24 Kevin \
Krammer wrote:<br><br></div> <div class="im">> > For example assume that you \
access to KDE's committer list (I think there<br>> > is an Akonadi resource \
for that) and also access to Telepathy. The<br>> > git/svn blame \
view/annotation could display the respective committers IM<br> > > \
availability.<br>> ><br>> > Or sending the current diff as a patch email \
to the author or mailinglist<br>> > the code is associated \
with.<br>><br>> yes, showing such info is fine but as soon as one wants to \
interact with<br> > some person a designated app like kopete or telepathy or kmail \
or ...<br>> should be opened.<br><br></div>In general I would agree but it depends \
largely on the feature.<br>For example for collaborative editing (e.g. like Google \
docs) or just letting<br> the other user having a passive view of what you are doing \
(e.g. like most<br>webinar viewers) might benefit from having the messaging channel \
to that person<br>inline.<br> <div class="HOEnZb">
<div class="h5"><br>Cheers,<br>Kevin<br>--<br>Kevin Krammer, KDE developer, xdg-utils \
developer<br>KDE user support, developer mentoring<br></div></div><br><br>>> \
Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe <<<br> <br></blockquote></div><br>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic