| fatema__ | for 201677, what are the metadata indicated ?? | 00:08 |
|---|---|---|
| *** openstack has joined #storyboard | 00:15 | |
| *** ChanServ sets mode: +o openstack | 00:15 | |
| persia | For 2001634, I think it's more about modifying the existing email notification system. I think 2001746 is a supybot plugin (but haven't been following the bot refactoring closely enough to be sure). | 00:20 |
| fatema__ | for 2001634, this one seems interesting but I would need more elaboration as I see it's very relevant to already existing stuff | 00:22 |
| persia | For 2001677, I believe it is interesting to be able to search for lots more things: figuring out what and doing each seems left as an exercise for the implementor. Top item is probably making searching for a person show all the stories related to the person (in any way), but it is likely intersting to consider searches for "creator", "commentor", "assignee", etc. | 00:22 |
| fatema__ | I think for 2001677, I need to go deeper in the database schema ? | 00:25 |
| persia | For 2001634, it is probably just changing how the subject is defined in http://git.openstack.org/cgit/openstack-infra/storyboard/tree/storyboard/plugin/email/factory.py , but there may be other threading concerns (so requires some research into common mail readers threading algorithms to see if additional header info is important) | 00:25 |
| *** lodowa has joined #storyboard | 00:26 | |
| persia | I think 2001677 involves changes to the DB schema, to the REST server, and to the webclient: it is probably one of the most comprehensive of the tasks listed. My recommendation would be to pick one (or all) of the easier ones first, as a way of getting more familiar with the codebase, workflow, etc. | 00:26 |
| fatema__ | persia, so I am expected to choose one of those bugs not all of them, right ? | 00:27 |
| persia | On the other hand, some of the easier ones require more research or discussion (e.g. I think 2001634 is about 5 lines of code and user-invisible, but others appear to think very differently about the problem) | 00:28 |
| fatema__ | how is differently ? | 00:29 |
| persia | I have no expectations of you: I can only quote diablo_rojo above suggesting picking two of the four. I would recommend against picking 2001677 as a primary target, as writing the spec for that involves lots of discussion about things like "define the metadata", etc., but I tend to be conservative about effort estimates. If you're feeling ambitious, don't let me stop you. | 00:29 |
| diablo_rojo | In the context of 2001677, bswartz meant that he wanted to be able to search for things he created- so the metadata of the task or story | 00:30 |
| persia | In the case of 2001634, I think the title of the story is a terrible idea, and that users should never configure their email address when we already know their email address (and when it changes). I think enabling that will make life harder for users because they have to update even more systems if their address changes. I think we should just silently update whenever we get a different address from the OpenID provider. | 00:30 |
| diablo_rojo | He wanted to be able to see things he made rather than just things he was assigned to. | 00:31 |
| persia | Whereas, others apparently think it is a good idea, or the story wouldn't exist. | 00:31 |
| persia | diablo_rojo: I would like that too. I also want to see things I've commented on. | 00:31 |
| diablo_rojo | persia, yeah it was a feature requested yesterday. | 00:31 |
| diablo_rojo | persia, oh yeah that would be good to search on too. | 00:32 |
| persia | diablo_rojo: Yep. I argued against it yesterday. Story was created anyway. I've commented about why I think it's a terrible idea in the story. As usual, I hope my opinions guide development, but my disagreement isn't enough to block :) | 00:32 |
| * diablo_rojo missed the argument yesterday, catching up now | 00:33 | |
| persia | Somewhere around 2:00 UTC, but I've repeated it immediately above :) | 00:35 |
| fatema__ | ok, the thing is it's 2:30 am here, I really need to go on with the discussion as I need your experience and thoughts but it's getting pretty late and I have early classes | 00:35 |
| fatema__ | so I have to go to bed | 00:35 |
| diablo_rojo | Yes I see now. So... how should users change it then? its a bit annoying to have an admin do it for each person that wants it changed. | 00:35 |
| diablo_rojo | fatema__, no worries- you can always read the channel logs to get caught up when you wake up | 00:36 |
| persia | fatema__: Best advice I can give: do't stay up very late hacking on stuff: sleep is an excellent source of productivity. | 00:36 |
| persia | diablo_rojo: We should notice when the email address we get from the identity provider changes, and update the DB. User-invisible. | 00:36 |
| fatema__ | so I need to know who will be available in about 10 hours or something complete the timeplan ! | 00:37 |
| persia | Mind you, it only works when folk log in, but a support question becomes "How do I reset my email?" "Log out, and log in again, making sure your identity provider has the right email". | 00:37 |
| persia | fatema__: I don't think anyone is going to be available in 10 hours. Do you have a link to what the timeplan needs to contain? | 00:38 |
| persia | I suspect the letter of the requirements can be met quickly, even if the right counterparties aren't present. | 00:38 |
| diablo_rojo | fatema__, I will be up for about 9 hours still ( I have a meeting I have to host at 08:00UTC | 00:38 |
| fatema__ | persia, I always try to remind myself of that but I just get too involved | 00:39 |
| fatema__ | diablo_rojo, ok I will try make sometimes to get to you within the next 9 hours | 00:39 |
| diablo_rojo | fatema__, sounds good, get some sleep :) | 00:40 |
| fatema__ | ok thank you, GN | 00:40 |
| *** fatema__ has quit IRC | 00:40 | |
| diablo_rojo | persia, I am fine with that approach. We should add info about where it can be updated in documentation or in the UI though so its a bit more obvious. I thiiink EmilienM tried updating it elsewhere but it didn't take (not sure if he logged out and in again or what all the details were exactly) Either way, its updated now cause fungi went ahead and did it manually. | 00:41 |
| persia | Yes. I think we currently never update for any reason. I think that is a bug. I just don't think adding UI is the way to fix it :) | 00:41 |
| diablo_rojo | Got it. On the same page now. | 00:42 |
| diablo_rojo | Responded to you comment with one. | 00:44 |
| persia | Actively working in a story at the same time as someone else makes me wonder if there is already a story for live updates (or notices of updates), like we have for gerrit. | 00:54 |
| persia | I know there was an implementation of that at one point but it was part of a large messy fork that nobody ever managed to figure out how to use anything from. | 00:55 |
| lodowa | Hi! I saw this project and found it interesting through outreachy and I know it's really late in the game as I found out about it yesterday, but I still want to put in an effort if I can. I setup the local enviornment and was wondering if it would still be possible for me to try do a contribution and apply or is it just too late in the game? | 00:56 |
| persia | I'm not authoritative in any way, but based on recent traffic, I don't think any final decision has been made. | 00:58 |
| diablo_rojo | lodowa, Its definitely getting close to the wire, but you can definitely try to make a contribution before then. | 00:58 |
| persia | Also, everyone is welcome to help out even aside from the internships, although perhaps with less structure and funding, which may or may not work for you (depending on your level of interest and other commitments) | 00:59 |
| diablo_rojo | +2 | 01:01 |
| lodowa | Cool, thanks. Honestly it's not a big deal, I'm here for the experience mostly and this project seemed understandable at least so far. | 01:01 |
| diablo_rojo | lodowa, thats good news :) We have plenty of work to do if you're interested. We would definitely love the help. | 01:04 |
| *** lodowa has quit IRC | 01:14 | |
| * persia imagines describing Storyboard experience as "full-stack development of a cloud-based UX-driven collaboration system used by more than 20% of the Fortune 50" | 01:15 | |
| *** lodowa_ has joined #storyboard | 01:21 | |
| *** lodowa_ has quit IRC | 01:21 | |
| *** lodowa_ has joined #storyboard | 01:21 | |
| *** Lodowa_ has joined #storyboard | 01:26 | |
| *** Lodowa_ has quit IRC | 01:35 | |
| *** jamesmcarthur has joined #storyboard | 02:15 | |
| *** lodowa has joined #storyboard | 03:13 | |
| lodowa | Hi if any of you are still here, I tried to get accustomed to the code base so far. Not trying to get spoonfed but could anyone suggest a bug/feature on the tracker that is a small scope since I'm not exactly sure how far everything fits together. | 03:15 |
| *** jamesmcarthur has quit IRC | 03:21 | |
| *** jharolds has joined #storyboard | 03:31 | |
| persia | lodowa: Are there particular parts of the stack that are more appealing to you? | 03:45 |
| persia | https://storyboard.openstack.org/#!/story/2000646 is one of my pet issues, but mostly front-end | 03:49 |
| persia | https://storyboard.openstack.org/#!/story/2000644 is slightly more complicated, and requires plumbing through several layers | 03:50 |
| persia | https://storyboard.openstack.org/#!/story/2000552 is both UI and backend, and one of our higher profile annoyances | 03:51 |
| *** jamesmcarthur has joined #storyboard | 03:54 | |
| *** udesale has joined #storyboard | 03:57 | |
| persia | http://eavesdrop.openstack.org/irclogs/%23storyboard/%23storyboard.2018-03-27.log.html#t2018-03-27T23:47:39 has some others that were recently highlighted as fairly ready to go | 03:58 |
| lodowa | Thanks a lot persia, the start is helpful! | 04:01 |
| persia | Just to check, did you already find the instructions on setting up a local storyboard environment, setting up a gerrit account, etc.? | 04:02 |
| lodowa | Yep I got that all up and running so far on my machine and got the account | 04:03 |
| persia | In that case, take a look at the tool, take a look at the issues, and try something. Feel free to fix something that isn't reported yet, if you discover it while investigating. if you have questions, folk are usually fairly responsive in this channel from around 12:00 to 22:00 UTC, although some of us might be around earlier or later. | 04:06 |
| lodowa | Yep, thanks for all the help, I'll keep poking around. | 04:08 |
| *** jharolds has quit IRC | 04:50 | |
| *** lodowa has quit IRC | 04:51 | |
| *** udesale has quit IRC | 04:58 | |
| *** udesale has joined #storyboard | 04:59 | |
| *** jtomasek has joined #storyboard | 05:43 | |
| *** vaatiesther has joined #storyboard | 05:53 | |
| *** udesale_ has joined #storyboard | 06:28 | |
| *** udesale has quit IRC | 06:30 | |
| *** udesale__ has joined #storyboard | 06:30 | |
| *** jtomasek has quit IRC | 06:32 | |
| *** udesale_ has quit IRC | 06:33 | |
| *** tosky has joined #storyboard | 07:23 | |
| SotK | persia: we had a patch which naively added a proof-of-concept for live-updating boards (which worked just by polling the API at a set interval), but we've not had anything for stories | 07:40 |
| SotK | I don't know if the thoughts we've given it are in a story or if they're just in my head, I suspect the latter | 07:40 |
| SotK | I also seem to remember various brief discussions on IRC over the years | 07:42 |
| *** udesale__ is now known as udesale | 07:43 | |
| persia | I also remember IRC discussions, and some in-person discussions. I don't remember the patch, but that isn't the worst way to do it. I do remember talk about websockets being raised multiple times over the years, but don't think that came to anything. | 07:47 |
| SotK | the idea was to use the event stream implementation we already have (used by the notification system) to allow subscription to certain items over a websocket, and use that to notify the UI of updates (and the UI could use that information to update its view or it could simply notify the user of new things) | 07:48 |
| SotK | but yeah, nobody has had time to implement that | 07:48 |
| SotK | https://review.openstack.org/#/c/275193/ is the PoC for boards | 07:49 |
| SotK | we'd probably need to fallback to an implementation like that for things which don't support websockets | 07:50 |
| * SotK goes to wait for a bus | 07:51 | |
| *** udesale has quit IRC | 08:58 | |
| *** udesale has joined #storyboard | 09:05 | |
| *** dtantsur|afk is now known as dtantsur | 09:46 | |
| *** fatema__ has joined #storyboard | 09:51 | |
| *** fatema__ has quit IRC | 10:03 | |
| *** vaatiesther has quit IRC | 10:19 | |
| *** vaatiesther has joined #storyboard | 10:19 | |
| *** udesale_ has joined #storyboard | 10:46 | |
| *** udesale has quit IRC | 10:49 | |
| *** udesale_ has quit IRC | 10:52 | |
| *** jtomasek has joined #storyboard | 11:10 | |
| *** jtomasek has quit IRC | 11:28 | |
| *** dtantsur is now known as dtantsur|brb | 11:31 | |
| *** udesale has joined #storyboard | 12:02 | |
| *** jamesmcarthur has quit IRC | 12:52 | |
| *** jamesmcarthur has joined #storyboard | 12:52 | |
| *** jamesmcarthur has quit IRC | 13:07 | |
| *** jamesmcarthur has joined #storyboard | 13:08 | |
| *** jamesmcarthur has quit IRC | 13:12 | |
| *** dtantsur|brb is now known as dtantsur | 13:15 | |
| *** fatema__ has joined #storyboard | 13:21 | |
| *** jamesmcarthur has joined #storyboard | 13:28 | |
| fatema__ | Hi, I would like to discuss https://storyboard.openstack.org/#!/story/2001677 to break it into smaller tasks | 13:28 |
| *** udesale has quit IRC | 13:32 | |
| persia | fatema__: Some that come to my mind are "creator", "commentor", "assignee" as ways to search for people. | 13:33 |
| fatema__ | first of all it'll be done in the storyboard repo right ? | 13:33 |
| persia | (LP also allows one to search by an "is subscribed to by" filter, but I don't know if we need that) | 13:33 |
| persia | I don't think so. I think there's a lot of storyboard repo work to extend the API, but also some storyboard-webclient work to expose the interface. | 13:34 |
| fatema__ | persia, so it will be in the puppet repo ? | 13:35 |
| persia | I don't think it requires any changes to puppet-storyboard. | 13:35 |
| fatema__ | And of course the webclient for the front and the front end (Actually this is the first subtask of the project) | 13:36 |
| persia | It probably would benefit from some changes to python-storyboardclient as well, to expose the richer search features there. | 13:36 |
| SotK | browsing for stories by comment author will need some work in the storyboard repo, but the browse endpoint for stories already supports filtering by creator, assignee, and subscribers | 13:36 |
| fatema__ | aha I didn't work with that repo yet persia | 13:37 |
| persia | SotK: Ah, so bswartz might be satisfied with more documentation? | 13:37 |
| SotK | I suspect he will need more webclient functionality to be satisfied | 13:38 |
| SotK | I also would like such functionality | 13:38 |
| persia | Trying today, I can definitely add a person to the filter criteria, but it seems to always be assignee. I'm not sure how to add creator or subscriber. | 13:38 |
| fatema__ | SotK, I am working on the time plan and we were finding a bug with 3 months timespan to solve, test and document | 13:39 |
| persia | Oh, right, now I get it: the API has those features, but not the UI. The API only needs to be extended to support "commentor"/"editor", or whatever. | 13:39 |
| SotK | persia: correct | 13:40 |
| fatema__ | so it has the ui as well | 13:40 |
| SotK | I can do https://storyboard.openstack.org/api/v1/stories?creator_id=935 to see stories I created, but there is no way to reproduce that in the webclient | 13:40 |
| SotK | to do so will require modification of how the criteria stuff works in the webclient | 13:41 |
| fatema__ | So SotK is there any particular bug that would fit that time | 13:41 |
| fatema__ | I guess this all doesn't oppose that feature as a project idea | 13:42 |
| persia | fatema__: I think picking two from diablo_rojo's list is probably a good place to start. You won't be penalised for doing extra work. You can pick three if two seems too simple. | 13:43 |
| fatema__ | it will be expanding the search feature to include search by creator in the ui, search by commentors | 13:43 |
| persia | I think 2001677 is well-agreed as being worth doing, reasonably well understood, and unlikely to cause much contention (although the underlying work may require some plumbing). | 13:44 |
| SotK | I agree (though I disagree with the proposed syntax in that story) | 13:45 |
| fatema__ | I won't be penalized for not completing the tasks in the timeplan ? | 13:46 |
| fatema__ | SotK, what syntax ? | 13:46 |
| SotK | the story suggests typing something like "owner:self" or "creator=bswartz" to add such a filter in the search API | 13:47 |
| SotK | s/API/UI/ | 13:47 |
| fatema__ | persia, the thing that lots of work would seem simple but as you mentioned it might have underlying work that I am not expecting, that's why I am consulting you ^^ | 13:48 |
| *** vaatiesther has quit IRC | 13:48 | |
| fatema__ | SotK, so it wouldn't need ui modification | 13:48 |
| persia | I think the user should just type a name, and have different icons for the different object types (like project vs. project-group vs tag today) | 13:49 |
| SotK | persia: that matches my opinion | 13:49 |
| *** vaatiesther has joined #storyboard | 13:49 | |
| SotK | quite how to represent "creator" differently from "assignee" with fontawesome icons is something I haven't found a good idea for yet | 13:50 |
| persia | fatema__: I mean you won't be penalised for doing more tasks than you put in the timeplan, so be conservative about the timeplan (including a smaller number of tasks than the most you think you can do) | 13:50 |
| fatema__ | persia, I totally agree with you about this | 13:51 |
| SotK | fatema__: it would require some modification of the javascript codebase, and probably some html/css, but no redesign of the UI (whereas I think the suggestion of something like "owner:self" would require redesign of the UI to be nice) | 13:51 |
| fatema__ | persia, so you would recommend I include 2001677 in the timeplan and the other tasks we would work on them as we would have time as well (sequentially or in parallel ?) | 13:53 |
| fatema__ | SotK, I agree minor changes for the UI, maybe some fontawesome icons as I'd like to be more concentrated on the development more than the design | 13:54 |
| *** jamesmcarthur has quit IRC | 13:54 | |
| persia | fatema__: If 2001677 interests you, I'd recommend including that, and one other from diablo_rojo's list. I suspect you could probably complete more in 3 months, but it is better to estimate being less productive than more productive when preparing formal plans. | 13:54 |
| dtantsur | hi all! do you have plans to allow human-readable names (e.g. for projects) in URLs? | 13:54 |
| *** jamesmcarthur has joined #storyboard | 13:55 | |
| dtantsur | like, remembering (or guessing) 'ironic-inspector' for the ironic-inspector project is easier than 944.. | 13:55 |
| persia | dtantsur: https://review.openstack.org/#/c/548244/ | 13:55 |
| SotK | dtantsur: https://review.openstack.org/#/c/548244/ :) | 13:55 |
| dtantsur | w000t! | 13:55 |
| fatema__ | persia, ok I am interested in https://storyboard.openstack.org/#!/story/2001476 but had no experience with bots before | 13:56 |
| fatema__ | but I'd like to make sure that we're on the same page: | 13:59 |
| *** jamesmcarthur has quit IRC | 13:59 | |
| persia | fatema__: Do you want to learn about IRC bots? if so, that seems a reasonable pairing. If not, then maybe the email threading or user email preference stories might be good. | 14:00 |
| persia | (I think both email stories are considerably smaller than either the search story or the IRC bot story) | 14:01 |
| fatema__ | for 2001766, make search by creator available in the api ui , add search by commentor | 14:01 |
| fatema__ | is there any other feature in the search | 14:01 |
| fatema__ | persia, I didn't understand the threading mail , what is MUA ? | 14:02 |
| persia | Mail User Agent | 14:02 |
| persia | The software a user uses to read email | 14:02 |
| persia | So maybe not that one then :) | 14:03 |
| persia | so maybe 2001677 and 2001634 ? | 14:03 |
| fatema__ | I'm not familiar with it but if we can break it into smaller understandable tasks. I would not disagree, persia | 14:04 |
| persia | Oh, sorry. I got the numbers confused. | 14:05 |
| *** udesale has joined #storyboard | 14:05 | |
| persia | I *meant* 2001677 and 2001746. | 14:05 |
| *** udesale has quit IRC | 14:05 | |
| persia | (being better searching for people and being able to change email address) | 14:05 |
| fatema__ | 2001677 is the search task right ? | 14:05 |
| *** udesale has joined #storyboard | 14:05 | |
| * persia double-checks | 14:05 | |
| persia | Yep. | 14:06 |
| fatema__ | we agreed on the search features as a total, right ? | 14:06 |
| persia | You can do that as well, if you like. | 14:06 |
| persia | ('remember that I'm not authoritative when it comes to your intern application: I just spend lots of time on this channel and have opinions) | 14:07 |
| * SotK notes that https://storyboard.openstack.org/#!/story/2001677 is a subset of https://storyboard.openstack.org/#!/story/2000913 if you want more search-related tasks | 14:07 | |
| fatema__ | It's nice to have more insightful and experienced opinion | 14:08 |
| SotK | I agree that 2001677 and 2001746 seem like a good choice | 14:08 |
| fatema__ | SotK, 200913 is more detailed, I like it | 14:09 |
| persia | So maybe 2001677 and 2000913 then? | 14:11 |
| fatema__ | but I don't see it possible without UI changes | 14:11 |
| SotK | the functionality described in 2000913 will require both more API work and more UI work than 2001677, yeah | 14:11 |
| persia | I think resolution requires both UI and API changes, especially if you get into some of the other search-related stories. | 14:11 |
| fatema__ | ok it's 2000913 as 2001677 is subset of it as well | 14:13 |
| persia | That seems a sensibly-sized chunk. Large enough to be interesting, but small enough to be achieveable. | 14:16 |
| SotK | indeed | 14:16 |
| SotK | I would recommend starting with 2001677 and then expanding into the more complex functionality described in 2000913 | 14:17 |
| fatema__ | SotK, so I shall add 2001677 features to get more familiar with the environment I agree | 14:19 |
| fatema__ | SotK, so as a mentor how detailed do you need the timeplan | 14:19 |
| fatema__ | ? | 14:19 |
| fatema__ | sorry but I need your response ASAP to finish the application as I have a midterm tomorrow ^^ | 14:28 |
| *** jamesmcarthur has joined #storyboard | 14:31 | |
| SotK | sorry, personally I don't need anything super detailed, just a rough outline is fine by me | 14:32 |
| SotK | its worth asking diablo_rojo too :) | 14:32 |
| SotK | also good luck with your midterm! | 14:34 |
| fatema__ | ok when is diablo_rojo avialable ? | 14:35 |
| fatema__ | as the deadline is in couple of hours xD | 14:35 |
| fatema__ | SotK, thanks ^^ | 14:35 |
| SotK | normally later on in the day UTC-wise, if she doesn't show up in time then just assume she agrees with me I guess | 14:37 |
| fatema__ | ok | 14:37 |
| fatema__ | it's a three months so you'd need estimation for each feature or maybe update for each 2 weeks SotK | 14:38 |
| fatema__ | another thing, I shall take in consideration the final exams period | 14:39 |
| fatema__ | and one last thing I need your review of the plan :D | 14:42 |
| *** vaatiesther has quit IRC | 14:46 | |
| *** vaatiesther has joined #storyboard | 14:48 | |
| SotK | fatema__: feel free to link it to me in a PM or email it to me at adamcoldrick@hotmail.com if you prefer | 14:50 |
| *** udesale has quit IRC | 14:50 | |
| fatema__ | SotK, sure once I'm done with it xD | 14:53 |
| SotK | of course :) | 14:53 |
| *** vaatiesther has quit IRC | 14:54 | |
| *** fatema__ has quit IRC | 14:58 | |
| *** udesale has joined #storyboard | 14:59 | |
| persia | For icons: what do others think about "hands" for creator, "hands-helping" for collaborator (added task, added comment, changed description/title, etc.), and "handshake" for assignee? | 15:03 |
| *** udesale has quit IRC | 15:03 | |
| * persia has failed to find another sensible set of three humanesque icons that seemed to have the right semantics from the fontawesome library, but may not have looked hard enough | 15:04 | |
| SotK | handshake and hands-helping are quite similar, but other than that I'm fine with that suggestion | 15:05 |
| persia | hand-receiving was the other candidate for assignment, but that ends up being similar to just hands. | 15:10 |
| SotK | that also requires "pro" :( | 15:13 |
| SotK | fontawesome 5 is something closer to an "open core" model than previous actually open source versions | 15:15 |
| SotK | "pro" isn't particularly compatible with FOSS projects, even disregarding the other problems with that: https://fontawesome.com/help#use-opensource | 15:16 |
| persia | Oh, ugh. I didn't even consider that possibility. | 15:21 |
| * SotK dislikes it | 15:22 | |
| * persia encounters https://github.com/fictiondotcom/ficons and ponders whether it makes sense to just create a custom iconset | 15:30 | |
| SotK | if we had a willing person/set of people I would be entirely in favour | 15:32 |
| persia | Heh. | 15:37 |
| * persia adds "find SVG author" to todo list | 15:38 | |
| SotK | worth noting we already have a step in our build for building a custom icon font (used for the icon next to "StoryBoard" in the header bar currently) | 15:40 |
| persia | Ooh, so all that needs doing is a) dig out the icon names from the code, b) create SVGs for those, c) create a couple extra for other actor types, d) add them to StoryBoard, and e) include them in the pre-existing build? | 15:44 |
| persia | That's lots easier than I had imagined (involving building a custom icon set as an external project, etc.) | 15:44 |
| SotK | yep, it just needs someone with sufficient SVG-creating talent and time | 15:45 |
| *** jamesmcarthur has quit IRC | 15:50 | |
| *** jamesmcarthur has joined #storyboard | 15:50 | |
| *** jamesmcarthur has quit IRC | 16:35 | |
| *** tosky has quit IRC | 16:59 | |
| *** lodowa has joined #storyboard | 17:00 | |
| *** dtantsur is now known as dtantsur|afk | 17:10 | |
| *** lodowa has quit IRC | 17:18 | |
| *** lodowa has joined #storyboard | 17:23 | |
| *** lodowa has quit IRC | 17:38 | |
| *** jamesmcarthur has joined #storyboard | 17:39 | |
| *** fatema__ has joined #storyboard | 17:44 | |
| diablo_rojo | fatema_, hey :) | 17:50 |
| diablo_rojo | I don't need anything super detailed either. | 17:56 |
| * diablo_rojo caught up on the backscroll | 17:56 | |
| diablo_rojo | If there is anything you need more details on too we can work on getting those added or discuss the item in one of our weekly meetings (kind of what they are there for thought we should add more detail to stories in the first place) | 17:57 |
| *** jmccrory has quit IRC | 17:59 | |
| *** jamesmcarthur has quit IRC | 18:01 | |
| *** jmccrory has joined #storyboard | 18:06 | |
| fatema__ | diablo_rojo, hey there! | 18:17 |
| fatema__ | that's cool ^^, How can I show you my timeline to hear your thoughts about it | 18:18 |
| fatema__ | diablo_rojo, I'd like to know more about testing and documentation. | 18:22 |
| diablo_rojo | fatema__, email it to me :) let me dm you my email addr | 18:31 |
| diablo_rojo | As for docs & testing.. let me grab some links | 18:32 |
| fatema__ | I mean how much time would they take ? | 18:32 |
| diablo_rojo | Ahhh well testing for each thing would probably take a few days. Docs less time. Maybe a day or two tops. | 18:33 |
| diablo_rojo | The largest variable with all of this is how much time the rest of us have to review- the activity itself (doing testing or writing docs) takes substantially less time than it does for us to find the time to review and actually do it. | 18:34 |
| diablo_rojo | I promise to be as diligent as I can to make it a good experience just want to be honest about how slow things can be sometimes. Simultaneously if you get stuck with one story you are welcome to start on the other. | 18:35 |
| fatema__ | yes actually it's cool, you're very responsive with the issues in here and I guess this is the most important factor diablo_rojo ^^ | 18:36 |
| diablo_rojo | We do try :) | 18:38 |
| diablo_rojo | SotK, I updated the agenda for the meeting- https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting | 18:39 |
| diablo_rojo | fatema__, if you have anything you want to add to it too, feel free :) | 18:39 |
| diablo_rojo | just put your irc nic next to the topic when you add it so we know who is leading the discussion | 18:40 |
| *** corvus is now known as kermitf | 18:42 | |
| *** kermitf is now known as corvus | 18:42 | |
| openstackgerrit | Kendall Nelson proposed openstack-infra/storyboard master: Document some usage instructions for a freshly deployed dev instance https://review.openstack.org/556018 | 18:45 |
| fatema__ | The other thing that I can't seem to know https://review.openstack.org/#/c/557070/ why did this patch fail ! | 18:48 |
| fatema__ | I have to go as I have to study for tomorrow's midterm but will check the logs xD | 18:52 |
| fatema__ | if anyone responded to my equiries | 18:52 |
| *** fatema__ has quit IRC | 18:52 | |
| diablo_rojo | Meeting time! | 19:01 |
| *** fatema__ has joined #storyboard | 19:50 | |
| fatema__ | diablo_rojo, I wish you would review the application through outreachy itself as a mentor xD | 19:51 |
| diablo_rojo | fatema__, as soon as the meeting is done I will reply to your email :) | 19:55 |
| fatema__ | oh, diablo_rojo sorry for interrupting | 19:57 |
| openstackgerrit | Jeremy Stanley proposed openstack-infra/storyboard master: Use charset=utf8mb4 in pymysql DBURIs https://review.openstack.org/557498 | 19:58 |
| diablo_rojo | fatema__, no problem at all :) If it was that big a deal I probably just wouldn't have responded yet. I'm not running this one. | 19:58 |
| diablo_rojo | You can join us if you want fatema__ its over in #openstack-meeting | 19:58 |
| diablo_rojo | Though there are only 2 min left | 19:58 |
| *** tosky has joined #storyboard | 19:59 | |
| *** jamesmcarthur has joined #storyboard | 20:00 | |
| fungi | SotK: diablo_rojo: https://review.openstack.org/557498 is the test and documentation change to update dburis everywhere, for completeness | 20:01 |
| * diablo_rojo opens tab for fungi's latest patch | 20:02 | |
| fatema__ | diablo_rojo, maybe next time I'd attend from the beginning ^^ | 20:02 |
| diablo_rojo | fatema__, might be helpful on getting you more aware of everything that is going on :) We do them weekly on Wednesdays at 19:00 UTC in #openstack-meeting | 20:03 |
| diablo_rojo | You can get the details and logs from meetings though here: http://eavesdrop.openstack.org/#StoryBoard_Meeting | 20:03 |
| fungi | yeah, attending meetings is by no means mandatory. we do have minutes and logs from them published as diablo_rojo indicated | 20:04 |
| fungi | but if you're available at that time and want to pop into the meeting to discuss something or even just lurk, that's totally cool | 20:04 |
| *** tosky has quit IRC | 20:05 | |
| diablo_rojo | Exactly, unless you have something you want to talk about with us during the meeting (we can probably talk about it in the channel just the same) reading back through the logs is just fine. | 20:06 |
| diablo_rojo | fatema__, timeline looks good to me | 20:09 |
| *** tosky has joined #storyboard | 20:09 | |
| fatema__ | diablo_rojo,definitely in my next week plans to attend the meeting | 20:10 |
| diablo_rojo | I do want to note I have a lot of work travel planned periodically May- July but I can give you a heads up when I will be harder to reach on IRC and easier to reach via email. I will have like 5 work trips and a vacation in there. | 20:11 |
| fatema__ | diablo_rojo, one final thing is I wish that you'd review the application as a whole through outreachy site | 20:11 |
| diablo_rojo | fatema__, ^^ | 20:11 |
| diablo_rojo | fatema__, can go see if I can figure that out now (unless you have a link for me) | 20:12 |
| fatema__ | . The "Save" button makes the latest version of your application visible to Outreachy mentors and coordinators. | 20:13 |
| fatema__ | and I have saved it | 20:13 |
| fatema__ | I'm making sure that the application as a total has all what you need | 20:13 |
| diablo_rojo | Okay trying to find where I can view it in the less than intuitive UI of the outreachy site :) | 20:14 |
| fatema__ | https://www.outreachy.org/2018-may-august/communities/openstack/#extend-redfish-hardware-provisioning-tooling-for-p this is the project link | 20:14 |
| fatema__ | diablo_rojo, about your trips-> you'll be available through the mail/ will SotK be available (I understand that he is a mentor as well) | 20:16 |
| diablo_rojo | Yes I will be available via email. | 20:16 |
| diablo_rojo | And SotK will be around as much as he has been the last week or so. persia and fungi are also generally around throughout the day to help answer your questions too | 20:17 |
| diablo_rojo | And finally found your application :) | 20:17 |
| diablo_rojo | Cairo, that is awesome :) | 20:18 |
| fatema__ | yes, is ne of your trips here ^^ | 20:19 |
| fatema__ | one* | 20:19 |
| diablo_rojo | Sadly not, the closest I will be is Poland during the internship period. After the internship is done though, we can try to get you funding though the travel support program to our Summit in Berlin in November if you're interested. | 20:20 |
| diablo_rojo | fatema__, Also, application looks good to me :) | 20:21 |
| fatema__ | diablo_rojo, actually not the best weather, you'd enjoy more in winter so it's fine | 20:22 |
| fatema__ | ok that's cool so there is nothing to be modified before the deadline | 20:23 |
| diablo_rojo | fatema__, nope, I think you are good to go. Good luck on your exam :) | 20:23 |
| fatema__ | diablo_rojo, also the Summit looks interesting though, how can I get more details ^^ | 20:23 |
| diablo_rojo | fatema__, at this point we are planning/prepping for Vancouver which happens in May but most of the schedule is out so you can look at it and kinda get a feel for what it would be like in Berlin. https://www.openstack.org/summit/vancouver-2018/summit-schedule/#day=2018-05-21 | 20:24 |
| diablo_rojo | We also record a lot of the sessions so you can watch them as they get posted. There are tons of videos from past summits too. | 20:25 |
| fatema__ | diablo_rojo, super fine thanks alot I will get to those | 20:26 |
| diablo_rojo | :) | 20:26 |
| *** fatema__ has quit IRC | 20:27 | |
| fungi | i may not pay attention in channel unless someone mentions me though, since i tend to float around between a lot of different projects wearing all manner of silly hats | 20:28 |
| * diablo_rojo imagines a closet full of hats that fungi fights to close every night | 20:28 | |
| fungi | more like the "silly hats only" segment from don hertzfeldt's "rejected" | 20:34 |
| diablo_rojo | fungi, imagining this with hats instead of dresses: https://www.youtube.com/watch?v=eiLeBJUf1iE | 20:36 |
| fungi | well, sort of, but with stick figure violence. if you haven't watched rejected, it's short at just under 10 minutes | 20:39 |
| fungi | can easily be found on the tubez | 20:39 |
| fungi | probably also slightly nsfw now that i think about it. but stick figures | 20:40 |
| diablo_rojo | fungi, oh yes I watched it before sending you the link to that video | 20:40 |
| fungi | hertzfeldt is one of my favorite underground animators. i've got a few collections of his stuff on disc including a recent blu-ray with a bunch of them remastered | 20:42 |
| fungi | makes great background entertainment when throwing parties | 20:42 |
| diablo_rojo | fungi, seriously think we should do an eng team weekend at your place with pie, internet comics, games and hacking. | 20:43 |
| fungi | he collaborated with mike judge (beavis and butthead, milton/office space, king of the hill) on some stuff | 20:43 |
| diablo_rojo | Oh thats interesting. | 20:43 |
| fungi | they ran "the animation show" for a number of years which was a collection of underground animation from various animators which did the film festival circuits | 20:44 |
| fungi | some real trippy stuff | 20:45 |
| fungi | yeah, if we do a get-together at my place, i have shelves full of animation | 20:46 |
| *** tosky has quit IRC | 20:50 | |
| *** tosky has joined #storyboard | 20:54 | |
| *** jamesmcarthur has quit IRC | 21:03 | |
| *** jamesmcarthur has joined #storyboard | 21:10 | |
| *** jamesmcarthur has quit IRC | 21:12 | |
| *** jamesmcarthur has joined #storyboard | 21:12 | |
| openstackgerrit | Jeremy Stanley proposed openstack-infra/storyboard master: Use charset=utf8mb4 in pymysql DBURIs https://review.openstack.org/557498 | 21:25 |
| *** jamesmcarthur has quit IRC | 21:30 | |
| *** jamesmcarthur has joined #storyboard | 21:33 | |
| -openstackstatus- NOTICE: the zuul web dashboard will experience a short downtime as we roll out some changes - no job execution should be affected | 21:53 | |
| *** jamesmcarthur has quit IRC | 22:48 | |
| *** tosky has quit IRC | 23:16 | |
| *** jamesmcarthur has joined #storyboard | 23:18 | |
| *** jamesmcarthur has quit IRC | 23:22 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!