| 5 Dec 2022 |
|  Lily Kelting joined the room. | 14:57:26 |
| Lily Kelting set a profile picture. | 18:15:52 |
| 19 Dec 2022 |
|  asrar joined the room. | 19:21:44 |
| 21 Dec 2022 |
|  Wasswa Samuel joined the room. | 22:50:35 |
| 27 Jan 2023 |
 julianp | https://www.openhub.net/p/_compare?project_0=Exosphere&project_1=OpenStack+Horizon
Interesting! | 18:32:39 |
| julianp | If I plug in $90K for average developer salary I get a 'value' of about $450K:
https://www.openhub.net/p/exosphere/estimated_cost
With this caveat:
- Please note that COCOMO was created to model large institutional projects, which often don't compare well with distributed open-source projects.
So it could be more!
| 18:37:00 |
| julianp | * If I plug in $90K for average developer salary I get a 'value' of about $450K:
https://www.openhub.net/p/exosphere/estimated_cost
With this caveat:
- Please note that COCOMO was created to model large institutional projects, which often don't compare well with distributed open-source projects.
| 18:37:55 |
 cmart | IMO this is an estimate of cost, which is not the same as value | 20:53:32 |
| julianp | Very good point. | 20:53:55 |
| cmart | how much did the first transistor cost | 20:54:19 |
| cmart | * e.g.: how much did the first transistor cost | 20:54:30 |
| 6 Feb 2023 |
| cmart | we're now in
https://dev.to/lucamug/elm-2022-a-year-in-review-33pp
(search it for Exosphere) | 22:50:09 |
| 8 Feb 2023 |
|  matrixbot (matrixbot) joined the room. | 12:48:44 |
|  julianpistorius_gitlab (Julian Pistorius) joined the room. | 12:48:45 |
|  bmb (Blair Bethwaite) joined the room. | 12:48:46 |
|  jrcolby_gitlab (jrcolby) joined the room. | 12:48:47 |
|  lenards (Andrew Lenards) joined the room. | 12:48:47 |
| cmart | I guess they accepted my talk proposal https://vancouver2023.openinfra.dev/a/schedule | 16:13:23 |
| cmart | 
Download image.png | 16:13:52 |
| cmart | * hey, they accepted my talk proposal https://vancouver2023.openinfra.dev/a/schedule | 16:14:06 |
| 14 Feb 2023 |
|  Nicholas Skaggs joined the room. | 20:12:44 |
| Nicholas Skaggs | Hey cmart I poked you on the scientific sig slack a bit ago, but thought my questions might better be asked here. Do you find horizon is still useful even after installing exosphere? Are both used? | 20:31:37 |
| cmart | hi balloons. short answer is yes, and yes | 20:32:16 |
| cmart | (and I didn't see your messages over there. you sent them on Slack or Matrix?) | 20:32:45 |
| Nicholas Skaggs | Also, I was curious to use try.exosphere.app. However, unless I'm misunderstanding something, I have to provide private credentials to the app. It would be nice to give an auth token with limited privileges I could later revoke or similar.. I guess I'm not sure how best to use that as a demo | 20:33:36 |
| cmart | oh we can provide 🙂 | 20:33:46 |
| Nicholas Skaggs | Ahh, I erased my message, heh, you won't see it. It was on slack | 20:33:58 |
| Nicholas Skaggs | I manage the team behind Wikimedia Cloud Services. https://horizon.wikimedia.org/. Tips hat. Nice to meet you. | 20:35:13 |
| cmart | awesome! I've been curious about WMF's use of OpenStack. been vaguely following you from a distance | 20:35:54 |
| cmart | longer answer is the two apps serve different use cases.
Exosphere is for folks who are not professional sysadmin or devops people. They need to create and interact with instances and storage, they're probably new to using cloud infrastructure, they probably don't know about software-defined networking or SSH keypairs.
Horizon is like the AWS dashboard. It exposes most of the OpenStack API features, including those that only make sense to developers and ops people. It doesn't try to make it easy to access interactive services on your instances. a lot of stuff is assemble-it-yourself. | 20:37:28 |
