Tracking issue for Next Release

[rikai]

CC @eriknelson, @s0ph0s-2, @cbojar, @herbmillerjr & @Hippyjake as the currently active people working on the project.

This is a tracking bug for the Next Release milestone.
The current list of tasks for Next Release follows (With the currently assigned people in brackets):

• Async title page reload (@eriknelson)
• Abstract Admin functionality (@eriknelson)
• Make plugins that use data.json more robust (@cbojar)
• Implement command cooldowns using cinch-cooldown (@s0ph0s-2)
• Implement Rate limiting (@s0ph0s-2)
• Implement 'silent mode' (@eriknelson)
• Track down unknown memory leak (@eriknelson)
• Add variable title limits per show (Unfinished PR)
• Switch Twitter API from polling to streaming (Tweetstream branch, needs some love)
• Migrate to google-api-client 0.9.x (Unfinished PR)

I've created this as a central place to collaborate on finishing off these tasks in a timely fashion. The original stated goal date of this release was 'Mid-September', with the caveat of possibly taking to the end of September.

If it's still possible to hit that goal, that'd be really nice. However, if outside forces prevent working on stuff, that's understandable as well and stating as much as fine. It'll just let other people take over in your stead. 👍

Feel free to use this issue for discussion of collaboration, passing off of information or anything else relating to getting these tasks done.

This issue will be updated as tasks are completed.

[rikai]

Also, would doing some sort of 'group sprint' this weekend be something that would help people along?

I'm willing to be available via IRC if we wanted to make a group effort! 💯

[ObserverHerb]

That kind of thing seems to help the Solus project a lot. I can only take part in such when it's my turn to elder-sit the parental unit (like last weekend, when I started contributing). But whenever it lands on one of those weekends I'm game. Sorry I can't help with one for this release cycle.

[rikai]

Due to the lack of responses, I think I'll delay this until next weekend, that way everyone will have a week to plan for it. 👍

[rikai]

@eriknelson, @s0ph0s-2, @cbojar, @herbmillerjr & @Hippyjake Any of you guys able to make it at any point between now and sunday? :)

[s0ph0s-dog]

I have exams this upcoming week, so I might have some time after I finish studying.

On 2016 sep 15 15:54 -0400, rikai [email protected], wrote:

@eriknelson (https://github.com/eriknelson), @s0ph0s-2 (https://github.com/s0ph0s-2), @cbojar (https://github.com/cbojar), @herbmillerjr (https://github.com/herbmillerjr) & @Hippyjake (https://github.com/hippyjake) Any of you guys able to make it at any point between now and sunday? :)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (#70 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/ATl-TSJd0tLb8ZDVj8k9tR570lc1mBcnks5qqaJ7gaJpZM4J4Sjk).

[ObserverHerb]

Yeah, I should be able to drop in here and there.

On Sep 15, 2016 3:54 PM, "rikai" [email protected] wrote:

@eriknelson https://github.com/eriknelson, @s0ph0s-2
https://github.com/s0ph0s-2, @cbojar https://github.com/cbojar,
@herbmillerjr https://github.com/herbmillerjr & @Hippyjake
https://github.com/hippyjake Any of you guys able to make it at any
point between now and sunday? :)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#70 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAxYaQHazX3hd6909a7dSTLigV4RWe7-ks5qqaJ7gaJpZM4J4Sjk
.

[rikai]

Alright, just give me a ping if you're active in the IRC and working on something so i can keep track. I'm going to be working on the tweetstream stuff myself this weekend, but i'd be happy to see discussion/activity on any implementation details or whatever over the course of this weekend.

Hoping for a big push to check off the rest of those boxes and release! 👍 💃 🍖

[rikai]

Sadly, we missed our release date goal due to everyone being extremely busy, but that's understandable.

That said, I'd still like to get things crossed off the list, so if you guys could give me a status update on things when you've got a chance, that'd be wonderful! 🍖

[s0ph0s-dog]

I hope to finish up my issue this weekend, but I can't fully commit to it until I know how much other work I'll have.

On Oct 3, 2016, 11:03 -0400, rikai [email protected], wrote:

Sadly, we missed our release date goal due to everyone being extremely busy, but that's understandable.

That said, I'd still like to get things crossed off the list, so if you guys could give me a status update on things when you've got a chance, that'd be wonderful! 🍖

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (#70 (comment)), or mute the thread (https://github.com/notifications/unsubscribe-auth/ATl-Tc25UwaMwKbgQ_JhF-ldZZQFyhcSks5qwRk7gaJpZM4J4Sjk).

[rikai]

Initial work on the tweetstream code is now in the FEATURE/tweetstream branch.

The code is pretty minimal to get it up and running, but I'm running into issues restricting the output to only the users tweets, rather than replies from others and retweets as well.

[rikai]

@s0ph0s-2 Had a chance to look at the updated cinch-cooldown?

[s0ph0s-dog]

I have! I got it partly working during a hackathon in November, but I wasn't able to quite get it working. I'll be able to finish it this May, after the spring semester ends.