diff options
| -rw-r--r-- | spm-slides.tex | 32 |
1 files changed, 24 insertions, 8 deletions
diff --git a/spm-slides.tex b/spm-slides.tex index 922aee8..7b3be2b 100644 --- a/spm-slides.tex +++ b/spm-slides.tex @@ -925,7 +925,15 @@ the single reviewer. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \foilhead{Technical debt} -tbd +Like financial debt. It is a debt, and you need to pay it off in the future (with interest). + +``When taking {\em short cuts} and delivering code that is not quite right for the programming task of the moment, a development team incurs Technical Debt. This debt decreases productivity. This loss of productivity is the interest of the Technical Debt.'' + +High technical debt would make the software not maintainable. + +FIXME. + +https://www.agilealliance.org/introduction-to-the-technical-debt-concept/ %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \foilhead{Be open from day one} @@ -954,10 +962,10 @@ Note: cleaning up needs extra time and decision-making. Also, you don't want al - Developer discussion forums -And your daily work is visible to the public. +Your daily work is visible to the public. Compatible with being open source. \newpage -``In the open'' does NOT mean +``In the open'' does NOT have to mean the following - allowing strangers to check code into your repository @@ -975,6 +983,8 @@ And your daily work is visible to the public. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \foilhead{Opening a formerly closed project} +Like exposing your underwear to the world. + Mechanical difficulties you may encounter: Your code depends on proprietary, platform-dependent libraries. @@ -982,7 +992,7 @@ Your code depends on proprietary, platform-dependent libraries. Confidential data (e.g., unpublishable comments, passwords or site-specific configuration information). -Solutions: open-source libraries, \underline{``top-skim''} version. +Solutions: use open-source libraries, start from \underline{``top-skim''} version. Managerial issues (1) make sure everyone in the team understand that a BIG change is coming. (2) make sure that you understand how it's going to feel from their point of view. @@ -994,7 +1004,7 @@ Managerial issues (1) make sure everyone in the team understand that a BIG chang - Lots of questions from strangers suggest inadequate documentation. Burden of external communications. -Solution: the above discomfort is perfectly normal. +Solution: Don't worry. The above discomfort is perfectly normal. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \foilhead{Announcing} @@ -1005,10 +1015,14 @@ Put the announcement on the Project Homepage. Post the announcement in the appropriate forums. One post per forum. -General: https://news.ycombinator.com/ +General forum: https://news.ycombinator.com/ https://www.reddit.com/r/ subdirectories: opensource, programming, software. Topic-specific forums: mailing lists. +https://freshcode.club/ + +http://openhub.net/ + Make sure your announcement contain keywords that would help search engines find your project. Your announcement should be short and to the point. @@ -1048,7 +1062,7 @@ Your announcement should be short and to the point. Running code provides the best foundation for success. -Without running code? It may also work. Subversion, Mozilla. But there has to be something {\bf concrete/tangible}. +Without running code? It may also work. Subversion (a design document, core developers), Mozilla. But there has to be something {\bf concrete/tangible} than just good intentions. You can announce after you made the project open-source. @@ -1060,7 +1074,9 @@ What you should expect: - A few more people in your mailing list. -Seed. From project to community. +Announcing is Seeding. + +Form exponential communications networks. From project to community. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \foilhead{Why open source?} |