Re: [MeeGo-dev] Using meego-dev for the Accounts SSO project
On Mon, 2011-03-28 at 15:58 -0700, Ryan Ware wrote: On 03/25/2011 12:52 AM, Rob Staudinger wrote: On Fri, 2011-03-25 at 09:10 +0200, Alberto Mardegan wrote: Hi all, I'd like to hear your comments about the possibility of moving the development team discussions from an internal (and not public) Nokia mailing list to meego-dev. I would estimate the traffic to be from 1 to 5 messages per day (with some occasional spikes, of course) and being mostly consisting of patches and review comments. I would encourage you to do patch review in bugzilla primarily, and tie in the mailing list only if there's need to. Yes, I'm aware that the contribution guidelines say that a patch needs to go onto the ML first. I'd suggest following the contribution guidelines. They are there for a reason. If we want to change the guidelines, then there's a discussion to be had. http://meego.com/about/contribution-guidelines : Please send an email to the meego-dev@meego.com mailing list, CC'ing the appropriate project maintainer, with [PATCH] as the first word in the subject line, or attach your patch to a bug report in bugzilla. Again, I'm encouraging everyone to raise patches on the mailing list (best already with bug number), and then spin off the discussions to bugzilla. So you get the wider awareness first, and everyone who's interested can subscribe to the bug to follow the micro-discussions. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Using meego-dev for the Accounts SSO project
On 03/25/2011 12:52 AM, Rob Staudinger wrote: On Fri, 2011-03-25 at 09:10 +0200, Alberto Mardegan wrote: Hi all, I'd like to hear your comments about the possibility of moving the development team discussions from an internal (and not public) Nokia mailing list to meego-dev. I would estimate the traffic to be from 1 to 5 messages per day (with some occasional spikes, of course) and being mostly consisting of patches and review comments. I would encourage you to do patch review in bugzilla primarily, and tie in the mailing list only if there's need to. Yes, I'm aware that the contribution guidelines say that a patch needs to go onto the ML first. I'd suggest following the contribution guidelines. They are there for a reason. If we want to change the guidelines, then there's a discussion to be had. Ryan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Using meego-dev for the Accounts SSO project
On 03/25/2011 12:33 AM, Michael Przybilski wrote: Since the code is in gitorious and also the bug-fixes have been done in the MeeGo bugzilla, I think it only makes sense to also have the discussions in public. That said, I'd suggest that it might be better to have this in the MeeGo-security ml instead. If the group feels that MeeGo-Security-Discussion is a better place for this, I don't have a problem with it. That said, continuing to have these discussions on an internal only mail list is problematic. It does not allow us to discuss the shortcomings and issues with the current Accounts SSO solution with the people that are developing it. I think it's pretty simple. If the relevant stakeholders want to continue having their discussions on a private mail list, their solution will become less and less relevant to MeeGo. Ryan ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Using meego-dev for the Accounts SSO project
Hi all, I'd like to hear your comments about the possibility of moving the development team discussions from an internal (and not public) Nokia mailing list to meego-dev. I would estimate the traffic to be from 1 to 5 messages per day (with some occasional spikes, of course) and being mostly consisting of patches and review comments. Reasons for moving away from the internal mailing list should be quite obvious. :-) Accounts SSO is part of MeeGo Core, yet almost nobody knows about it, and very little contributions are coming from outside of Nokia. I initially though that a project specific ML would be more appropriate (and filed BMC#14801 about that), but if people here don't mind a little extra traffic then having the development happening in this ML would be all fine to me, and could be even more beneficial to the project. You opinion about this proposal is appreciated and, in fact, needed. :-) Ciao, Alberto -- http://blog.mardy.it -- geek in un lingua international! ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Using meego-dev for the Accounts SSO project
2011/3/25 Alberto Mardegan ma...@users.sourceforge.net: Hi all, I'd like to hear your comments about the possibility of moving the development team discussions from an internal (and not public) Nokia mailing list to meego-dev. I would estimate the traffic to be from 1 to 5 messages per day (with some occasional spikes, of course) and being mostly consisting of patches and review comments. Reasons for moving away from the internal mailing list should be quite obvious. :-) Accounts SSO is part of MeeGo Core, yet almost nobody knows about it, and very little contributions are coming from outside of Nokia. I initially though that a project specific ML would be more appropriate (and filed BMC#14801 about that), but if people here don't mind a little extra traffic then having the development happening in this ML would be all fine to me, and could be even more beneficial to the project. You opinion about this proposal is appreciated and, in fact, needed. :-) Hi, One suggestion could be to use a prefix, like we in N900 try to use N900: as prefix on subject lines and then when there's sufficient traffic, move to seperate. BR Carsten Munk Ciao, Alberto -- http://blog.mardy.it -- geek in un lingua international! ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Using meego-dev for the Accounts SSO project
On Fri, 2011-03-25 at 09:10 +0200, Alberto Mardegan wrote: Hi all, I'd like to hear your comments about the possibility of moving the development team discussions from an internal (and not public) Nokia mailing list to meego-dev. I would estimate the traffic to be from 1 to 5 messages per day (with some occasional spikes, of course) and being mostly consisting of patches and review comments. I would encourage you to do patch review in bugzilla primarily, and tie in the mailing list only if there's need to. Yes, I'm aware that the contribution guidelines say that a patch needs to go onto the ML first. - Rob ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Using meego-dev for the Accounts SSO project
On 03/25/2011 09:52 AM, Rob Staudinger wrote: On Fri, 2011-03-25 at 09:10 +0200, Alberto Mardegan wrote: I would estimate the traffic to be from 1 to 5 messages per day (with some occasional spikes, of course) and being mostly consisting of patches and review comments. I would encourage you to do patch review in bugzilla primarily, and tie in the mailing list only if there's need to. Yes, I'm aware that the contribution guidelines say that a patch needs to go onto the ML first. Since our code is in gitorious.org, we generally do code reviews in gitorious.org, and we just post a URL to a short comment to the mailing list. Trivial/short patches are usually sent to the mailing list. I think it will be challenging enough to convince all the stakeholder to migrate to a different ML; I wouldn't like to also change the review process. But that said, if someone submits patches as bugzilla attachments, it's also fine to review them there. But to ensure that all team members have a chance to view the submissions, I'd rather encourage using the ML. Ciao, Alberto -- http://blog.mardy.it -- geek in un lingua international! ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Using meego-dev for the Accounts SSO project
Hi, On 25/03/11 07:10, Alberto Mardegan wrote: Hi all, I'd like to hear your comments about the possibility of moving the development team discussions from an internal (and not public) Nokia mailing list to meego-dev. Looking forward to seeing you all on here. :) I would estimate the traffic to be from 1 to 5 messages per day (with some occasional spikes, of course) and being mostly consisting of patches and review comments. I don't think that will be a problem. If it proves to become a problem, it can always be spun off onto a different list. Ciao, Alberto Best regards, -- Robin Burchell http://rburchell.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
