my estimate for startup in philosophy domain area: 10-50 blns$. output per year.about 2-7$ per person in world. And it is not about profit only, it can be about negative impact, about abusing of social environment for profit in short term with great lost in mid term. ISIS as an example with investment flow about 1bln per year with ancient technology ( not ancient, but 500 years old). if you have society ( it public company ) with 100k employees, then estimate per person can be based on proportion 1:1k with year salary as base. and 10mlns$ for integrated solution and maintenance does not sound expensive. Philosophy impact is less then climate change, infosec, biotechnology, energy( chemistry, physics, agriculture [not oil]), but has scale close to modern social startups, media and dream industry startups. Bigger then marketing, design innovations. Thanks to Павел Кириченко for impulse to compare with innovation in linguistics/philology domain area.

Наталья Дмитриевна Карпушина убеждала нас в том, что мы - элита. Мы то знали, что мы - "говно" ( мы - это я и те с кем я имел счастье общаться достаточно близко, чтобы без пафоса соизмерять) и редкий день знали как надо, то что должны были.

Но она нас убеждала. И не знаю как кто, но я уверен, что у меня нет никаких вариантов быть "говном". Это как бы долг - масштабом в разрыв между нулем и практически бесконечностью, потому что от такого человека, который работал с такими людьми (Сковрцов, Лазарев и многие другие)...... Ну, одним словом, как бы, нет вариантов.  А она, кстати, была не преподавателем философии ( ей тоже спасибо), она была зам декана и инженером с большой, настоящей буквы.

Спасибо вам, Наталья Дмитриевна.

ПС Ясное дело, со скептически-прагматическое точки зрения, что это является (может являться/должно являться) составляющей часть учебной методики - как потом в магистратуре нам рассказывал Фомин Николай Николаевич - важная часть процесса обучения  - это ощущение "что что-то не так".  И ощущение это у меня тогда это было в чудовищном масштабе. Но вкладывать этот заряд и говорить такие слова - это очень дорогая вещь, драгоценная. И это не только благодарность, но и контракт. Да, это контакт или контракт соединений и ценность этого соединения для меня в том, что я знаю или воспринимаю эти слова как часть передачи, передачи, которая началась давно и которая ведется через преподавание.

Вот такая вот связь между передачей, коммуникациями, словами/сигналами и вычислениями. 

fail fast! fail first !
but not with info security and not with ethics !

Recently I allowed myself to express concern that may be one team do not realize or underestimate one pain point.

It is really my bad/fail moment for last few months. I need to learn how to express  concerns without conflict in ethics/social and without risk of disturbing community.  it is especially important when you are working with interesting/sensitive/innovative things.

Sad that I'm still not good enough with potential distruptive communication after working in such great teams as GridDynamics, Comcor(akado-telecom) with high level of engineering culture which is really very sensetive to concerns about  professionalism (level of proficiency,  level of technology ownership, etc).   

"i often hold things I don't know how to use"(c) Todd Willeyhttps://flic.kr/p/crX3cb I've seen this photo on my job interview with guys from openstack's team. about five years ago. just want to save it in my memories.

I’ve found interesting project Energy Aware Scheduling (EAS) project - http://www.linaro.org/blog/core-dump/energy-aware-scheduling-eas-progress-update/

it can be useful not only for IoT and personal devices but also for "green cloud” to reduce power consumption/heat pollution

Draft of slides about CICD for OpenStack

https://drive.google.com/file/d/0B15iMp5w33p4bHFDejdLMlpfa1k/view?usp=sharing

draft of talk proposal for OpenStack summit

Proposed Presentation Title*: Data-driven release decisions for your private IaaS cloud.

Abstract:
Are you using OpenStack in production?
Do you need to manage feature list delivered in production by yourself?
It sounds like you are working on your own product which is based on OpenStack's community and maybe on some existing OpenStack's distribution. If you really want to be flexible in release management for your OpenStack production solution, then you need to develop and maintain product.
Let's assume for beginning that you are using some OpenStack's distribution and you are not planning to maintain independent version of source code.You just want to control you feature list in production, support change management process and support few development teams which are working on new features for production.
"Opensource","RM", "CI", "CD": all these words together for your own little cheese shop link1[https://www.youtube.com/watch?v=cWDdd5KKhts] link2[http://www.space.com/10459-wheel-cheese-launched-space-private-spacecraft.html].
This talk is about internal implementation of few CICD components and about what do you need to support few regular releases and few change management incidents in year.

What is the problem or use case you’re addressing in this session?
The term "production environment" means that you are using approach based on products in your business operations. And infrastructure as a service can be delivered by using solution that will be built from OpenStack's components. There is one thing that can help to integrate your business operation model and open source community model of software development. This thing is the product that should be developed and maintained. It should be compiled from open source components, but it should have own release cycle. This release cycle should be based on release cycle of open source components and should help integrate business requirements for new features and development model ( release cycle, methodology etc) of different open source projects.

What should attendees expect to learn?

This talk will be about product example that  can be built from OpenStack's projects. What do you need to support release cycle? How CICD automation can help? 

Also it can be interesting to learn about CICD automation as a product: data structure/API design session, components and api calls.

Why should this session be selected?

This session should be selected if you are interested to know what are the relations between CICD, product development and using open source technologies. How open discussion can help collaborate and integrate? Release management as final integration point. Because delivery is a process that can integrate.

There are different people, different ideas, different approaches, different experience, difference between short term strategy and midterm strategy, huge gap between long term strategy and every day routine life, gap between future and present. Open discussion in open source community can help to present different things in formal way. Formal logic, it is an integration point. Public form of discussion, it is validation method. Talk on summit should help to share experience and open discussion can help to verify problem statement and implementation approach.