Live Blue techbase & userbase sprint
“To compile kde from trunk (soon to be kde4.1) the latest Qt4.4 snapshot must be compiled from source.”
taken from one link on ‘building from trunk’ on techbase.kde.org, aparently it needs a bit of love.
tomorrow the people from live blue ( Me, Sandro Andrade, Henrique Watt, Vito, Cibele Vasconcelos and a few more ) will unite forces and remove do a big cleanup of old information, write about new things and do more translations to pt_BR.
I will, also, add a section on the techbase for the kdesvn-build, since it’s really easier to start building kde-trunk with it.
if anybody has any comments of places on techbase and userbase that needs improvements, please, state it on the comments and I will take a look carefully.
there will be 8 persons writing documentation from 1p.m to 5:30 p.m
and probably many more to come.
10 comentários até agora
Leave a reply
I think it would be great to have “Documentation Days” like we have bug days. Getting 10 or 20 people to help out with documentation would do wonders for techbase, userbase and our other web services.
Hi, Thank you for looking at this.
I am new to KDE, and use kubuntu. A couple of weeks ago, I wanted to start helping with the bug squads, writing documentation and stuff and get more involved.
In order to do this, I wanted to run a development environment in a virtualbox. I tried to use project neon, but I am running Jaunty so this would not work for me.
I really, really tried to understand the techbase documentation getting started/build/kde4 but this is soooo complicated, I was going around in circus. I had to follow links to follow links and I got lost where I was within the process of the overall process.
I have complied a couple of programs from source, and I really did not want to give up, but it was beyond my comprehension and I gave up and deleted the virtual machine.
Is the barrier to entry to get involved in KDE too high?
Thank you for looking at this techbase article. Can it be a simple 1 page article? Run ‘this’ script and you have a working development environment.
It might also be useful to have a practical example of how to make a contribution and then submit that for review.
I’m really glad that somebody steps in to improve the techbase docu. I resently set up a new kde dev environment and found not that easy to collect the needed information. Everything needed was there on techbase, but a bit scattered. IMHO the “kdesvn-build way” should be described as the default way, and the detailed manual instructions should be presented as in-depth knowledge for advanced readers.
That’s awesome. Improving content on techbase is so very much welcome!
With regard to kdesvn-build, there are already two pages right now:
1. http://techbase.kde.org/Getting_Started/Build/KDE4/kdesvn-build
2. http://techbase.kde.org/Getting_Started/Build/kdesvn-build
I propose to merge the content of the first one into the second one (if needed at all) and then make a #REDIRECT from 1 to 2.
Thanks
Hm, I’ve just fixed it myself what I mentioned in my last post
Good, IT’s good to see some motivation to upgrade the docs =)
Keep up the good work! and thanks for making KDE better.
@Matt: I don’t think a whole lot can be improved in the getting started/build/kde4 article. It’s detailed, completed, and all the information is relevant. The main problem is that building a desktop environment the size and scope of KDE is just not trivial. People that just want to test and report bugs should be pointed out on techbase that there are excellent distros with continously updated trunk/ packages. Install one of those distro’s (in a virtual machine if you don’t want to touch your main desktop) and test away. Take chakra (http://chakra-project.org) for example. Install, enable kdemod unstable repositories, update, and voila: a recent trunk/ desktop. I also know opensuse has regulary updated trunk/ packages.
Anyway: good initiative
there’s a lot of outdated documentation out there.
I am totally new to programming in Linux or KDE. For last one week I am trying to learn and get started to contribute some fixes to KDE apps. But finding it very tough to follow the techbase tutorial. Some pages say checkout “Project Neon” and another says checkout and build from svn. And I was not able to get my settings right as there is no continuity in tutorial like step1: do this, step2: do this, each page appear to be separate from other. It will be good if starter tutorial is organized like chapter 1, 2 and so on, because starters need very basic explanation.
Well, its a good idea to make a section for building it if you don’t want to know what’s happening there, just for testing.
the main problem of doing that is that it will be really easy to breake everything while you don’t have the knowledge to fix it. so it’s mostly unlike we will do that.
@Karthik, do you have an example of pages without continuity? I could follow easily the steps on the techbase page.