linaro-project-management team mailing list archive
-
linaro-project-management team
-
Mailing list archive
-
Message #00494
Re: Blueprints naming conventions
We should only enforce it if it brings a substantial benefit, and then
only by automation.
Every rule has a cost associated. The cost is proportional to the
number of people who has to deal with the rules.
>From a human perspective I see no need for a naming convention. You
filter on Milestone or Series to see what's interesting. Searching in
the lp search dialog is done on content, I don't know how to search on
name anyway.
1 → 20 of 45200 other pages matching "linaro-android"
Killing obsolete wiki pages is very important.
/Tony
On 26 September 2011 15:53, Fathi Boudra <fathi.boudra@xxxxxxxxxx> wrote:
> Hi,
>
> We have this wiki page about blueprints naming conventions:
> https://wiki.linaro.org/Process/Blueprints/NamingConventions
>
> Current teams practices don't follow these conventions anymore.
> Could we officially state these naming conventions as obsolete
> and kill the related wiki pages to avoid confusion?
>
> Otherwise, we need to enforce this policy and make sure that
> the blueprints writers use the same naming conventions.
>
> Opinions?
>
> Cheers,
> --
> Fathi Boudra
> Linaro Release Manager | Validation Project Manager
> Linaro.org | Open source software for ARM SoCs
>
> _______________________________________________
> Mailing list: https://launchpad.net/~linaro-project-management
> Post to : linaro-project-management@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~linaro-project-management
> More help : https://help.launchpad.net/ListHelp
>
References