User:Chani/GettingStarted: Difference between revisions

From KDE TechBase
(awful outline, but better than nothing)
 
(links to my files)
 
(5 intermediate revisions by 2 users not shown)
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 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?
*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 [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.
*mailing list is panel-devel (iirc it's harder to find than other kde lists... what's the url?)
*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?

Latest revision as of 19:05, 4 August 2008

A quick intro for potential plasma contributors

  • Plasma uses kdelibs coding style. there's a file in svn that makes vim follow this automatically: 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 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 on aaron's blog. note that the reviewboard url and path have changed since that post; here's an up-to-date sample .reviewboardrc. if you're using git-svn, you will want the updated script, plus this script for producing compatible diffs.
  • our mailing list is plasma-devel (archives). the old mailing list was panel-devel. bugs go to a separate list, 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?
Retrieved from "https://techbase.kde.org/index.php?title=User:Chani/GettingStarted&oldid=31263"