| 2007-09-30 21:29:58 |
Philipp Kern |
bug |
|
|
added bug |
| 2007-09-30 22:00:42 |
Tim Penhey |
launchpad: status |
New |
Won't Fix |
|
| 2009-09-05 22:32:31 |
Tim Penhey |
launchpad-code: importance |
Undecided |
Medium |
|
| 2009-09-05 22:32:31 |
Tim Penhey |
launchpad-code: status |
Won't Fix |
Triaged |
|
| 2011-09-22 22:30:17 |
Robert Collins |
launchpad: importance |
Medium |
High |
|
| 2011-09-22 22:30:23 |
Robert Collins |
tags |
lp-code |
lp-code ui |
|
| 2011-12-14 22:11:45 |
Andrew Starr-Bochicchio |
bug |
|
|
added subscriber Andrew Starr-Bochicchio |
| 2011-12-19 09:43:35 |
Robert Collins |
summary |
Junk sounds too harsh |
Junk sounds harsh - reference to tridge's junkcode is too oblique |
|
| 2011-12-19 09:45:31 |
Robert Collins |
description |
The `junk' bit in bazaar URLs which are not assigned to any project sounds a bit too harsh IMHO. |
The `junk' bit in bazaar URLs which are not assigned to any project sounds a bit too harsh IMHO.
Analysis
========
Being able to start small and garden and improve as things get bigger is a key principle for reducing the learning curve on websites. Forcing a project registration to get started is in tension with that principle, and we will make LP easier to get to know if we do a nicer job of handling no-project-yet or not-worth-a-project code branches. |
|
| 2012-04-02 23:50:48 |
Display Name |
bug |
|
|
added subscriber Renato Silva |
| 2012-12-03 16:12:20 |
Curtis Hovey |
tags |
lp-code ui |
branches lp-code teams ui users |
|
| 2012-12-03 16:13:58 |
Curtis Hovey |
description |
The `junk' bit in bazaar URLs which are not assigned to any project sounds a bit too harsh IMHO.
Analysis
========
Being able to start small and garden and improve as things get bigger is a key principle for reducing the learning curve on websites. Forcing a project registration to get started is in tension with that principle, and we will make LP easier to get to know if we do a nicer job of handling no-project-yet or not-worth-a-project code branches. |
I want to place many small projects under my personal namespace, so that I publish the repository in my CV. The only way I've found is to place them under +junk, but *junk* is not something to put in my CV.
Being able to start small and garden and improve as things get bigger is a key principle for reducing the learning curve on websites. Forcing a project registration to get started is in tension with that principle, and we will make LP easier to get to know if we do a nicer job of handling no-project-yet or not-worth-a-project code branches.
Previous discussion concluded that we want to change the name to +personal or +personal-branches. This is not as easy as other renames because "+junk" is hard coded into many classes. |
|
