[chromium-dev] Re: Questions About Contributing Codes
On Mon, Dec 29, 2008 at 8:50 PM, DeArto20 wrote: > Hi. I'm new on this chromium project. Welcome... > I have some questions about joining on this project as a developer. > I wanna know how developers find the problems that should be improved > or resolved. > > - 1. Do they check bug tracker board? Sometimes. > : In this case, how can he (or she) be assigned on the issue that > he (or she) is interested in? Add a comment to the bug saying you're working on it. (A good time to do that is when you post your first patch for review; you can put the URL of the code review in the bug tracker. Or you can do it sooner, but doing it when you have at least some code shows that you're serious.) > - 2. Do they find the problem during their daily use of chrome > browser? A lot of the work at the moment is just reducing the number of webkit layout test failures. - Dan --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Questions About Contributing Codes
Hi. I'm new on this chromium project. I have some questions about joining on this project as a developer. I wanna know how developers find the problems that should be improved or resolved. - 1. Do they check bug tracker board? : In this case, how can he (or she) be assigned on the issue that he (or she) is interested in? - 2. Do they find the problem during their daily use of chrome browser? : In this case, is there no need that he (or she) should report that issue to someone or some board? And then, simply write his (or her) own code for that issue and request review (using review board) about it? Thanks for reading. Have a good day! --~--~-~--~~~---~--~~ 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: Default line ending CR LF, CR, or LF???
On Mon, Dec 29, 2008 at 8:01 PM, Daniel wrote: > > What should be used for the default line endings? DOS (CR LF), MAC > (CR) or UNIX (LF) style? > > I notice that most files seem to use UNIX (LF), but I want to make > sure that this is the expected line endings format. You're right, we should generally have Unix line endings. Brett --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Default line ending CR LF, CR, or LF???
What should be used for the default line endings? DOS (CR LF), MAC (CR) or UNIX (LF) style? I notice that most files seem to use UNIX (LF), but I want to make sure that this is the expected line endings format. Thanks, Daniel --~--~-~--~~~---~--~~ 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: bookmark menu
Darren, Sorry you feel this way - in all honesty this friction is something the UI team may struggle with from time to time, and I hope I can explain the background of the problem to your satisfaction - Chromium's UI was something we spent a very long time going over, and the bookmarks dropdown menu was something we experimented with for a large segment of that time. Our design was driven by watching people use existing browsers, and we found: - Most people don't (or very rarely) use bookmarks. - Those that do use the bookmarks bar. This is why we do not have a bookmarks menu in our primary UI - like many things, it's just not used by enough users to justify its presence. That said, there are a number of users (many on the Chromium UI team) who like the menu, and dislike the bookmarks bar, and as Ben suggested, we think that perhaps a customizable toolbar will be the right solution - it has its shortcomings (discoverability), but we think it's the right place to start. We are also very very wary of adding anything to our primary UI without a great deal of discussion, consideration and experimentation - once you add something, it's nearly impossible to remove. And now, back to my vacation - I hope yours is similarly enjoyable. ~ Glen On Tue, Dec 16, 2008 at 12:41 PM, Bizzeh wrote: > > this views do intersect with my own, however i do not feel that i was > fairly treated. i feel as if i was treated as "the kid that nobody > wants around at school" because everybody is fine as they are. what i > have tried to introduce today is a feature that is a staple part of a > browser, fast no-frills access to a users bookmarks. as this was met > with critisism from the start, i tried the harder in order to win > favour for compleating the feature. which was then met with "why > should we add it when we dont know if people want it, and it might > mess up our image", which i have taken the liberty of translating "we > dont want to be anything like the other browsers at the detrement of > our own browsers usability". > > i wasnt in any way trying to be nasty or offencive. i was simply > speaking my mind about the situation in hand that should never have > risen its head. > > the least i expected was for the feature i had taken the time to > create to be considered, rather than instantly dismissed. > > Regards, > Darren > > On 16 Dec, 01:32, "Ben Goodger (Google)" wrote: >> Thanks for taking the time to send us your thoughts. >> >> Chrome functions as a project at scale by maintaining a set of >> development principles (some of which are outlined >> here:http://dev.chromium.org/developers/contributing-code). One of these >> principles is encouraging communication with each other in a >> reasonable fashion. >> >> To be a successful member of the Chromium project, you should be >> mindful of the way we work and considerate of the principles that we >> think are important (such as communicating your ideas early, building >> consensus, backing up your arguments with data where appropriate, >> being prepared to have your ideas be challenged by your peers). Coming >> in and trying to blackmail us by saying we're losing a developer if we >> don't agree with you isn't going to work. >> >> If these values don't intersect with yours, then there may not be a >> good cultural fit for you in the Chromium project. >> >> -Ben >> >> >> >> On Mon, Dec 15, 2008 at 5:21 PM, Bizzeh wrote: >> >> > this has totally missed the issue, the issue is not about user >> > customisation, its about user experiance. >> >> > nowhere did i mention anything about customising the toolbar, and >> > nowhere did i limit it. >> >> > what i did do, was reduce the amount of time needed to navigate >> > bookmarks, and make it obvious that chrome actually has the feature. >> >> > please, i am not some stupid kid who will fall for tactics such as >> > avoiding the question, and creating unanswerable questions. >> >> > congratulations on loosing a potential developer >> >> > On 16 Dec, 01:16, "Ben Goodger (Google)" wrote: >> >> I am generally supportive of allowing users to put UI elements where >> >> they want, but I think the right context for this work is in allowing >> >> our toolbars to be customizable, as is possible in other software, >> >> rather than special casing this one particular issue. The end result >> >> for you, and others who have the same preferences is the same, but the >> >> way of getting there is much more powerful (and allows other people to >> >> create the configurations they want, too). >> >> >> -Ben >> >> >> On Mon, Dec 15, 2008 at 4:50 PM, Darren Horrocks >> >> >> wrote: >> >> > i have recently created a patch and submitted it to codereview >> >> >http://codereview.chromium.org/14441/show >> >> >> > the patch adds a menu button to the right of the address bar and the >> >> > menu >> >> > gives a menu of all the bookmarks within the bookmark manager and >> >> > allows for >> >> > a user to navigate to their bookmarks with
[chromium-dev] Re: bugtracker cleanup
Thanks, Paweł. I haven't looked at all those bugs, but I'm sure your changes were appropriate, and this kind of cleanup is very helpful! - Pam 2008/12/29 Paweł Hajdan Jr. : > Before Christmas I asked on #chromium about doing a small cleanup. Today I > reviewed unconfirmed bugs, and removed duplicates, changed Area- label to be > more specific etc. I generally followed the rule to only make quite obvious > changes. > > In case you'd like to review my changes, I attach a list of changed bugs at > the end of this message. > > Paweł > > http://code.google.com/p/chromium/issues/detail?id=1651 > http://code.google.com/p/chromium/issues/detail?id=5888 > http://code.google.com/p/chromium/issues/detail?id=333 > http://code.google.com/p/chromium/issues/detail?id=355 > http://code.google.com/p/chromium/issues/detail?id=426 > http://code.google.com/p/chromium/issues/detail?id=471 > http://code.google.com/p/chromium/issues/detail?id=3873 > http://code.google.com/p/chromium/issues/detail?id=1915 > http://code.google.com/p/chromium/issues/detail?id=3354 > http://code.google.com/p/chromium/issues/detail?id=5229 > http://code.google.com/p/chromium/issues/detail?id=4622 > http://code.google.com/p/chromium/issues/detail?id=4480 > http://code.google.com/p/chromium/issues/detail?id=496 > http://code.google.com/p/chromium/issues/detail?id=2644 > http://code.google.com/p/chromium/issues/detail?id=566 > http://code.google.com/p/chromium/issues/detail?id=684 > http://code.google.com/p/chromium/issues/detail?id=1378 > http://code.google.com/p/chromium/issues/detail?id=769 > http://code.google.com/p/chromium/issues/detail?id=848 > http://code.google.com/p/chromium/issues/detail?id=943 > http://code.google.com/p/chromium/issues/detail?id=2075 > http://code.google.com/p/chromium/issues/detail?id=2119 > http://code.google.com/p/chromium/issues/detail?id=3566 > http://code.google.com/p/chromium/issues/detail?id=3635 > http://code.google.com/p/chromium/issues/detail?id=4756 > http://code.google.com/p/chromium/issues/detail?id=4770 > http://code.google.com/p/chromium/issues/detail?id=4781 > http://code.google.com/p/chromium/issues/detail?id=4924 > http://code.google.com/p/chromium/issues/detail?id=4926 > http://code.google.com/p/chromium/issues/detail?id=4996 > http://code.google.com/p/chromium/issues/detail?id=5484 > http://code.google.com/p/chromium/issues/detail?id=5513 > http://code.google.com/p/chromium/issues/detail?id=5902 > http://code.google.com/p/chromium/issues/detail?id=5717 > http://code.google.com/p/chromium/issues/detail?id=5781 > http://code.google.com/p/chromium/issues/detail?id=5803 > http://code.google.com/p/chromium/issues/detail?id=5854 > http://code.google.com/p/chromium/issues/detail?id=5864 > http://code.google.com/p/chromium/issues/detail?id=5870 > http://code.google.com/p/chromium/issues/detail?id=5879 > http://code.google.com/p/chromium/issues/detail?id=5889 > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] bugtracker cleanup
Before Christmas I asked on #chromium about doing a small cleanup. Today I reviewed unconfirmed bugs, and removed duplicates, changed Area- label to be more specific etc. I generally followed the rule to only make quite obvious changes. In case you'd like to review my changes, I attach a list of changed bugs at the end of this message. Paweł http://code.google.com/p/chromium/issues/detail?id=1651 http://code.google.com/p/chromium/issues/detail?id=5888 http://code.google.com/p/chromium/issues/detail?id=333 http://code.google.com/p/chromium/issues/detail?id=355 http://code.google.com/p/chromium/issues/detail?id=426 http://code.google.com/p/chromium/issues/detail?id=471 http://code.google.com/p/chromium/issues/detail?id=3873 http://code.google.com/p/chromium/issues/detail?id=1915 http://code.google.com/p/chromium/issues/detail?id=3354 http://code.google.com/p/chromium/issues/detail?id=5229 http://code.google.com/p/chromium/issues/detail?id=4622 http://code.google.com/p/chromium/issues/detail?id=4480 http://code.google.com/p/chromium/issues/detail?id=496 http://code.google.com/p/chromium/issues/detail?id=2644 http://code.google.com/p/chromium/issues/detail?id=566 http://code.google.com/p/chromium/issues/detail?id=684 http://code.google.com/p/chromium/issues/detail?id=1378 http://code.google.com/p/chromium/issues/detail?id=769 http://code.google.com/p/chromium/issues/detail?id=848 http://code.google.com/p/chromium/issues/detail?id=943 http://code.google.com/p/chromium/issues/detail?id=2075 http://code.google.com/p/chromium/issues/detail?id=2119 http://code.google.com/p/chromium/issues/detail?id=3566 http://code.google.com/p/chromium/issues/detail?id=3635 http://code.google.com/p/chromium/issues/detail?id=4756 http://code.google.com/p/chromium/issues/detail?id=4770 http://code.google.com/p/chromium/issues/detail?id=4781 http://code.google.com/p/chromium/issues/detail?id=4924 http://code.google.com/p/chromium/issues/detail?id=4926 http://code.google.com/p/chromium/issues/detail?id=4996 http://code.google.com/p/chromium/issues/detail?id=5484 http://code.google.com/p/chromium/issues/detail?id=5513 http://code.google.com/p/chromium/issues/detail?id=5902 http://code.google.com/p/chromium/issues/detail?id=5717 http://code.google.com/p/chromium/issues/detail?id=5781 http://code.google.com/p/chromium/issues/detail?id=5803 http://code.google.com/p/chromium/issues/detail?id=5854 http://code.google.com/p/chromium/issues/detail?id=5864 http://code.google.com/p/chromium/issues/detail?id=5870 http://code.google.com/p/chromium/issues/detail?id=5879 http://code.google.com/p/chromium/issues/detail?id=5889 --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
