On Fri, Aug 20, 2010 at 01:37:37PM -0700, Shane Bryan wrote: > On Fri, Aug 20, 2010 at 09:56:13PM +0200, Carsten Munk wrote: > > 2010/8/20 Foster, Dawn M <[email protected]>: > > > The draft guidelines are here on this wiki page: > > > http://wiki.meego.com/Contributing_code_to_MeeGo > > > > > My proposal: > > > > Have [PATCH] projectname/pac: description of patch, as standard form > > of subject. > > > > This would allow maintainers to monitor for/flag patches for their own > > project as well as potentially being useful for Metrics. > > I'd have to disagree, and here is why. Imagine the following real life
OK, so we all know the only constant is change, right ;) > patch I received as part of a series produced from git-format-patch: > > [PATCH 05/16] Implemented dialogs for selecting Bluetooth modems > > Even with it's description falling within the recommended length for git > commit messages, this would turn into the following for it's target > project, the dialer, AKA, meego-handset-dialer: > > [PATCH 05/16] meego-handset-dialer/meego-handset-dialer: Implemented dialogs > for selecting Bluetooth modems As came up in a recent patch submission email thread, I can now see how having a project name in the subject *could* prove useful. The problem remains though, with these artifically long project names. So, I'd like to propose we allow for abbreviated/shortend names, or we find a reasonable "rule" by which MeeGo project names could be abbreviated. For example: m-h-dialer meego-handset-dialer libmtf libmeegotouch mtf-theme meegotouch-theme mtf-t-meego meegotouch-theme-meego I'm open to other ideas too, like just using dialer as the short name, but we need broader review of how this could/would play out for all the possible permutations. -- Shane... _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
