User:Chani/GettingStarted - Revision history

Chani: links to my files

2008-08-04T19:05:19Z

links to my files

Chani: update a bunch of info; more to come

2008-08-04T18:49:23Z

update a bunch of info; more to come

Chani: rewording n'stuff. can someone make the formatting not ugly?

2008-02-02T21:08:25Z

rewording n'stuff. can someone make the formatting not ugly?

Chani: found another url too. thanks zander

2008-02-02T19:12:18Z

found another url too. thanks zander

Zander: Add more links

2008-02-02T12:49:21Z

Add more links

Zander: add link

2008-02-02T12:46:12Z

add link

Chani: awful outline, but better than nothing

2008-02-01T13:23:39Z

awful outline, but better than nothing

New page

A quick intro for potential plasma contributors (kdebase and maybe extragear, not playground or other locations)

*Plasma uses kdelibs coding style. there's a file somewhere in svn that makes vim follow this automatically. I know there was a page explaining it, so why can't I find it?
*if a patch is nontrivial, please get it reviewed before committing. best place to do that is http://matt.rogers.name/dashboard/
*mailing list is panel-devel (iirc it's harder to find than other kde lists... what's the url?)

@@ Line 2: / Line 2: @@
 *Plasma uses [[Policies/Kdelibs_Coding_Style|kdelibs coding style]]. there's a file in svn that makes vim follow this automatically: [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim?view=log kde-devel.vim]
