Posts Tagged ‘Freedom’
PROJMAN #115 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . and enforce the division. If people post a development question onto -user, politely ask them to repost it onto -devel and vise versa. Subscribe yourself to both groups and encourage all primarily developers to do the same. This system provides so that no one person is stuck doing all of the support work and works so that users learn more about the program, they can help newer users with their questions.—————————————————————————– 4.2.2.2. Choose mailing list software well Please don’t make the selection of mailing list software impulsively. Please consider easy accessibility by users without a lot of technical experience
Duration : 0:1:32
PROJMAN #84 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . the patch may feel differently about the answer to these questions than you do. However, if you feel that that the answer to either of those questions is “no,” it is your responsibility to reject the change. If you fail to do this, the project will become unwieldy and unmaintainable and many ultimately fail.—————————————————————————– 3.2.3. Rejecting patches Rejecting patches is probably the most difficult and sensitive job that the maintainer of any free software project has to face. But sometimes it has to be done. I mentioned earlier (in Section 3 and in Section 3.1) that you need to try and balance your responsibility and power to make what you think are the best technical decisions with the fact that you
Duration : 0:1:42
PROJMAN #82 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . the link to the document so they can do it the “right way.”—————————————————————————– 3.2.2. Technical judgment In Open Source Development with CVS, Karl Fogel makes a convincing argument that the most important things to keep in mind when rejecting or accepting patches are: ��*�A firm knowledge of the scope of your program (that’s the “idea” I talked about in Section 2.1); ��*�The ability to recognize, facilitate, and direct “evolution” of your program so that the program can grow and change and incorporate functionality that was originally unforeseen; ��*�The necessity to avoid digressions that
Duration : 0:1:28
PROJMAN #141 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . that I’ve come across. It is written for people who already have a good knowledge of CVS. In the chapter on branching, he describes when and how to branch but gives no information on what C.V.S commands you should use to do this. This is fine (technical C.V.S H.O.W.T.O have been written) but C.V.S newbies will want to spend some time with Fogel’s reference before they will find this one very useful. Venugopalan creates checklists of things to do before, after, and around releases. It’s definitely worth a read through as most of his ideas will save tons of developer head aches over any longer period of time.—————————————————————————– Advogato Articles
Duration : 0:1:35
PROJMAN #86 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . etc.) which will definitely be accepted and some that you feel are so off base that they do not even merit further discussion. It is those that fall into the gray area between these two groups that might merit a quick forward to a mailing list. I recommend this process wholeheartedly. As the project maintainer you are worried about making the best decision for the project, for the project’s users and developers, and for yourself as a responsible project leader. Turning things over to an email list will demonstrate your own responsibility and responsive leadership as it tests and serves the interests of yoursoftware’s community.—————————————————————————– 3.2.3.2. Technical issues
Duration : 0:1:38
PROJMAN #154 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. You may also lend copies, under the same conditions stated above, and you maypublicly display copies.—————————————————————————– A.4. 3. COPYING I.N QUANTITY If you publish printed copies of the Document numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that
Duration : 0:1:40
PROJMAN #76 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . to startor good sources of inspiration:—————————————————————————– 3.1.1.1. Allow a larger group of people to have write access to your C.V.S repository and make real efforts toward rule by a committee [http://httpd.apache.org/] Apache is an example of a project that is run by small group of developers who vote on major technical issues and the admission of new members and all have write access to the main source repository. Their process is detailed [http://httpd.apache.org/ABOUT_APACHE.html] online. The [http://www.debian.org/] Debian Project is an extreme example of rule by committee. At current count, more than 700 developers have full responsibility for aspects of the project. All these
Duration : 0:2:12
PROJMAN #100 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . a group of developers takes code from a free software project and actually starts a brand new free software project with it. The most famous example of a fork was between Emacs and XEmacs. Both emacsen are based on an identical code-base but for technical, political, and philosophical reasons, development was split into two projects which now compete with each other. The short version of the fork section is, don’t do them. Forks force developers to choose one project to work with, cause nasty political divisions, and redundancy of work. Luckily, usually the threat of the fork is enough to scare the maintainer or maintainers of a project
Duration : 0:1:36
PROJMAN #87 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . are not always good justification Especially toward the beginning of your project’s life, you will find that many changes are difficult to implement, introduce new bugs, or have other technical problems. Try to see past these. Especially with added functionality, good ideas do not always come from good programmers. Technical merit is a valid reason to postpone an application of a patch but it is not always a good reason to reject a change outright. Even small changes are worth the effort of working with the developer submitting the patch to iron out bugs and incorporate the change if you think it seems like a good addition to your project. The effort on your part
Duration : 0:1:35
PROJMAN #2 Free Software Project Management
This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. [http://yukidoke.org/~mako/projects/howto/] Benjamin “Mako” Hill . guide to the non-technical aspects of free software project management and was written to be a crash course in the people skills that aren’t taught to commercial coders but that can make or break a free software project. —————————————————————————– Table of Contents 1. Introduction 1.1. Copyright Information 1.2. Disclaimer 1.3. New Versions 1.4. Credits 1.5. Feedback 1.6. Translations 2. Starting a Project 2.1. Choosing a Project 2.2. Naming your project 2.3. Licensing your Software 2.4. Choosing a Method of Version Numbering 2.5. Documentation 2.6. Other Presentation Issues 3. Maintaining a Project: Interacting with Developers 3.1. Delegating Work 3.2. Accepting and
Duration : 0:1:52