Hmm, can't we put the license in a svn property, too?
The project should be clear from the directory it is, and the copyright
should be clear from the SVN-History, if not, e.g. imports/vendor drops
from another projects, we could add a COPYRIGHT-file in these directories.
So we wouldn't need a header at all...
Or the header could be autogenerated on commit or on a checkout...
I would vote for d (further discussion), too.
>>>> -----Original Message-----
>> From: ros-dev-bounces at reactos.org [mailto:ros-dev-bounces at reactos.org]
>> On Behalf Of Royce Mitchell
>> III
>> Sent: 27. november 2005 20:02
>> To: ReactOS Development List
>> Subject: Re: [ros-dev] [Vote] Top-level source header
>>>> Casper Hornstrup wrote:
>>>> >By making project rules we can better avoid the "I'll rewrite it this
>> way
>> >because my way is better" class of changes. Without project rules, it
>> is
>> >the last one to commit that "wins".
>> >
>> >
>> I don't disagree with this, but as I stated before this is an open
>> source unpaid project, so we should only have so many rules as are
>> strictly necessary. We should take great care about the rules we create.
>> I agree, but I trust people to use their best judgement. If 90% vote for
> something which I think is crazy, who am I to say this shouldn't be how
> the project will do it?
>>> Too many rules - especially frivolous ones, and we'll drive potential
>> developers and even existing developers away.
>> I could say the same about too few rules. Remember that what one person
> does, affects the other persons on the project. I suppose I would like
> ReactOS to be somewhere on the middle of this line.
>> No rules Many rules
> <----------------------------------------------------------->
> Chaos/inconsistency order/consistency
>> E.g. having order/consistency where is helps the group function well
> and help the group create a better product. I know ReactOS is about
> having fun, but I don't think that not being able to do whatever you feel
> like with regard to the project implies no fun. Certainly being in the
> chaos/inconsistency state (we've been there) won't create a happy team.
> I remember times when ReactOS often couldn't be built or booted for weeks
> at a time. In the early days, I just spent my time elsewhere when that
> happened. ReactOS wasn't useful anyway.
>> I recently joined a 15 person team who were working on some project.
> This project was close to the no rules/chaos end of that line. Of course
> the project was more than 100% over budget and half of the team worked
> 60-70 hours/week for two months. They were of course unhappy about that,
> but they really wanted to have this product ready for their customer.
> Nobody likes to fail. For those of you who are interested in numbers,
> that is a burn-rate of approx. 700 hours/week. I'll leave it as an
> exercise to the reader to calculate their salary per week ;-) Hint:
> additional hours over 37 hours/week pays 100% extra.
>> I see similarity in the ReactOS project. I see many desperately waiting
> for that 1.0 release. Now since nobody is paid to work on ReactOS, the
> project can't go 100% over budget. We can however spend twice or more as
> many hours getting there, depending on how we choose to develop ReactOS.
> So instead of reaching 1.0 in 2010 we have to wait until 2022. I'm not
> a patient person.
>>> Furthermore, this vote seems to have started in part because you
>> complained that a header copied from another file didn't get updated
>> properly. I can only assume that means you intend to have removed parts
>> of the headers that are in excess of the agreed-upon header in the vote.
>> Well, the voting is about what the standard should be (e.g. for new
> files).
> It doesn't specify anything about what to do with the existing headers.
> They could be replaced over time for instance.
>>> >That's what comments are for.
>> >
>> >
>> As I just stated, you were complaining about comments in the header
>> about the name of the file that you felt shouldn't be there. Where do we
>> draw this line of what's an allowed comment?
>> I argumented that the contents of the FILE fields in the headers tend to
> become wrong and thus useless over time. I can point you to at least four
> new files added this week for which this is true. I can point you to
> another
> set of files where the PURPOSE and PROGRAMMER fields states "Unknown" just
> because "something should be there".
> The vote is about how the header should look like and there were three
> suggestions. We have no rules for comments so you can put anything you
> feel
> like in a comment below the header. If you put the name of the file in a
> comment in the file, then fine. I will however still argument that they
> become wrong over time.
>>> >That you or someone else don't like a change shouldn't prevent someone
>> >else from trying to make that change. Which person or persons should
>> >decide which changes shouldn't be allowed to be proposed? If you don't
>> >like what someone else proposes, then you can use your right to vote to
>> >stop that change within the project.
>> >
>> >
>> Even this is a gray area, because if someone is making changes to an
>> area nobody else wants to touch... well... maybe I don't like it, but if
>> I'm not willing to fix a perceived problem but someone else is, then how
>> much right do I have to complain.... it's like the story of the little
>> red hen: nobody wanted to help her bake the bread, but they all wanted
>> to eat it. All I'm saying is that we should try to limit our complaints
>> about other people's changes just because we don't "like" them. We're
>> never going to all agree completely on how things should be done. We
>> need to agree to disagree and only invoke this kind of policy-setting
>> when it's really important. I think at a minimum we need to more
>> carefully word the proposals for the top-level source header issue here
>> - in order to solve the problem without unnecessarily constraining
>> freedom to develop in each of our own styles.
>> He has every right. If not, who decides that he hasn't the right?
> He may not have good reasons to complain, and may just be annoying to
> other people, but that's another issue.
>> Casper
>>> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
More information about the Ros-dev
mailing list
CHAPTER VII. THE FOUR CLASSES OF SOCIETY. THE FOUR CLASSES OF SOCIETY. "After the herald had given the names of the wrestlers who were to make the first round, the fellows came in. They were dressed without any clothes to speak of, or rather they were quite undressed, with the exception of a cloth around their loins. They came in on opposite sides of the ring, and stood there about five feet apart, each man resting his hands on his knees, and glaring at the other like a wild beast. They[Pg 231] looked more like a pair of tigers than human beings, and for a moment I thought it was not at all unlike what a bull-fight in Spain might be. I turned upon her choking with anger, but her melting beauty rendered me helpless. Black woods were on our left. "Shall we turn in here?" I asked. "None of that with me," he growled. "Do you know who I am, Countess Lalage? I am Leon Lagage, Count of the Holy Roman Empire, and your husband. Incomparable woman, you cannot alter that fact. For better or worse, for richer or poorer, till death do us part!" I have in this way imperfectly indicated a methodical plan of generating a design, as far as words alone will serve, beginning with certain premises based upon a particular work to be performed, and then proceeding to consider in consecutive order the general character of the machine, mode of operation, movements and adjustments, general arrangement, strains, special arrangement, and proportions. ‘Alas! what is life, what is death, what are we, 11th January two best dresses. Commencement was as usual, with a few showers “All right,” agreed Sandy. “Dick, you and I are the ground crew. As soon as you’re ready, Mr. Whiteside, we’ll take hold!” Effects of Walpole's Administration—Formation of the new Ministry—Attitude of the Malcontents—Committee of Inquiry into Walpole's Administration—Walpole's Protectors—Ministerial Measures—Prorogation of Parliament—Disasters of the French—British Division in the Netherlands—Opening of Parliament—The German Mercenaries—Amendment of the Gin Act—George goes to Germany—Stair and De Noailles in Franconia—Stair in a Trap—Bold Resolution of King George—The Battle of Dettingen—Resignation of Stair—Retreat of the French—Negotiations for Peace—Treaty of Worms—Pelham becomes Prime Minister—The Attacks of Pitt on Carteret—Attempted Invasion of England—Its Failure—Progress of the French Arms—Frederick II. invades Bohemia—His Retirement—Resignation of Carteret—Pelham strengthens his Ministry—Death of the Emperor—Campaign in Flanders—Battle of Fontenoy—Campaign of Frederick II.—The Young Pretender's Preparations—Loss of the Elizabeth—Landing in the Hebrides—The Highland Clans join him—The First Brush—Raising of the Standard—Cope's Mistake—He turns aside at Dalwhinnie—Charles makes a Dash for Edinburgh—The March to Stirling—Right of the Dragoons—The "Canter of Coltbridge"—Edinburgh surprised by the Highlanders—Charles marching against Cope—Battle of Prestonpans—Delay in marching South—Discontent of the Highland Chiefs—The Start—Preparations in England—Apathy of the Aristocracy—Arrival of the Duke of Cumberland—Charles crosses the Border—Capture of Carlisle—The March to Derby—Resolution to retreat—"Black Friday"—The Retreat—Recapture of Carlisle—Siege of Stirling—Battle of Falkirk—Retreat to the Highlands—Cumberland's Pursuit—Gradual Collapse of the Highlanders—Battle of Culloden—Termination of the Rebellion—Cruelty of the Duke of Cumberland—Adventures of the Young Pretender—Trials and Executions—Ministerial Crisis. The next morning he was up betimes, and cooked the boys as good a breakfast as he could out of the remainder of his store and what he could get from the hospital, and then gave what was left to whoever came. The comfortable crib, which had cost the Deacon so much labor, had been pre-empted by the Surgeon for some of his weakest patients. "You two step forward one pace," he commanded. "Gentleman, I've got my six. The rest are yours." "Where are you goin'?" he said sternly. Every now and then the crowd would break into the latest rhymings of MacKinnon's poet: A large thicket, at this moment, gave the dusty foot an opportunity of doubling, and, for an instant, diverging from the straightforward course, though it availed him little, he seemed to feel the breath of his pursuer on the back of his neck; his foot sounded as if at his heels; he drew his garment closely around him, turned suddenly to the right, and, bounding from the ground, the next instant a splash was heard in the little river, and the fugitive was safe from his pursuer. HoME明日之后怎么免费刷一级纳米材料
ENTER NUMBET 0018www.atomdesign.com.cn sg6gw3r6.com.cn provocraft.com.cn zhuxing8.com.cn www.kowj.com.cn idc00.com.cn www.je2s.com.cn www.fixj.com.cn shelters.com.cn yuwenjie.com.cn