[chromium-dev] Re: Meeting Notes From 2/9/2009 Now Posted!
An OWP seems an excellent thing. The thing is, there seems to be a separation between internal Google developers and External developers. For instance, we are not brought into the loop regarding some processes. I know some of you use the mailing list to bring out ideas which is awesome, and do a discussion. But many features just come out of nowhere. Would be cool to know the path of what chromium is going to become (I know stability, security, etc, etc), and our (external) voice would matter on how the development / discussion is going. More involvement into the project would be better than just being considered as a programmer only. Some projects do weekly or biweekly quick online meetings on IRC. Its productive because its like a quick weekly scrum where we discuss next release goals etc etc. I don't know how Chromium is organized or if it applies to us. -- Mohamed Mansour On Fri, Jul 10, 2009 at 12:48 AM, Brian Rakowski br...@chromium.org wrote: We stopped posting because (a) the notes seemed not to be very useful out of context and (b) removing any Google-specific info, though it was minimal, was pretty labor intensive. I think it may be more productive to try to keep some public roadmaps and tasklists updated. Ian is working on creating an OWP roadmap that will be updated weekly with the status of the main areas of work. If that works out, perhaps we can do the same for other areas of the project. It seems like that would be more helpful and also more practical. Does that seem like it would meet the needs of the external developers? I want to make sure contributors have the info they need to be productive, but I don't want to create unnecessary work. Brian On Thu, Jul 9, 2009 at 8:10 PM, Evan Stade est...@chromium.org wrote: Is it possible to continue posting these? external developers have requested it. -- Evan Stade On Wed, Feb 11, 2009 at 10:18 AM, Peter Kastingpkast...@google.com wrote: On Tue, Feb 10, 2009 at 6:19 PM, Glenn Wilson gwil...@chromium.org wrote: Meeting notes from February 9, 2009 are now posted on the Chromium developer documentation: http://sites.google.com/a/chromium.org/dev/developers/meeting-notes#02092009 Please contact me if you have any questions, and enjoy! It might be nice to post these on a blog somewhere, primarily so they can be grabbed via RSS; various Mozilla meeting notes are posted this way. PK --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Meeting Notes From 2/9/2009 Now Posted!
On Fri, Jul 10, 2009 at 4:48 AM, Mohamed Mansour m...@chromium.org wrote: An OWP seems an excellent thing. The thing is, there seems to be a separation between internal Google developers and External developers. For instance, we are not brought into the loop regarding some processes. I know some of you use the mailing list to bring out ideas which is awesome, and do a discussion. But many features just come out of nowhere. Even if you work at Google, many of the features come out of nowhere. :-) I think roadmaps could help here, but honestly I'm not sure how much it actually matters that everyone is in the loop...especially since being/keeping people in the loop uses up resources that could otherwise be spent working on new features. I actually think it's better that we move quickly to get new features out there (sometimes behind flags) and then iterate from there. Already, almost all technical discussion happens on the external mailing list or IRC. The Google Chrome team is geographically distributed, which definitely helps in more communication being done via mailing lists and thus externally. Besides meetings, I'm not really sure what other processes your talking about though. And I think roadmaps will bring 90% of the benefits to meeting minutes. Would be cool to know the path of what chromium is going to become (I know stability, security, etc, etc), and our (external) voice would matter on how the development / discussion is going. More involvement into the project would be better than just being considered as a programmer only. Most technical discussion already happens in bugs. There are definitely too many bugs flying by to keep track of all of them, which is why a roadmap might help: it could give a high level overview and then point to specific bugs for further discussion. As for being considered as a programmer: this is pretty much how open source projects work. Power is gained by being the go-to person for stuff. It just so happens that all the go-to people are at Google right now. Hopefully that'll change over time. :-) I think UI decisions are the only exception to this rule...and there are both pros and cons to that. Some projects do weekly or biweekly quick online meetings on IRC. Its productive because its like a quick weekly scrum where we discuss next release goals etc etc. I don't know how Chromium is organized or if it applies to us. I'm sure a number of developers here would be open to trying this out, but I'm not sure how useful it'd be. Can you think of a sample agenda for such a meeting? J On Fri, Jul 10, 2009 at 12:48 AM, Brian Rakowski br...@chromium.orgwrote: We stopped posting because (a) the notes seemed not to be very useful out of context and (b) removing any Google-specific info, though it was minimal, was pretty labor intensive. I think it may be more productive to try to keep some public roadmaps and tasklists updated. Ian is working on creating an OWP roadmap that will be updated weekly with the status of the main areas of work. If that works out, perhaps we can do the same for other areas of the project. It seems like that would be more helpful and also more practical. Does that seem like it would meet the needs of the external developers? I want to make sure contributors have the info they need to be productive, but I don't want to create unnecessary work. Brian On Thu, Jul 9, 2009 at 8:10 PM, Evan Stade est...@chromium.org wrote: Is it possible to continue posting these? external developers have requested it. -- Evan Stade On Wed, Feb 11, 2009 at 10:18 AM, Peter Kastingpkast...@google.com wrote: On Tue, Feb 10, 2009 at 6:19 PM, Glenn Wilson gwil...@chromium.org wrote: Meeting notes from February 9, 2009 are now posted on the Chromium developer documentation: http://sites.google.com/a/chromium.org/dev/developers/meeting-notes#02092009 Please contact me if you have any questions, and enjoy! It might be nice to post these on a blog somewhere, primarily so they can be grabbed via RSS; various Mozilla meeting notes are posted this way. PK --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Meeting Notes From 2/9/2009 Now Posted!
Is it possible to continue posting these? external developers have requested it. -- Evan Stade On Wed, Feb 11, 2009 at 10:18 AM, Peter Kastingpkast...@google.com wrote: On Tue, Feb 10, 2009 at 6:19 PM, Glenn Wilson gwil...@chromium.org wrote: Meeting notes from February 9, 2009 are now posted on the Chromium developer documentation: http://sites.google.com/a/chromium.org/dev/developers/meeting-notes#02092009 Please contact me if you have any questions, and enjoy! It might be nice to post these on a blog somewhere, primarily so they can be grabbed via RSS; various Mozilla meeting notes are posted this way. PK --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Meeting Notes From 2/9/2009 Now Posted!
We stopped posting because (a) the notes seemed not to be very useful out of context and (b) removing any Google-specific info, though it was minimal, was pretty labor intensive. I think it may be more productive to try to keep some public roadmaps and tasklists updated. Ian is working on creating an OWP roadmap that will be updated weekly with the status of the main areas of work. If that works out, perhaps we can do the same for other areas of the project. It seems like that would be more helpful and also more practical. Does that seem like it would meet the needs of the external developers? I want to make sure contributors have the info they need to be productive, but I don't want to create unnecessary work. Brian On Thu, Jul 9, 2009 at 8:10 PM, Evan Stade est...@chromium.org wrote: Is it possible to continue posting these? external developers have requested it. -- Evan Stade On Wed, Feb 11, 2009 at 10:18 AM, Peter Kastingpkast...@google.com wrote: On Tue, Feb 10, 2009 at 6:19 PM, Glenn Wilson gwil...@chromium.org wrote: Meeting notes from February 9, 2009 are now posted on the Chromium developer documentation: http://sites.google.com/a/chromium.org/dev/developers/meeting-notes#02092009 Please contact me if you have any questions, and enjoy! It might be nice to post these on a blog somewhere, primarily so they can be grabbed via RSS; various Mozilla meeting notes are posted this way. PK --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Meeting Notes From 2/9/2009 Now Posted!
On Tue, Feb 10, 2009 at 6:19 PM, Glenn Wilson gwil...@chromium.org wrote: Meeting notes from February 9, 2009 are now posted on the Chromium developer documentation: http://sites.google.com/a/chromium.org/dev/developers/meeting-notes#02092009 Please contact me if you have any questions, and enjoy! It might be nice to post these on a blog somewhere, primarily so they can be grabbed via RSS; various Mozilla meeting notes are posted this way. PK --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