-*nontrivial patches should be reviewed before committing. depending on the content of the patch, this could be as simple as getting someone on irc to do a quick sanity-check, or it could turn into a full discussion about the pros and cons of various ways of implementing something. :) we have a [http://reviewboard.vidsolbach.de review board] to post patches to (sadly it only works in firefox), and a script to easily post patches. the original script and instructions for using it are [http://aseigo.blogspot.com/2008/02/post-review-plasma.html on aaron's blog]. note that the reviewboard url and path have changed since that post. if you're using git-svn, you will want the updated script, plus the script for producing compatible diffs.
+*nontrivial patches should be reviewed before committing. depending on the content of the patch, this could be as simple as getting someone on irc to do a quick sanity-check, or it could turn into a full discussion about the pros and cons of various ways of implementing something. :) we have a [http://reviewboard.vidsolbach.de review board] to post patches to (sadly it only works in firefox), and a script to easily post patches. the original script and instructions for using it are [http://aseigo.blogspot.com/2008/02/post-review-plasma.html on aaron's blog]. note that the reviewboard url and path have changed since that post; here's an up-to-date [http://chani.ccdevnet.org/plasma/sample.reviewboardrc sample .reviewboardrc]. if you're using git-svn, you will want the [http://chani.ccdevnet.org/plasma/post-review-plasma updated script], plus [http://chani.ccdevnet.org/plasma/git-svn-diff this script] for producing compatible diffs.
 *our mailing list is [http://mail.kde.org/mailman/listinfo/plasma-devel plasma-devel] ([http://lists.kde.org/?l=kde-plasma-devel&r=1&w=2 archives]). the old mailing list was [http://lists.kde.org/?l=kde-panel-devel&r=1&w=2 panel-devel]. bugs go to a separate list, [http://mail.kde.org/mailman/listinfo/plasma-bugs plasma-bugs].
 *of course, the rest of techbase has lots of important information about contributing to kde in general; you've read that stuff, right?

@@ Line 1: / Line 1: @@
-A quick intro for potential plasma contributors (kdebase and maybe extragear, not playground or other locations)
+A quick intro for potential plasma contributors
 *Plasma uses [[Policies/Kdelibs_Coding_Style|kdelibs coding style]]. there's a file in svn that makes vim follow this automatically: [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim?view=log kde-devel.vim]
-*nontrivial patches should be reviewed before committing. depending on the content of the patch, this could be as simple as getting someone on irc to do a quick sanity-check, or it could turn into a full discussion about the pros and cons of various ways of implementing something. :) we have a new tool to help with this: [http://matt.rogers.name/dashboard/ review board]
+*nontrivial patches should be reviewed before committing. depending on the content of the patch, this could be as simple as getting someone on irc to do a quick sanity-check, or it could turn into a full discussion about the pros and cons of various ways of implementing something. :) we have a [http://reviewboard.vidsolbach.de review board] to post patches to (sadly it only works in firefox), and a script to easily post patches. the original script and instructions for using it are [http://aseigo.blogspot.com/2008/02/post-review-plasma.html on aaron's blog]. note that the reviewboard url and path have changed since that post. if you're using git-svn, you will want the updated script, plus the script for producing compatible diffs.
-*mailing list is panel-devel [http://mail.kde.org/mailman/listinfo/panel-devel subcribe] [http://lists.kde.org/?l=kde-panel-devel&r=1&w=2 archives]
+*our mailing list is [http://mail.kde.org/mailman/listinfo/plasma-devel plasma-devel] ([http://lists.kde.org/?l=kde-plasma-devel&r=1&w=2 archives]). the old mailing list was [http://lists.kde.org/?l=kde-panel-devel&r=1&w=2 panel-devel]. bugs go to a separate list, [http://mail.kde.org/mailman/listinfo/plasma-bugs plasma-bugs].
 *of course, the rest of techbase has lots of important information about contributing to kde in general; you've read that stuff, right?

@@ Line 2: / Line 2: @@
 *Plasma uses [[Policies/Kdelibs_Coding_Style|kdelibs coding style]]. there's a file in svn that makes vim follow this automatically: [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim?view=log kde-devel.vim]
-*if a patch is nontrivial, please get it reviewed before committing. best place to do that is http://matt.rogers.name/dashboard/
+*nontrivial patches should be reviewed before committing. depending on the content of the patch, this could be as simple as getting someone on irc to do a quick sanity-check, or it could turn into a full discussion about the pros and cons of various ways of implementing something. :) we have a new tool to help with this: [http://matt.rogers.name/dashboard/ review board]
 *mailing list is panel-devel [http://mail.kde.org/mailman/listinfo/panel-devel subcribe] [http://lists.kde.org/?l=kde-panel-devel&r=1&w=2 archives]

@@ Line 1: / Line 1: @@
 A quick intro for potential plasma contributors (kdebase and maybe extragear, not playground or other locations)
-*Plasma uses kdelibs coding style. there's a file somewhere in svn that makes vim follow this automatically. I know there was a page explaining it, so why can't I find it?  (I think its this one; [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim?view=log kde-devel.vim] [[User:Zander|Zander]] 13:46, 2 February 2008 (CET))
+*Plasma uses [[Policies/Kdelibs_Coding_Style|kdelibs coding style]]. there's a file in svn that makes vim follow this automatically: [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim?view=log kde-devel.vim]
 *if a patch is nontrivial, please get it reviewed before committing. best place to do that is http://matt.rogers.name/dashboard/
 *mailing list is panel-devel [http://mail.kde.org/mailman/listinfo/panel-devel subcribe] [http://lists.kde.org/?l=kde-panel-devel&r=1&w=2 archives]

@@ Line 3: / Line 3: @@
 *Plasma uses kdelibs coding style. there's a file somewhere in svn that makes vim follow this automatically. I know there was a page explaining it, so why can't I find it?  (I think its this one; [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/kde-devel-vim.vim?view=log kde-devel.vim] [[User:Zander|Zander]] 13:46, 2 February 2008 (CET))
 *if a patch is nontrivial, please get it reviewed before committing. best place to do that is http://matt.rogers.name/dashboard/
-*mailing list is panel-devel (iirc it's harder to find than other kde lists... what's the url?)
+*mailing list is panel-devel [http://mail.kde.org/mailman/listinfo/panel-devel subcribe] [http://lists.kde.org/?l=kde-panel-devel&r=1&w=2 archives]