Hi Dave, On 7/4/11 3:25 PM, "ext Dave Neary" <dne...@maemo.org> wrote:
>Hi, > >eric.le-r...@nokia.com wrote: >> I'm very happy to announce that we have finally released our MeeGo >> bugzilla instance code on gitorious. >> Check it out here: https://gitorious.org/meego-bugzilla > ><snip> > >> I would like to thank Stephen for the tremendous and quality work he's >> been delivering and his extremely valuable contribution to the MeeGo >> project. >> A clear direction was given and a great vision of collaborative work. >> I'm sure Shuang will take this legacy further and get contributions from >> you, developers, in order to make MeeGo bugzilla a reference in >> usability and a wonderful environment to work in. > >I just wanted to say thanks and congratulations! This is going to be >useful whenever we see Bugzilla related bugs/feature requests. Thanks for your encouragement :) Indeed, I truly believe this is a great enabler and we get actual contributions. > >> I really would like to encourage you to collaborate, submit ideas and >> patches and make Meego bugzilla really yours. > >Do you have a list of bugs which require Bugzilla modifications handy, >by any chance? This is just my personal list, https://bugs.meego.com/buglist.cgi?quicksearch=19714%2C10540%2C10251%2C3187 The most important item so far is https://bugs.meego.com/show_bug.cgi?id=3187 as it's almost mandatory to allow graceful tracking accross multiple hardware/releases Note we had a custom version but it was dismissed as it doesn't scale up in MeeGo context. I see more viability in focusing on the upstream patch, make it solid and contribute back... > >Cheers, >Dave. > >-- >Email: dne...@maemo.org >Jabber: bo...@jabber.org Best regards, Eric _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
