Launchpad itself

How to use launchpad effectively

Asked by Vivek Sharma

I have a personal project and I have hosted my code on launchpad and code.google.
As of now with lots of googling and launchpad help notes i have been able to do it fine... dont know when i will hit a wall for source code related checkin/checkouts. As i am totally new to SCMs/VCSs

now for the design documents, let say i wish to write a page describing the design, where do i write it... blueprints. Blueprints does not have a place to write... but only a small place for description. It would be great have a place like wiki (wiki.code.google.com/project) or something... Am i missing something. ps let me know

what is the use of whiteboard... do you mean this is the wiki part of the of idea/blueprint, do i write here for what i wish to share. can i attach bazaar to it, i mean will bazaar maintain the revision repository of whiteboards, or full blueprints. if yes then will i be able to change the docs offline and then push.

I liked launchpad more, but then checked google code... it is very comparable, rather googlecode looks better, its wiki is simple clean and uncluttered (i dont know why so many thinks in blueprint, may be i donot fully understand the purpose of it). Wiki is a very very Important feature, a simple wiki. And the unbeatable feature is wiki-respository, change it offline and update to main branch. its simply awesome.

Can i have something like this in launchpad. As google code is so slim of features. But they have one killer, the wiki-repo :D.

thanks in advance.
PS - i am just asking, as i am new dont know launchpad so well. So launchpad advocates ps pardon :D.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Curtis Hovey
Solved:
Last query:
Last reply:
Revision history for this message
Best Curtis Hovey (sinzui) said : 		#1

Hi Vivek.

I believe your question is about how to use blueprints.

Blueprints is a tool to organise feature specifications for a project. It is based on the early experience of Ubuntu developers where they wrote specifications in wikis, then registered them in the Ubuntu project. The Ubuntu member meets (often face to face at sprints) to discuss the blueprints. They leave notes on the whiteboard, assign people to manage the work and target it to a release.

Blueprint cannot store a detailed specification, only the description. Most projects keep their documents in a wiki. Some project write very small blueprints that fit in the description and use the whiteboard for comments. Each blueprint is linked to the other blueprints so that the application can draw the order that the feature must be implemented.

This application needs to change. Everyone agrees it (and all Launchpad) must support wiki editing of descriptions and notes. the whole specification should be stored in Launchpad. All whiteboards must be replaced with a comment board.

Revision history for this message
Vivek Sharma (sharmavivek) said : 		#2

Hmm, thanks Curtis,

i hope they implement the so required change (wiki-feature) asap. I hope also implement the ditto feature of google, where i download my wiki repository and work offline, then commit and push it. It would be a good idea to integrate the wiki along with the project main page, like a blueprint tab.

In the mean while, do you know any wiki that support repository based version control feature, like google wiki, i can download my repository and add/edit the pages.

Thanks again.

Revision history for this message
Julian Edwards (julian-edwards) said : 		#3

There is an open bug about adding some formatting controls to blueprints:
https://bugs.launchpad.net/launchpad-answers/+bug/151687
but this is not full wiki functionality.

I can only suggest you link your blueprint to a google wiki for now.

Revision history for this message
Vivek Sharma (sharmavivek) said : 		#4

Thanks Curtis Hovey, that solved my question.