From kde-core-devel Thu Jan 20 10:25:46 2011 From: "Aaron J. Seigo" Date: Thu, 20 Jan 2011 10:25:46 +0000 To: kde-core-devel Subject: Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git Message-Id: <201101200225.47643.aseigo () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=129551922220649 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2457181.9efyunkiWY" --nextPart2457181.9efyunkiWY Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Thursday, January 20, 2011, Aaron J. Seigo wrote: > On Wednesday, January 19, 2011, Alexander Neundorf wrote: > > http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for > > somebody who knows how to use git for KDE, but not for me. > > Can somebody please add a simple step-by-step howto, what I have to do > > with identity.kde.org, projects.kde.org and git.kde.org, how the git > > push/merge/branching policy is for KDE, etc. If there are existing blog >=20 > this is, at least to me, two related but separate topics: >=20 > a) how do i get myself hooked up with all the tools? > b) what is the development workflow once i have those tools? just occured to me that there is a third topic here, too: c) how to build KDE software from the new git repositories we'll need to replace the "getting started" tutorials currently on techbase= =20 with something that uses the new git stuff. it probably makes sense to make= =20 something much, much more simple this time around, even if it is less=20 comprehensive and doesn't cover every possible use case in the main tutoria= l. once kdesrc-build and the projects.kde.org xml file are able to work togeth= er=20 (and how i dream for a nice simple Qt GUI to sit on top of that :), i think= it=20 would make sense to drive people who want to build KDE software from our=20 repositories in that direction. it's simple, straight-forward and should ma= sk=20 a lot of the possible complexity with the new git infrastructure. kdesrc-bu= ild=20 is the kind of thing that people can use to get up and started within minut= es=20 with. building an individual module by "hand", important for starting to contribu= te=20 to a given module, can be another small tutorial. from there readers could = be=20 directed to the CMake documentation as well for more in depth info. the relationships between the modules (qt -> support -> libs -> runtime,=20 workspace, SC modules, extragear) could be another. still, the first "getting started building KDE software" tutorial should be= =20 kept dead simple. =2D-=20 Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks --nextPart2457181.9efyunkiWY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAk04DasACgkQ1rcusafx20NWMQCeOs9iujSpeLN9q6oc2sMZk63u SacAoJBgwk0+Gordu3oO9sCG7N60UVq0 =V4pO -----END PGP SIGNATURE----- --nextPart2457181.9efyunkiWY--