From: Scott M. <sco...@gm...> - 2011-04-18 17:10:06
|
Breaking your hand, that sucks, wishing you a speedy recovery. Yeah, I see the point about Mantis. Codestyle: I'm not upset about the "cuddled / uncuddled elses", but my first instinct is to go fix them all, and I realize that' not what I should be spending my time doing. So I was hoping that if Mark was amicable toward keeping elses cuddled, he would simply stop uncuddling the elses. I do think that, in general, when working on an open source project, new people should attempt to abide by whatever existing style already exists, so long as that style is relatively sensible and consistent. -Scott On Mon, Apr 18, 2011 at 9:10 AM, David Thompson < tom...@us...> wrote: > Hi people. > > I have been quiet recently mostly due to work, but I also had the > misfortune a week ago to break my hand. But I have been following what's > been going on. > > So firstly, I want to say that I think it's great what momentum and > progress you have achieved on 2.0 so far. In the past we have never had much > more than two people on anything at any one time. Thanks to everyone! I just > wish I had more time to help. > > I want to respond on a couple of points. > > Regarding Mantis: I agree with Mark - use it to record long term TODOs, for > immediate work on getting 2.0 stable and fully featured the mailing list is > best. But this is a good reminder, try to prioritise and push things that > can wait onto Mantis, that way we will get 2.0 out quicker. > > Regarding codestyle: Somehow I'm honoured that you would consider that I > should decide, but you know that you can't win on that one. At some point > early in the project I did apply a style to tidy up contributions from > various people, but as new people an contributions come then things change > (Entropy requires no maintenance. -- Markoff Chaney). > > The best rule of thumb is: keep functional changes separate from > formatting/style changes. So Scott, put your pet peeves away at the moment > while the new code is written. I have seen projects where developers > religiously reformatted to their personal style on every commit, and you > "can't see the wood for the trees". > > So if you edit a file and it uses tabs then use tabs too, or if it "cuddles > elses" then do that too. But adapt on a per-file basis. That way the other > team members will better see (and hopefully appreciate more) your > contributions. > > I hope some of this makes sense (maybe I should cut down on the > painkillers...) > > Cheers > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Tsheetx-developers mailing list > Tsh...@li... > https://lists.sourceforge.net/lists/listinfo/tsheetx-developers > > |