Diff for "Code/FindingAndDownloading"

Not logged in - Log In / Register
Differences between revisions 3 and 20 (spanning 17 versions)
⇤ ← Revision 3 as of 2008-09-04 13:31:45 →
Size: 5567
Editor: 92-237-59-186
Comment:
← Revision 20 as of 2009-06-23 09:56:39 → ⇥
Size: 0
Editor: 202
Comment: delay in project
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
'''DRAFT: this page is a work in progress. Please [[Feedback|seek further help]] or check the [[TitleIndex|wiki index]] for a complete page on this topic.'''

||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

= Overview =

Launchpad and Bazaar give you access to thousands of branches of code. With just a few keystrokes, you can download the code from any of the projects that has code registered in Launchpad.

||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 0 0;" style="padding:0.5em;">{{attachment:code-stats.png}}||
||<style="text-align: center;">'''Launchpad Code stats'''||

So, what does it mean to have code registered in Launchpad? Well, it can be one of four things:

 * code in a Bazaar branch that's hosted directly by Launchpad
 * a Bazaar branch that's hosted elsewhere and mirrored by Launchpad
 * a Bazaar branch that's hosted elsewhere and monitored by Launchpad
 * a Subversion or CVS repository that's imported into a Bazaar branch hosted by Launchpad.
 
If all you want is to get hold of that code, you don't need to worry about its exact relationship with Launchpad because Launchpad sorts all that out for you.

= Getting code =

[[https://launchpad.net/do|GnomeDo]] is an application launcher for Gnome desktops. You can create your own branch of GnomeDo's ''trunk'' [[Projects/SeriesMilestonesReleases#Series|line of development]] with just a few keystrokes and without even having to visit Launchpad's web interface.

Once you've [[http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html#installation|got Bazaar on your system]], open a terminal and type the following:

{{{
$ bzr branch lp:do
}}}

Bazaar will now download the latest version of GnomeDo's trunk branch to your machine.

{{{
$ bzr branch lp:do
You have not informed bzr of your launchpad login. If you are attempting a
write operation and it fails, run "bzr launchpad-login YOUR_ID" and try again.
Branched 524 revision(s).
}}}

Don't worry about the login notice, as we're not yet uploading anything to Launchpad

Now you have your own local branch of the GnomeDo trunk, complete with full version control. You can commit any changes you like to that branch and, when you're ready, upload your version back to Launchpad to sit alongside the trunk and any other GnomeDo branches.

== Other branches ==

Let's visit [[[[https://code.launchpad.net/do|GnomeDo]]|GnomeDo's code overview page]. Here you can see a list of the GnomeDo-related branches that Launchpad knows about.

||<tablestyle="float:right; font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 0 0;" style="padding:0.5em;">{{attachment:code-stats.png}}||
||<style="text-align: center;">'''Branches associated with GnomeDo series'''||

Launchpad lists the branches in order of likely importance. So, the branch that the GnomeDo team have marked as their current development focus comes first - and is what you get when you use ```bzr branch lp:do```. At the time of writing, the following two branches are associated with GnomeDo's ''0.6'' and ''devel'' branches. The address you need to give Bazaar is also shown for both of these branches: ```do/0.6``` and ```do/devel```.





Here, you can see every branch of code associated with GnomeDo that Launchpad knows about.

== More than one branch for each project ==

Most projects have more than one line of development, such as

Use the first two paragraphs to summarise all the important points about this article.

Tell the reader if this is the information they need as soon as possible.

= Instructional text =

Where appropriate, use step by step instructions:

'''Step 1:''' Give concise and unambiguous instructions.

'''Step 2:''' Try not to state the obvious, unless you're writing for a novice user.

{i} '''Note:''' Highlight important information with a note.

'''Step 3:''' Use a well cropped screen shot if it will help orient the reader. Don't let the screen shot replace instructional text: not everyone can see your screen shot. Don't worry about borders or annotation for small, cropped screen shots such as this.

{{attachment:screen-shot.png}}

{i} '''Warning:''' If you're about to tell the reader to delete or otherwise change something that would be hard to restore, warn them.


== Full screen shots ==

||<tablestyle="float:right; font-size: 0.8em; width:30%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">{{attachment:proj-announce.png}}||
||<style="text-align: center;">'''Describe the screen shot here'''||

Some screen shots will be better placed to the right of your text. As they're not placed directly below the text that they support, use a border and short description.

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam sagittis. Aliquam eros dui, scelerisque id, consequat in, accumsan vitae, pede. Suspendisse neque ligula, scelerisque ac, mattis ut, aliquam quis, odio.

Proin nunc nisi, fringilla ac, congue ac, luctus eu, lacus. Maecenas ac purus. Cras felis metus, ultricies non, euismod ac, accumsan eleifend, leo. Quisque imperdiet tempus tellus.

Ut euismod, diam nec adipiscing interdum, tortor orci fringilla nisi, vel blandit erat magna at nisi. Fusce hendrerit odio non metus. Mauris nisl massa, dapibus id, feugiat quis, blandit a, quam. Integer tincidunt feugiat nunc. Curabitur iaculis egestas elit. Nam imperdiet suscipit odio.

Code/FindingAndDownloading (last edited 2009-06-26 05:52:07 by c-98-229-120-106)