| *** edmondsw has joined #openstack-tc | 00:43 | |
| *** edmondsw has quit IRC | 00:48 | |
| Jeffrey4l | TheJulia, hi i'm back, call me when you are free | 01:40 |
|---|---|---|
| *** mriedem is now known as mriedem_away | 01:45 | |
| *** ricolin has joined #openstack-tc | 02:11 | |
| *** edmondsw has joined #openstack-tc | 02:32 | |
| *** edmondsw has quit IRC | 02:36 | |
| *** spsurya_ has joined #openstack-tc | 03:32 | |
| *** edmondsw has joined #openstack-tc | 04:20 | |
| *** edmondsw has quit IRC | 04:24 | |
| *** e0ne has joined #openstack-tc | 05:16 | |
| *** e0ne has quit IRC | 05:18 | |
| *** ricolin has quit IRC | 05:52 | |
| *** ricolin has joined #openstack-tc | 05:52 | |
| *** e0ne has joined #openstack-tc | 07:27 | |
| *** jpich has joined #openstack-tc | 07:42 | |
| *** tosky has joined #openstack-tc | 08:03 | |
| *** mriedem_away has quit IRC | 08:20 | |
| *** cdent has joined #openstack-tc | 08:26 | |
| mnaser | https://www.kernel.org/doc/html/v4.10/process/management-style.html#managementstyle | 08:31 |
| mnaser | An interesting read | 08:31 |
| * cdent adds to reading list | 08:58 | |
| cmurphy | interesting document coming from the kernel community | 08:58 |
| cmurphy | "Write insulting posts with a sneer just to get into a good flame every once in a while, and you’ll feel cleansed." that sounds totally healthy~ | 08:59 |
| *** cdent has quit IRC | 10:54 | |
| *** jaypipes has joined #openstack-tc | 11:22 | |
| *** rosmaita has joined #openstack-tc | 11:53 | |
| *** mriedem has joined #openstack-tc | 12:01 | |
| *** ricolin has quit IRC | 12:03 | |
| TheJulia | Jeffrey4l: o/ | 12:05 |
| *** edmondsw has joined #openstack-tc | 12:09 | |
| *** dklyle has quit IRC | 13:14 | |
| dims | oh boy (kernel manager doc) | 13:47 |
| Jeffrey4l | TheJulia, o/ | 14:09 |
| TheJulia | o/ Jeffrey4l | 14:14 |
| TheJulia | I see you replied to my email, but I've not had a chance to get back to my email since noticing that I had a reply :\ It has been a busy week | 14:14 |
| Jeffrey4l | TheJulia got minutes? i am ok. | 14:14 |
| TheJulia | I have time! | 14:14 |
| Jeffrey4l | great | 14:15 |
| TheJulia | So as my email indicated, we're looking at the health of the projects and trying to get a feeling for current issues/challenges that the projects are facing, in order to identify if there is something we can assist or help with. I was wondering what your perception is for the current health of kolla? | 14:16 |
| Jeffrey4l | TheJulia, i though kolla is health as before. | 14:17 |
| Jeffrey4l | there are lots newbie in kolla project | 14:17 |
| Jeffrey4l | and the number of commits and review seems not bad. | 14:18 |
| Jeffrey4l | And we have implement several important feature during this cycle. | 14:19 |
| TheJulia | do you feel there is anything that is hindering or making it difficult for the kolla team? | 14:20 |
| Jeffrey4l | TheJulia, i think guess no so far :) | 14:22 |
| dims | Jeffrey4l : TheJulia : hi | 14:24 |
| TheJulia | Jeffrey4l: That is great to hear :) | 14:24 |
| TheJulia | Good morning dims! | 14:24 |
| Jeffrey4l | hi dims | 14:24 |
| dims | Jeffrey4l : have folks moved on from kolla-kubernetes? | 14:24 |
| dims | nothing left to do there i hope | 14:25 |
| Jeffrey4l | dims, kolla-k8s have been killed. ;( , at that time, only rich is working on it. and i guess him already moved to openstack-helm now. | 14:25 |
| dims | ++ Jeffrey4l | 14:26 |
| dims | Jeffrey4l : are there any new projects showing interest on depending directly on kolla/kolla-ansible | 14:30 |
| Jeffrey4l | dims, kayobe ( not sure whether you know this project ) | 14:31 |
| dims | don't think i have heard of it Jeffrey4l ... looking | 14:31 |
| *** ricolin has joined #openstack-tc | 14:32 | |
| Jeffrey4l | Deployment of containerised OpenStack to bare metal using kolla and bifrost | 14:32 |
| dims | gotcha thanks Jeffrey4l | 14:34 |
| TheJulia | Interesting | 14:35 |
| *** mugsie has quit IRC | 14:36 | |
| *** mugsie has joined #openstack-tc | 14:36 | |
| *** mugsie has quit IRC | 14:36 | |
| *** mugsie has joined #openstack-tc | 14:36 | |
| dims | Jeffrey4l : looks like kolla is coasting along, that's good news :) hopefully we can find more interest and contributors from kayobe and other projects. will there be a presence for kolla at PTG? | 14:37 |
| *** hongbin has joined #openstack-tc | 14:37 | |
| Jeffrey4l | dims, yes kolla will be there ;D | 14:38 |
| dims | perfect, let's talk more when we are there | 14:38 |
| Jeffrey4l | dims, sure | 14:38 |
| *** AlanClark has joined #openstack-tc | 14:58 | |
| dhellmann | tc-members: who's around for office hours? | 14:59 |
| *** e0ne has quit IRC | 14:59 | |
| TheJulia | o/ although I need coffeeeeeee | 14:59 |
| mnaser | o/ | 15:00 |
| *** jeremyfreudberg has joined #openstack-tc | 15:01 | |
| dhellmann | what's on everyone's mind this week? | 15:01 |
| TheJulia | I was wondering if you had any thoughts to the question I raised ?tuesday? night | 15:02 |
| TheJulia | I | 15:02 |
| AlanClark | AlanClark is listening in | 15:02 |
| TheJulia | err | 15:02 |
| dhellmann | hi, AlanClark | 15:02 |
| TheJulia | I've not had a chance to reply to the ptl that inquired yet, and some of the discussion wednesday morning seemed interesting at least | 15:03 |
| TheJulia | o/ AlanClark | 15:03 |
| dhellmann | TheJulia : I guess I missed you question, do you want to repeat it? | 15:03 |
| TheJulia | let me find the log entry because it also expressed my perception | 15:04 |
| TheJulia | btw, should we start the meeting for the office ours? | 15:04 |
| * dhellmann is also scanning the tuesday logs http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-10.log.html | 15:04 | |
| TheJulia | s/ours/hours | 15:04 |
| *** jeremyfreudberg| has joined #openstack-tc | 15:04 | |
| dims | o/ | 15:04 |
| dhellmann | I thought we decided we didn't want to use meetbot any more | 15:04 |
| TheJulia | dhellmann: http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-11.log.html | 15:05 |
| TheJulia | dhellmann: oh, okay | 15:05 |
| dhellmann | because that hurt the casualness | 15:05 |
| *** jeremyfreudberg has left #openstack-tc | 15:05 | |
| TheJulia | I missed that somewhere along the way | 15:05 |
| TheJulia | Likely when I was taking some PTO | 15:05 |
| *** jeremyfreudberg| is now known as jeremyfreud|web | 15:05 | |
| dhellmann | well, in on of my summaries I suggested that we just keep doing it but then in office hour logs it looked like others didn't want to | 15:06 |
| dhellmann | and we did discuss it in channel, though I don't remember if that was a week ago | 15:06 |
| TheJulia | I concur it does hurt casuality | 15:06 |
| * TheJulia goes and makes coffee | 15:06 | |
| dhellmann | basically I was only using the bot to get convenient log URLs and I can just paste the log file links for that | 15:06 |
| dhellmann | ah, so the question about how to raise visibility of projects | 15:07 |
| mnaser | Interestingly enough on that subject, giving my very last minute prepared talk, a lot of people assume OpenStack == VMs | 15:08 |
| dhellmann | are there specific projects we think need more visibility? | 15:09 |
| mnaser | I wouldn’t want to point out specific projects | 15:10 |
| dims | tangentially related, starting-yet-another-integration-point-for-k8s-and-openstack-work - https://github.com/kubernetes-sigs/cluster-api-provider-openstack - this one is to deploy a cluster by talking to nova etc (and then start k8s on the cluster just deployed) | 15:10 |
| dhellmann | dims : how is that different from magnum? because it starts with the kubernetes API endpoint? | 15:10 |
| mnaser | But in general pushing for more presence of other projects beyond the main big ones | 15:10 |
| dhellmann | mnaser : presence where? in events? or deployments? | 15:11 |
| mnaser | dhellmann: events, marketing speak from the foundation, superuser articles | 15:12 |
| dhellmann | hmm | 15:12 |
| dims | dhellmann : the k8s community is standardizing around this new CRD pattern for starting/maintaining clusters. eventually magnum may adopt it as well. | 15:12 |
| mnaser | As much as I’d love to give more exposure to these projects, I don’t think we have the resources or ability to do much as TC other than ask nicely. | 15:12 |
| dhellmann | dims : nice | 15:12 |
| dhellmann | I guess I'm not sure of the source of concern with visibility. The foundation staff seems to go out of their way to give project teams opportunities to speak (project updates) and write for the blog. Am I mistaken? Are there folks who want to do one of those things but don't know how? | 15:13 |
| dims | mnaser : we put people in touch with each other well (case in point openlab bootstrap). so if we do want to evangelize, we need to figure out what to evangelize | 15:14 |
| TheJulia | dhellmann: I feel like there is a huge barrier to gaining knowledge of the existence to projects from the outside of the community, and I guess I feel like providing more use case visibility might be more beneficial to projects because there are multiple was things can be bolted together | 15:17 |
| TheJulia | dhellmann: I'm not sure project updates are an avenue to catch attention of someone randomly trying to solve their problem of the week | 15:17 |
| dhellmann | our effort to produce a set of "constellations" has stalled out, would reviving that help? | 15:18 |
| dhellmann | TheJulia : sure, and the project updates I watched were all *very* boring, so I'm not sure how much anyone really watches those anyway | 15:18 |
| TheJulia | I wonder if that might be too meta... | 15:18 |
| dims | separate identities for projects TheJulia? (their own xyz.openstack.org in addition to their logo and other things) | 15:18 |
| TheJulia | dims: that is an interesting concept | 15:19 |
| dhellmann | dims : can you elaborate on why that might help? | 15:19 |
| * dhellmann feels like he's missing a lot of context for this conversation | 15:19 | |
| dims | folks tend to lump everything into one "openstack" bucket | 15:20 |
| dhellmann | "folks"? | 15:20 |
| dims | may help highlight strengths of individual projects | 15:20 |
| dims | outside of openstack dev community | 15:20 |
| dhellmann | how would anyone find xyz.openstack.org if they aren't finding docs.openstack.org/xyz? | 15:21 |
| dhellmann | what else would we need to do differently, I guess | 15:21 |
| dhellmann | I don't think it's a bad idea, I just don't think I fully understand it | 15:22 |
| TheJulia | project.o.o could just redirect to docs.openstack.org... although they wouldn't have different indexing in that case | 15:22 |
| dims | dhellmann : it's more like the style of ASF and CNCF each project has a distinct identity | 15:22 |
| dhellmann | is that what we want? | 15:23 |
| TheJulia | I think the key is to highlight strengths and use cases of each project, and make that easy to reach... so maybe in ironic's case it would be replace our main doc landing page with something WAY less dense and that doesn't dive into every detail | 15:23 |
| dims | dunno yet. thinking aloud if that would help | 15:23 |
| dhellmann | we've recently had conversations about ways to break down walls between project teams to accomplish work across the community, so I'm interested to understand how separate websites for each project intersects with that goal | 15:24 |
| TheJulia | doing something like that would lower the "omg that is a novel on a page" shock that may be pushing people away | 15:24 |
| dhellmann | TheJulia : restructuring the docs landing pages seems like it would be healthy. Did you look at Petr's proposed template? | 15:24 |
| dhellmann | let me find that link | 15:25 |
| TheJulia | I suspect it does not, but I also suspect people will only work across the community as it relates to their day job or interests | 15:25 |
| TheJulia | dhellmann: what came out of atlanta? | 15:25 |
| TheJulia | atlanta ptg | 15:25 |
| dhellmann | https://review.openstack.org/579177 | 15:25 |
| dhellmann | well, I think the point of that cross-community idea is that we've reached a point where implementing a feature requires work in more than one project at a time, so focusing on features rather than projects would let us pull together dynamic teams | 15:26 |
| dhellmann | not that we want everyone to start working on all projects | 15:26 |
| dims | good point | 15:26 |
| TheJulia | that still looks like a wall of information that context is needed to be able to parse :\ | 15:26 |
| dhellmann | I'm sure pkovar would like to have that feedback | 15:26 |
| TheJulia | oh, the template | 15:27 |
| dhellmann | I guess the question is what purpose the landing page on docs.o.o is meant to achieve | 15:27 |
| scas | i've been struggling to deal with documenting my little corner of chef, and how that should go on docs.o.o -- this seems relevant to my interests | 15:27 |
| TheJulia | The discussion I was in in atl was very much along those lines, streamlined minimized link counts, let people explore instead of trying to present it all. Sadly I've gotten resistance to simplicity. :\ | 15:28 |
| dhellmann | scas : as part of the doc migration work last year we came up with a few audience-based divisions for the documentation; have you looked at that work? | 15:28 |
| scas | dhellmann: i've done some of the division in my documentation, having used other deploy space projects as inspiration | 15:29 |
| dhellmann | TheJulia : maybe another project team would be more receptive to going first, and then the ironic team would have an example to look at? | 15:30 |
| TheJulia | Maybe part of it is in a sense, a project needs to be able to "sell" its value, if that makes sense | 15:30 |
| dhellmann | scas : ah, consistency can be good | 15:30 |
| scas | at the same time, how i document the past 2+ years of work that i've been involved in, that's something else entirely. i've taken to having a point of entry as a 'quickstart' document, a tl;dr on how to get to 'openstack' if you will | 15:30 |
| TheJulia | dhellmann: That might work, or I might be able to build consensus now, just haven't tried recently | 15:30 |
| dhellmann | TheJulia : marketing can be hard, but I think you're right it would give us some value | 15:31 |
| dhellmann | scas : that sounds like the ideal sort of documentation for a deployment project | 15:31 |
| TheJulia | If main pages were refined with more problem/solution oriented strings, that would also likely change some of the results people were encountering searching for solutions to their higher level problems. Then it would be key for projects to then convey that contirbuting is easy, that you don't need to be a hardcore code developer, etc | 15:32 |
| dhellmann | speaking of docs, did anyone have any questions about my PTI change proposal? https://review.openstack.org/580495 | 15:32 |
| TheJulia | considering that bit ironic, I'm all for going back to using tox | 15:33 |
| dhellmann | yeah, we definitely recognize that we're reverting a mistake. one difference is the specification to have a "docs" environment, instead of using venv | 15:33 |
| dhellmann | I consider that PTI change a pre-req to the python3-first goal, so I would like to approve it before the PTG | 15:34 |
| TheJulia | Now, getting ironic back to using the warning is error flag... that is another issue entirely :\ | 15:34 |
| TheJulia | i think it should be easy to pass the pti revision before the ptg | 15:35 |
| dhellmann | most of the questions seem to be a form of "didn't we just finish going the other way?" so as long as we can overcome that sentiment I think we'll be OK | 15:36 |
| dhellmann | many projects have already landed the tox.ini changes they will need | 15:36 |
| TheJulia | yeah | 15:37 |
| * EmilienM jumps late | 15:38 | |
| dhellmann | I think https://review.openstack.org/#/c/579953/ needs 1 more code review, too. It would be good if someone would doublecheck my logic against the charter rules | 15:38 |
| dhellmann | o/ EmilienM | 15:38 |
| scas | i think chef is even set up for that, without having anything published | 15:38 |
| pabelanger | +1 on 580495 | 15:38 |
| dhellmann | scas : for the docs PTI change? | 15:39 |
| pabelanger | I believe we need to keep an eye out for projects adding commands, but not a blocker | 15:39 |
| dhellmann | yeah, I'm not sure how concerned I am about having teams extend their doc build process | 15:39 |
| dhellmann | adding doc8 for example wouldn't bother me | 15:39 |
| dhellmann | that was a much bigger concern for package builds, frankly | 15:40 |
| *** e0ne has joined #openstack-tc | 15:40 | |
| scas | dhellmann: i believe so. i'm mostly eye-comparing to the proposed change and my nascent docs | 15:40 |
| dhellmann | scas : if you can run "tox -e docs" and get content in docs/build/html you should be all set | 15:41 |
| scas | once i get tox again (new machine) | 15:41 |
| pabelanger | dhellmann: mostly raise it because it was an issue at some point as I understand correctly | 15:41 |
| pabelanger | I think fungi has more history | 15:41 |
| dhellmann | I saw tonyb started setting up the election repo for upcoming elections, https://review.openstack.org/#/c/582109/ | 15:42 |
| dhellmann | pabelanger : it was more of an issue when the CI system didn't use tox, but yeah | 15:42 |
| dhellmann | the bigger issue is actually the hackery involved in installing some projects' dependencies | 15:42 |
| dhellmann | and this should help us get back to a state where we can do that correctly everywhere | 15:42 |
| scas | dhellmann: yep. 'tox -e docs' works | 15:43 |
| dhellmann | another thing we should talk about on the schedule is when we want to make the final call on goals for stein | 15:43 |
| pabelanger | yes, agree. It also should help remove some of the legacy zuul-cloner some jobs are still using | 15:43 |
| dhellmann | smcginnis_afk is taking the lead on that, is someone helping him? | 15:43 |
| dhellmann | scas : \o/ | 15:43 |
| dhellmann | pabelanger : yep | 15:43 |
| fungi | about to start another meeting, but catching up now | 15:44 |
| jroll | TheJulia: I hate that we compare everything to k8s, but something more like https://kubernetes.io/ is what you're thinking? | 15:44 |
| dhellmann | TheJulia : I'm reviewing the tracker, and I see the anti-nitpicking campaign on that list still. Do you consider that "done" for now, or do you have more work planned (so that I should keep it on the tracking list)? | 15:44 |
| jroll | TheJulia: like more.... "marketing" focused web sites for projects | 15:45 |
| dhellmann | like https://www.openstack.org/software/ ? | 15:45 |
| TheJulia | jroll: not necessarilly marketing, but less information overload | 15:45 |
| jroll | TheJulia: yeah, hence the air quotes... more like "ironic solves x, y, and z. link to getting started, link to docs, link to demo video | 15:46 |
| pabelanger | dhellmann: I also believe I've carved out a timeslot to help monitor more on the python3 changes for zuul, so if you'd like to increase your ping window, I'll be more responsive. | 15:46 |
| TheJulia | dhellmann: I think there was another thing with that I wanted to address, I'll have to find my notes, but if you don't hear from me before monday saying oherwise, it can be considered done | 15:46 |
| dhellmann | pabelanger : that's good news, thanks! | 15:46 |
| TheJulia | jroll: kind of I guess | 15:47 |
| dhellmann | TheJulia : how about if you update the wiki with a note about what else you want to do, or to remove the block? | 15:47 |
| TheJulia | dhellmann: that works! | 15:47 |
| jroll | TheJulia: ok, I guess I'll have to see your ideas on a whiteboard or something :) | 15:47 |
| TheJulia | jroll: heh, okay | 15:48 |
| * dims back reading backscroll | 15:48 | |
| fungi | the original concern with tox -e docs is that some projects had started to add random extra scripted steps to build their documentation for things they could have done as sphinx plug-ins but adding random shell commands and assumptions was "easier" | 15:48 |
| fungi | is that the history you were asking about, pabelanger? | 15:49 |
| pabelanger | fungi: yes, but moving back to tox -edocs, that is still a concern or not any more | 15:49 |
| *** zaneb has quit IRC | 15:49 | |
| dhellmann | was that a problem because those steps were in the "docs" env but we built docs using the venv env? | 15:50 |
| *** zaneb has joined #openstack-tc | 15:50 | |
| fungi | it's still a concern, but we just need to be more vigilant in reminding people it's a bad idea to cram extra arbitrary build steps in their docs env | 15:50 |
| dhellmann | ok | 15:51 |
| fungi | as far as the projectname.openstack.org idea, we _used_ to have those for all projects many years ago because the docs team only wanted manuals hosted on docs.o.o and project-controlled documentation had to go on separate sites. eventually we came to an agreement that we could publish project docs to the main docs site and set up permanent redirects from projectname.o.o to docs.o.o/developer/projectname | 15:51 |
| fungi | and eventually were able to drop those redirects once they were no longer getting used | 15:52 |
| TheJulia | fungi: ahh | 15:52 |
| TheJulia | good to know | 15:52 |
| fungi | it took many years to finally get it all consolidated | 15:52 |
| fungi | and cleaned up | 15:53 |
| scas | from a deploy project perspective, i'd prefer a breadcrumb from docs.o.o and not my own custom landing page | 15:53 |
| TheJulia | all consolidated likely helps the algorithms upvote the information because it falls into a single domain name | 15:53 |
| dhellmann | scas : is chef not listed on docs.o.o with the other projects? | 15:53 |
| scas | not yet | 15:53 |
| dhellmann | ok, let me or pkovar know if you need help with that | 15:54 |
| fungi | well, also it means if you want https-hosted docs you don't need ssl certs for every project | 15:54 |
| dhellmann | fungi : do you happen to know if the work on the sitemap.xml was ever finished? | 15:54 |
| scas | i think i just need to flip the job from build to publish, but i've not had a good solid review of what i have merged to make sure it works from an actual structural/docs.o.o point of view | 15:54 |
| fungi | and don't need to make dns changes every time you add/remove/rename a project | 15:54 |
| fungi | dhellmann: no clue | 15:55 |
| dhellmann | fungi : yes, having 1 cert seems like a good simplification in terms of admin for the infra team | 15:55 |
| * fungi apologizes, intermittent connectivity and about to go into a lengthy meeting tunnel | 15:55 | |
| dhellmann | ok, I'll see if the docs team knows | 15:55 |
| *** jeremyfreud|web has quit IRC | 15:55 | |
| dhellmann | scas : the docs team may be able to give you some advice there. pkovar made an offer for that sort of thing on the -dev list a while back, irrc | 15:56 |
| scas | dhellmann: ok. i'll consult my archives | 15:56 |
| fungi | for years i've felt that even having a separate docs.o.o site is suboptimal, but it's an artifact of the separate jurisdiction with www.o.o basically being the foundation website rather than the community site | 15:57 |
| dhellmann | hmm, yeah | 15:57 |
| fungi | for zuul, docs are hosted at https://zuul-ci.org/docs/ because the community operates that site and can publish their documentation to the same place as other project content | 15:57 |
| scas | www.o.o/docs/... might go over better for seo purposes, too. | 15:57 |
| dhellmann | perhaps if the foundation is renamed as a part of the expansion, we can make that sort of change and take over more of the www.openstack.org domain | 15:58 |
| fungi | the jurisdiction issue over www.o.o is why we have separate security.o.o and governance.o.o and releases.o.o and specs.o.o and so on rather than being able to serve them all from one vhost | 15:58 |
| dhellmann | although I'm not necessarily looking forward to reorganizing the website content again | 15:58 |
| * ttx waves | 15:58 | |
| dhellmann | o/ ttx | 15:59 |
| * dhellmann needs to find some lunch | 16:00 | |
| scas | i presume the domain openstackfoundation.org is not under influence? | 16:01 |
| dhellmann | that doesn't look like something we control | 16:01 |
| scas | yeah. it looked rather squatter-y | 16:01 |
| *** dklyle has joined #openstack-tc | 16:02 | |
| fungi | somebody in panama with hidden contact info via namecheap | 16:02 |
| scas | the general theme, i guess i'm getting at, is that most other projects with a foundation attached usually have a separate domain away from project.ext for that information | 16:03 |
| fungi | anyway, there's a lot of marketing inertia with the www.openstack.org site at the moment, so if there ever were a foundation rename i wouldn't expect any sort of hand-off to go quickly | 16:03 |
| fungi | but for comparison, https://apache.org/ is the site for the asf and https://httpd.apache.org/ is the site for the apache web server | 16:05 |
| fungi | so i don't know that what osf has is all that different (even if i find it suboptimal from a community project perspective) | 16:08 |
| *** annabelleB has joined #openstack-tc | 16:08 | |
| TheJulia | fungi: I seem to remember apache.org -> httpd.apache.org was over the time span of years | 16:08 |
| fungi | yeah, that sounds familiar | 16:09 |
| TheJulia | Including a time when I think there was a "if your looking for the webserver, click here." link. | 16:09 |
| fungi | right | 16:09 |
| dims | they do have a central location as well - https://projects.apache.org/ with pointers to all the other projects and their websites | 16:13 |
| scas | asf does look rather shiny | 16:16 |
| *** mriedem is now known as mriedem_away | 16:16 | |
| scas | bluntly, it looks like a shinier version of how openstack has grown | 16:17 |
| *** e0ne has quit IRC | 16:20 | |
| *** e0ne has joined #openstack-tc | 16:23 | |
| *** e0ne has quit IRC | 16:23 | |
| scas | if one considers 'openstack' to just be the core services, project.o.o works and makes a lot of sense from how each project is intended to be showcased. it does fall down when factoring in the deploy projects that are so unfortunately named, like chef | 16:25 |
| *** spsurya_ has quit IRC | 16:26 | |
| *** AlanClark has quit IRC | 16:26 | |
| scas | if i were coming at this from a new user perspective, i'd come away with a higher confidence level just by seeing the information exposed in a manner as asf, however it's structured | 16:31 |
| *** jpich has quit IRC | 16:39 | |
| *** e0ne has joined #openstack-tc | 16:41 | |
| *** e0ne has quit IRC | 16:43 | |
| *** ricolin has quit IRC | 16:44 | |
| jroll | oh my, guido is stepping down, will be interesting to see the evolution of python governance: https://mail.python.org/pipermail/python-committers/2018-July/005664.html | 16:55 |
| *** zaneb has quit IRC | 16:57 | |
| *** zaneb has joined #openstack-tc | 16:59 | |
| *** ricolin has joined #openstack-tc | 17:15 | |
| *** annabelleB has quit IRC | 17:32 | |
| *** rosmaita has quit IRC | 17:33 | |
| *** mriedem_away is now known as mriedem | 17:37 | |
| TheJulia | It shall be interesting | 17:42 |
| *** rosmaita has joined #openstack-tc | 17:43 | |
| TheJulia | Since... I think the whole thing about living in interesting times already applies. | 17:43 |
| *** ricolin has quit IRC | 17:51 | |
| *** harlowja has joined #openstack-tc | 18:24 | |
| *** e0ne has joined #openstack-tc | 18:42 | |
| *** e0ne_ has joined #openstack-tc | 18:47 | |
| *** e0ne has quit IRC | 18:47 | |
| *** zaneb has quit IRC | 18:50 | |
| *** zaneb has joined #openstack-tc | 18:51 | |
| *** e0ne has joined #openstack-tc | 18:51 | |
| *** e0ne_ has quit IRC | 18:52 | |
| *** e0ne has quit IRC | 18:54 | |
| *** e0ne_ has joined #openstack-tc | 18:54 | |
| *** e0ne_ has quit IRC | 18:56 | |
| *** zaneb has quit IRC | 18:57 | |
| *** zaneb has joined #openstack-tc | 18:58 | |
| *** e0ne has joined #openstack-tc | 19:12 | |
| *** e0ne has quit IRC | 19:23 | |
| openstackgerrit | Doug Hellmann proposed openstack/governance master: write up the python3-first goal https://review.openstack.org/575933 | 19:27 |
| *** e0ne has joined #openstack-tc | 19:31 | |
| *** mriedem has quit IRC | 19:32 | |
| *** e0ne_ has joined #openstack-tc | 19:34 | |
| *** e0ne has quit IRC | 19:36 | |
| *** e0ne_ has quit IRC | 19:41 | |
| *** e0ne has joined #openstack-tc | 19:55 | |
| *** e0ne has quit IRC | 19:59 | |
| *** e0ne has joined #openstack-tc | 20:03 | |
| *** zaneb has quit IRC | 20:06 | |
| *** zaneb has joined #openstack-tc | 20:06 | |
| *** e0ne has quit IRC | 20:07 | |
| *** e0ne has joined #openstack-tc | 20:13 | |
| *** e0ne has quit IRC | 20:18 | |
| fungi | it does come across at least slightly as a ragequit e-mail | 20:19 |
| *** e0ne has joined #openstack-tc | 20:21 | |
| fungi | if he'd just left out that first sentence, the entire rest of the message would have had a much different tone | 20:24 |
| *** e0ne_ has joined #openstack-tc | 20:27 | |
| *** e0ne has quit IRC | 20:28 | |
| *** e0ne_ has quit IRC | 20:31 | |
| *** e0ne has joined #openstack-tc | 20:35 | |
| *** e0ne has quit IRC | 20:42 | |
| scas | it came off to me as being somewhat crabby, somewhat exhausted | 20:44 |
| scas | i blame the bay area monoculture | 20:45 |
| *** e0ne has joined #openstack-tc | 20:48 | |
| *** e0ne has quit IRC | 20:50 | |
| *** mriedem has joined #openstack-tc | 20:55 | |
| *** e0ne has joined #openstack-tc | 21:27 | |
| *** edmondsw has quit IRC | 21:34 | |
| *** e0ne has quit IRC | 21:39 | |
| *** edmondsw has joined #openstack-tc | 21:40 | |
| *** edmondsw has quit IRC | 21:44 | |
| *** e0ne has joined #openstack-tc | 21:59 | |
| *** dklyle has quit IRC | 22:16 | |
| *** dklyle has joined #openstack-tc | 22:16 | |
| zaneb | I can't believe there are people who don't like PEP572. Have those people ever programmed in Python? | 22:31 |
| *** e0ne has quit IRC | 22:32 | |
| *** zaneb has quit IRC | 22:52 | |
| *** zaneb has joined #openstack-tc | 22:52 | |
| *** zaneb has quit IRC | 22:57 | |
| *** rosmaita has quit IRC | 22:59 | |
| *** tosky has quit IRC | 23:01 | |
| *** hongbin has quit IRC | 23:19 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!