 devoted to maintenance. On the contrary, most libre software projects deliver releases so frequently that it could be considered as a continuous release process. This process implies the almost continuous stabilization of the code, at the same time that it evolves. Free software projects are used to improve and modify their software at the same time that they prepare it for end users.
• Bug reports and fixes. While every proprietary software system needs expensive debugging cycles, libre software can count on the help of people external to the project, in the form of valuable bug reports, and even fixes for them.
• Reuse, evolution, and inter-fertilization of code. It is common in libre software projects the reuse of code of other libre software projects as an integral part of the system being developed. It is also common that several projects develop evolutions of the same base system, in many cases with all of them using code of the others all the time. Some of this cases can also happen in proprietary developments, but even in large companies, with many open projects, they are not common, while they are the norm in libre software projects.
• Distributed development model. Although some proprietary systems are developed by geographically distributed teams, the degree of distributed development found in libre software projects is several orders of magnitude greater. There are exceptions, but usually libre software projects are carried out by people from different countries, not working for the same company, devoting different amount of effort to the project, interacting mainly through the Internet, and in most cases (specially in large projects), the developer team have never been physically together.
Some of these factors increase the effort needed to build the software, while some others decrease it. Without analyzing in detail the impact of these (and other) factors, the estimation models in general, and COCOMO in particular, may not be directly applicable to libre software development.

Comparison with size estimations for other systems
To put the numbers shown above into context, here we offer estimations for the size of some operating systems. Note that these comparisons are always difficult, and specially when we compare with proprietary systems. As reported in [Lucovsky2000]  Most of these estimations (in fact, all of them, except for Red Hat Linux) are not detailed, and is difficult to know what they consider as a line of code. However, the estimations should be similar enough to SLOC counting methods to be suitable for comparison.
Note also that, while both Red Hat and Debian include many applications, in a lot of cases even several applications in the same category, both Microsoft and Sun operating systems are much more limited in this way. If the more usual applications used in those environments were counted together, their size would be much larger. However, it is also true that all those applications are not developed neither put together by the same team of developers, as is the case in Linux-based distributions.
From these numbers, it can be seen that Linux-based distributions in general, and Debian 3.0 in particular, are some of the largest pieces of software ever put together by a group of developers.

Conclusions and related work
In this paper, we have presented some results of our work on counting the number of SLOC of Debian 3.0. They represent the state of the Debian GNU/Linux distribution around the summer of 2002. Our estimation is that it amounted for more than 105,000,000 SLOC around that time. Using the COCOMO model, this implies a cost (using traditional, proprietary software development models) close to 3,625 million USD and effort of more than 26,800 person-years. The list of the largest packages, and an analysis by programming language used are also offered. These figures do not even include components such as OpenOffice.org, which were not in Debian 3.0 but are included in the upcoming Debian 3.1. We can also compare this count to that of other Linux-based distributions, notably Red Hat. Roughly speaking, Debian 3.0 is about twice the size of Red Hat 8.0, which was released about two months later. It is also larger than the latest Microsoft operating systems (although, as is discussed in the corresponding section, this comparison could be misleading).
There are not many detailed studies of the size of modern, complete operating systems. Of them, the work by David A. Wheeler, counting the size of Red Hat 6.2 and Red Hat 7.1 is the most comparable. Another interesting paper, with some intersection with this paper is [GodfreyTu2000], a study on the evolution over time of the Linux kernel. Some other papers, already referenced, provide total counts of some Sun and Microsoft operating systems, but they are not detailed enough, except for providing estimations for the whole of the system.
Finally, we find it important to repeat once more that we are offering only estimations. However, we believe they are accurate enough to draw some conclusions and to compare with other systems.Power cover discharging question

hey everyone, been searching the subreddit and the interwebz for a few days now and this is the only post I found close to the issue i'm having

http://www.reddit.com/r/Surface/comments/21836q/power_cover_discharged_when_just_sitting_in_bag/

So pretty much the issue I'm having is when I'm using my surface pro at night (with the power cover connected) and I put the surface into sleep OR shut it down completely (using system shut down) when I pick up the surface in the morning the power cover is completely drained.

Kind of a pain that I bought the power cover for the extra battery and every morning its completely drained...  Am I doing something wrong here?  Is there a setting somewhere?  I feel like I've wasted my money, lately I've been using the type cover as a screen protector when its in my bag and when my battery is almost dead I connect the power cover.....<issue_start><issue_comment>Title: Create documentation about git best practices
username_0: This git commit message is awesome! I just found it on the HPHI - I'd forgotten all about it! 😆 🤣 😬 

```
Replace this line with imperative summary

Replace this text with an awesome description of WHY you did this 
work, not HOW/WHAT it does. The diff attached to commit should 
describe implementation (HOW) well-enough.

Addresses Issue #

#------------------------------------------------^---------------------^
#                                              50^                   72^
# 1. Summary should be imperative (not past tense), 50 characters or
#    less, and not end with a period.
#
# 2. Description of commit should explain WHY a change was made and
#    lines should be wrapped to 72 characters.
#
# 3. Optionally, reference a ticket/issue number. If needed, 
#    uncomment and go to town.
#
# For more tips:
#    http://chris.beams.io/posts/git-commit
#    https://github.com/erlang/otp/wiki/writing-good-commit-messages#do
#
```

Need to make some documentation in the onboarding repo to encourage this!!Yoga has gone to the dogs as community dogs and their owners participated in Doga, sponsored by Studio 8 Yoga at Ritter Park Thursday, Oct. 4.
Joan St. Clair, director of Studio 8, said she wanted to give people a place to do yoga with their dogs and help benefit the local animal shelter with donations.
“A lot of people come to class at the studio because practicing at home is a challenge because of distractions with their kids or dogs,” St. Clair said.
St. Clair said Doga was a way to surrender to those distractions and let the dog be part of the practice.
St. Clair said she wanted to spark community involvement to help give donations to the Cabell-Wayne Animal Shelter as well.
Future studio 8 events and workshops can be found on their website https://www.studio8wv.com/events-workshops/.Port Sunlight Lawn Tennis Club is open to anyone who has a desire to play league, social tennis or simply improve their own game. Based by a woodland setting in Bromborough on the Wirral, the club has been established for over 100 years.
If you prefer a more social game then there’s plenty going on for you at the club. There’s weekly club sessions as well as plenty of court time for you to play your own games.
The club provides a comprehensive coaching schedule for all levels. Juniors can learn from an early age with LTA mini tennis which uses smaller courts and equipment. As they grow and develop, the club offers a range of coaching. There’s also coaching for adults. So regardless of your age, there’s help available should you want to develop your game.
Club Coach, Grant Thomas, also runs holiday camp for Children during the school holidays!
Teams in the Chester and Wirral summer leagues, the West Cheshire winter leagues as well as a club floodlit leagues during the winter evenings.
Port Sunlight Lawn Tennis Club offers you many reasons why you should join, whatever your tennis ability. Whether you want to develop your game or simply play more, there’s a membership package for you. So consider visiting the club today and take your first step toward membership.
1976-2001. The Film Literature Index Online, (1976-2001) was retired effective 12/6/2021. You can now access the FL