Open venkatachalapathy opened 5 years ago
I have done some of that. Variable cardinality, whitespace, notification time, and other issues are ones that I put in after getting a shortlist from Marty. We decided to let him keep his full list and filter that to what goes into the issue tracker, at least for the time being. As you can see, the tracker is already starting to get a little busy. No complaints, I'm glad that people are starting to use it. Just keep in mind that there are currently only a couple of people looking at the code or working on documentation, so having more than a few of Marty's items in the issue tracker is unrealistic for what can be accomplished in the short term. That might be okay, and it might be worth putting in some more of the issues off his list. Personally, I'm fine with where we are on this for now, especially since there are also a number of documentation-related issues as well. But if we do want to put in a few more, I have a shortlist. Just be aware that we very likely are not going to put all of the stuff from his lists (several dozen items at least) in just yet. Just not quite sure the best number to have in at this point so any thoughts on that are appreciated.
I understand, Guy.
My thoughts were to see what they are; classify them; assign tags; and sneak them into capstone to-do-s. My guess is that Marty's list is all over the place in terms of breath and depth. Knowing what they are might help inform what we are doing now. I remember Bart mentioning that we need to have a few clear and easy and interesting fixes for outside contributors to make. So who knows, maybe some of the items on his wish list needs to be broken down into simple pieces.
I could easily gain access to them via Marty but as Bart mentioned the other day, the more open this list, the more transparent and better it will be for this project.
That makes sense - Bart made the same point that it's good to just have them in there even if they are tagged 'future' or whatever. I still think getting ALL of the stuff on Marty's lists in will be a gradual process - I started to go through the spreadsheets one day and my eyes crossed a little bit because a lot of the items were very technical things that I don't even have enough experience with OCCAM yet to quite understand the details of, and so I would want to sit down with Marty and talk through them to make sure that I understand what the issue actually is. But I do have a few more items off of Marty's shortlist that I'll finish putting in.
Guy, I might be able to translate Marty's wish list and try to partially decompose the items ;) That is one place where I can be most useful at the moment. This will also help me scavenge for optimal algorithms for these items.
In lieu of an issue list, how about creating of a publicly available .md with potential to grow into some kind of document?
That would be great if you wanted help go through them. A little more discussion with Marty is needed before posting the full lists in channel I think but I'm sure he would go through them with you. The two spreadsheet lists he was working with have dates of 2016 and 2017 so he wanted to clean up and update them. I think that's why he sent me the short list, because those were the things that were most relevant and definitely needed to go in the tracker. I still don't have an exact view of the status of all those list items so if you have a chance to ask him about that I'm sure he will give you some guidance. I'm not around the department much this term and it's easier to discuss in person than by email since the lists are extensive.
After some more discussion it seems that we are in agreement to help make this happen (going through his lists and determining what's still current and at what priority, and getting those in the tracker). That will have to wait until Marty is back from his trip (Feb. 25th I think). So let's plan to take a look then.
During our meeting yesterday 02/08, Marty mentioned that he has a few dozen items on his
occam-ra
wish list. It might be a good idea to put them all here as issues and tag them appropriately for all of us to see.