......department, ministry, or what in charge of reading code and making sure its correct code against which standard?
> Well, that's just the point, isn't it? All these tests and benchmarks are > needed simply because the code is not available. Some of the code is > presented as "shared source", but since there is no proof that the code > presented is the code compiled, it's merely an empty gesture. Whereas if > the code is open, governments can read it all, and compile their own > binary, knowing that they get exactly what they have seen. > > On 10 September 2012 10:32, <[email protected]> wrote: > >> I think all governments have risk managers who undertake risk >> evaluations >> before zeroing in on closed and non-audited source code from a >> predominantly American company and with strong ties to the government of >> the USA like you said. These solutions are tested and bench-marked at >> acceptable evaluation levels (Common Criteria, ITSEC, TCSEC, etc) >> >> I would like you to prove a simple scenario with simple terms the whole >> community understands (TCO, ALE, ARO, ROI, etc) that its not >> worthwhile.... >> >> >> > Think about how many government systems which depend on closed and >> > non-audited source code from a predominantly American company and with >> > strong ties to the government of the USA. Madness, is what it is. >> > >> > Reinier Battenberg <[email protected]> wrote: >> > >> >> >> >>this is a very wise decision from the Kenyan government. If developing >> >>nations >> >>want any control over their own ICT infrastructure & industry, this is >> >>the way >> >>to go. See Brazil, Vietnam etc. >> >> >> >> >> >> >> >> >> >>On Sunday 09 September 2012 20:47:31 Simon Vass wrote: >> >>> FYI >> >>> >> >>> >> >>> >> >>> Simon Vass >> >>> Managing Director >> >>> E-Tech Uganda Ltd >> >>> >> >>> http://www.etech.ug >> >>> Tel: +256 (0) 312260620 or (0) 312260621 >> >>> email: [email protected] >> >>> skype: e-techservicedesk >> >>> >> >>> >> >>> ----- Forwarded Message ----- >> >>> From: Evans Ikua <[email protected]> >> >>> To: FOSS certification <[email protected]> >> >>> Cc: fbt <[email protected]> >> >>> Sent: Fri, 07 Sep 2012 18:44:20 +0300 (EAT) >> >>> Subject: [Certification] Kenya Government plans to migrate systems >> to >> >>> open source software >> >>> >> >>> After a successful Software Freedom Day in Kenya last weekend, the >> >>ICT >> >>> Secretary at the Office of the President revealed that the Kenya >> >>Government >> >>> is planning to migrate its systems to free and open source software, >> >>a move >> >>> that will greatly benefit open source developers in Kenya. Please >> >>read more: >> >>> >> >> >> http://www.businessdailyafrica.com/Developers+lined+up+for+huge+gains+in+so >> >>> ftware+shift/-/1248928/1497380/-/kp7oeu/-/index.html >> >>-- >> >>rgds, >> >> >> >>Reinier Battenberg >> >>Director >> >>Mountbatten Ltd. >> >>www.mountbatten.net >> >>tel: +256 758 801749 >> >>twitter: @batje >> >>_______________________________________________ >> >>The Uganda Linux User Group: http://linux.or.ug >> >> >> >>Send messages to this mailing list by addressing e-mails to: >> >>[email protected] >> >>Mailing list archives: http://www.mail-archive.com/[email protected]/ >> >>Mailing list settings: http://kym.net/mailman/listinfo/lug >> >>To unsubscribe: http://kym.net/mailman/options/lug >> >> >> >>The Uganda LUG mailing list is generously hosted by INFOCOM: >> >>http://www.infocom.co.ug/ >> >> >> >>The above comments and data are owned by whoever posted them >> (including >> >>attachments if any). The mailing list host is not responsible for them >> >>in any way. >> > _______________________________________________ >> > The Uganda Linux User Group: http://linux.or.ug >> > >> > Send messages to this mailing list by addressing e-mails to: >> > [email protected] >> > Mailing list archives: http://www.mail-archive.com/[email protected]/ >> > Mailing list settings: http://kym.net/mailman/listinfo/lug >> > To unsubscribe: http://kym.net/mailman/options/lug >> > >> > The Uganda LUG mailing list is generously hosted by INFOCOM: >> > http://www.infocom.co.ug/ >> > >> > The above comments and data are owned by whoever posted them >> (including >> > attachments if any). The mailing list host is not responsible for them >> in >> > any way. >> >> >> _______________________________________________ >> The Uganda Linux User Group: http://linux.or.ug >> >> Send messages to this mailing list by addressing e-mails to: >> [email protected] >> Mailing list archives: http://www.mail-archive.com/[email protected]/ >> Mailing list settings: http://kym.net/mailman/listinfo/lug >> To unsubscribe: http://kym.net/mailman/options/lug >> >> The Uganda LUG mailing list is generously hosted by INFOCOM: >> http://www.infocom.co.ug/ >> >> The above comments and data are owned by whoever posted them (including >> attachments if any). The mailing list host is not responsible for them >> in >> any way. >> > _______________________________________________ > The Uganda Linux User Group: http://linux.or.ug > > Send messages to this mailing list by addressing e-mails to: > [email protected] > Mailing list archives: http://www.mail-archive.com/[email protected]/ > Mailing list settings: http://kym.net/mailman/listinfo/lug > To unsubscribe: http://kym.net/mailman/options/lug > > The Uganda LUG mailing list is generously hosted by INFOCOM: > http://www.infocom.co.ug/ > > The above comments and data are owned by whoever posted them (including > attachments if any). The mailing list host is not responsible for them in > any way. _______________________________________________ The Uganda Linux User Group: http://linux.or.ug Send messages to this mailing list by addressing e-mails to: [email protected] Mailing list archives: http://www.mail-archive.com/[email protected]/ Mailing list settings: http://kym.net/mailman/listinfo/lug To unsubscribe: http://kym.net/mailman/options/lug The Uganda LUG mailing list is generously hosted by INFOCOM: http://www.infocom.co.ug/ The above comments and data are owned by whoever posted them (including attachments if any). The mailing list host is not responsible for them in any way.
