I really think that the commit review is something very important. If nobody is doing that I'll take a look at it soon, I've been thinrking of doing it already. It might make the vcs support actually useful :P.<br>
<br>About the frontpage, there is already some work on it by Leinir somewhere, but it was discontinued. We should just integrate it with the actual code.<br><br>The rest of stuff to have integrated is not urgent imho. (like <a href="http://cia.vc">cia.vc</a>, mailing lists, irc). Chat could easily be integrated through Decibel, I'm not sure what would be the integration here, though.<br>
<br>Thanks,<br>Aleix<br><br><div class="gmail_quote">On Mon, Aug 3, 2009 at 1:40 PM, Milian Wolff <span dir="ltr"><<a href="mailto:mail@milianw.de">mail@milianw.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">Kishore wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Monday 03 Aug 2009 4:21:17 pm Dan Leinir Turthra Jensen wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Monday 03 August 2009 12:46:06 Milian Wolff wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello guys!<br>
<br>
I really like the ideas Cornelius came up with when working on his KDE<br>
SDK. He made the choice to patch Qt Creator, but imo his ideas are too<br>
good not to be used for KDevelop as well.<br>
<br>
Basically I think we should revise our ideas about the KDevelop splash<br>
screen. It is a nice-to-have thing for a first impression. Especially<br>
newcomers might be helped with getting started.<br>
<br>
But for "us", e.g. people who use KDevelop regularly I think Cornelius'<br>
ideas would be more helpful. I imagine a project-dashboard. When I hack<br>
on something with others I might want to know what they did:<br>
<br>
- recent commits with commit message. diffs just a click away, nicly<br>
integrated kompare part or similar<br>
- communication:<br>
* commit review (i.e. display discussion in kde-commits archive)<br>
* recent discussion on mailing list (again: just display archive).<br>
Also a way to get to the registration site for the mailing list.<br>
* maybe even a list of contributors to the project with ways to<br>
contact them, I imagine:<br>
- mail adress (on hit => fav mail prog)<br>
- any kind of IM (on hit => fav mail prog)<br>
- IRC nick (on hit => fire up fav IRC prog, connect to server [if<br>
not already there] and query the user, or join channel and write<br>
there...) - social aspect:<br>
* opendesktop integration, esp. kde-apps<br>
- rating<br>
- comments<br>
- ...<br>
* reviewboard integration<br>
<br>
I think this would be a great feature. Want to contribute to project<br>
XYZ? No problem, just check it out and it's description file (like the<br>
XML file Cornelius talks about) gives you all information to populate<br>
the dashboard. No need to search for the mailing list, no need to setup<br>
commit-filter. Looking for help just contact a devel via IM or similar.<br>
And especially commit reviewing could be made much easier this way.<br>
Looking at diffs in Kmail is OK but having it in Kompare with the<br>
original sources just a few clicks away is kick-ass imo :) Especially<br>
with a simple way to apply the patch, then build the project etc. etc...<br>
<br>
And to clarify: The dashboard should mostly just open external apps like<br>
KMail/Kopete/... or integrate KParts like Kompare. Most of the stuff<br>
above shouldn't be too hard to implement.<br>
<br>
The page should be shown in the main-content area (as a tab) when<br>
opening the project. You can close it if you want to. To reopen e.g.<br>
"open" the root item of the project in project-view or have a "toggle<br>
dashboard" menu entry in project group.<br>
<br>
What do you think?<br>
</blockquote>
i like the way you think :)<br>
</blockquote>
<br>
I always thought that the teamwork plugin's goal was to provide at least some of the above mentioned features. I look forward to using it in it's full potential.<br>
</blockquote>
<br></div></div>
Wasn't teamwork intended to provide ways for concurrent editing? I.e. edit one file at the same time? But I have to admit that I have never used the plugin nor have and in-depth knowledge of what it really wants to give.<div class="im">
<br>
<br>
-- <br>
Milian Wolff<br>
<a href="http://milianw.de" target="_blank">http://milianw.de</a><br>
<br>
_______________________________________________<br></div><div><div></div><div class="h5">
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org" target="_blank">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</div></div></blockquote></div><br>