Launch and scope for next release

[andypike]

Hi guys,

So, we did it! The site has launched and so far everything has been running smoothly. The server seems to be holding up ok although we did have a large spike in traffic when the announcement video came out it all seems to running fine now.

Thank you to everyone that made this possible. It's been a real community effort and I've very proud of you all, thank you.

Moving forward we need to start thinking about the next release. I'm going to hold off doing any changes for a couple of days just in case a serious issue comes up after the launch. Adam has been through all of the issues in GitHub and has given me feedback on each one (that was a lot of work so kudos to you sir). Basically he put the issues into 3 categories: things that need doing soon, things that can happen in the future and things that we will not need to do. I've gone through the issues and have organised them as such. Firstly, there are two milestones: Backlog and Icebox. The backlog holds the issues that we think need to be done soon. Icebox holds the issues that can come in the future. All the other issues have been closed. 

So I'm looking for your thoughts on what issues are top priority. I'd like to keep releases quite small but could each of you reply to this with your 3 highest priority issue numbers. I've created a milestone called "1.1.0" which will hold the issues for the next release and I've popped a few issues in there already. I'd like to get your feedback for the next release which will help us focus on the important stuff.

Thanks again!

Andy

[Stuka87]

Not really sure if I could pick out just three items. There are lots of items that I would consider to be roughly the same value, with some being above and some being not needed.

I would love a few more options for replay submissions. Mostly being length (ranged, like less then 10, 10-20, and 20+), 1v1 or 2v2 (I know there is a github issue for this), and I saw an issue for flagging replays. But if a replay just will not play, I would suggest just rejecting it and stating in the comment that it would not play properly. Same goes for replays from the current HotS beta. I am not sure there are any analyst that can replay these. But a tag for the future to separate them once they are released would be nice.

One thing I would love changed is to always sort forum post by the most recent post date.

I know thats way more than 2-3, its just what came to mind currently. And since I am an analyst, they are a bit skewed towards what I come across :)

[Robert Johnston]

I have a suggestion, which I can help with (It seems relatively simple
to do): Can we PLEASE make the site fluid?

It was both embarassing and cringe-inducing to watch Adam introducing
the site, as his 1920x1080 desktop made it look stupidly small, in a
tiny band down the middle of the screen. If you forsee problems with the
site on smaller screens, I suggest that we can use the min-width
declaration.

Here's the necessary CSS changes:

Change the rule: ".container, .navbar-fixed-top .container,
.navbar-fixed-bottom .container {
width: 940px;
}"

to read: ".container, .navbar-fixed-top .container, .navbar-fixed-bottom
.container {
min-width: 940px;
}"

Add a rule:

".logo_line .container a {
pading-left: 50%;
}"

And modify the rule: "header .logo {
margin: -84px 0px 0px 389px;
}"

To read: "header .logo {
margin: -84px -81px 0;
}"

Change: "#home .inner-banner {
background: url("tab-bg.png") repeat scroll 0% 0% transparent;
}"

To read: "#home .inner-banner {
background: url("tab-bg.png") repeat-y scroll 0% 0% transparent;
}"

Modify the order of the source so that the right-arrow element(s) (<div
class="pan-right pull-left">...</div>) comes before the viewport
element(s), change the "pull-left" to "pull-right" on the "pan-right"
and remove the "pull-left" on the viewport.

Change: "#home .channel .viewport {
overflow: hidden;
width: 862px;
margin: 0px 10px;
}"

To read: "#home .channel .viewport {
overflow: hidden;
width: auto;
margin: 0px 39px;
}"

And that's it. It's a few tiny CSS changes, but it makes the entire site
fit to the width of your browser, and look much better. The only slight
issue might be the background images on the tabs not stretching wide
enough, but that can be corrected easily enough (In fact, a better
method would be to have a full-width (2440-px wide, aligned center)
"starburst" image that gets set as the background of "#home
.inner-banner", and the (left-aligned) channel tab background gets set
on "#home .inner-banner .tabs"

The changes are fully CSS compliant, and work in FireFox, Chrome and
IE9+. Let me know what you think.

[Stuka87]

Well it should be noted he has a 27" display that has a resolution of 2560x1440. On my 1080P and 1200P displays, it doesn't look that bad, and I never have my browsers at full screen. Doesn't mean your idea isn't a bad idea, just saying Adam has a much larger resolution than the average person.

[Stuka87]

Oh, one other thing I would love to see in the forums, a way to go to the most recent unread post. Now maybe you guys are not tracking what threads have been read yet. But if so, I use that button a LOT on other forums (My own included).

[Robert Johnston]

On 2012-11-10 7:41 PM, Stuka87 wrote:
> Well it should be noted he has a 27" display that has a resolution of
> 2560x1440. On my 1080P and 1200P displays, it doesn't look that bad, and
> I never have my browsers at full screen. Doesn't mean your idea isn't a
> bad idea, just saying Adam has a much larger resolution than the average
> person.

I'm using 1680x1050 (With the Windows 8 task bar on the right), and it
looks a little too narrow. But that video was really way too narrow. And
I know that 2560 is generally the largest you can get for a single
monitor (multi-monitor users are more than likely used to websites
looking odd when stretched out to crazy aspect ratios), which is why I
suggested it as the width for the starburst.

If you want the site resizable down even further (for tablet/mobile
platforms), I can certainly look into doing that too, but for now I
thought this simple tweak would certainly add something to the site.

[Ludi Productions]

lol, Andy,

You made it tough for me to decide, XD.

1. Thread comment prioritization, thread bumping, preview, and quotes are a high priority for me. I think working on thread/post issues should be clean up a bit first before it becomes too clustered and confusing.
2. Analyst issues. I wanted to put this as number 1 (perhaps work on both?), but I think it should be easy enough to add more options for replay submissions. Flagging replays and editing ratings, I was kinda hoping this would happen as well, but could wait though.
3. Mod tools and/or Profile/Users - It is not a really important issue at this moment since:

Mods:
Users list/warning system can wait. I haven't seen any major issue with reporting issues since we have plenty of mods to take care of it and keep track of.

Profile/Users:
More features (Bios, stats, etc.) can be added as we go and it's not really important to have as of right now. We're still growing and testing how the analysts rating/comments goes first before we can proceed adding this feature to the profile.


As I was typing this, I went to check the milestones you set up, Andy, and I agree what you have set up and to have small releases. I am going to wait on the thread/post suggestions until Forem has been updated to see the changes made to thread/posts.

But for now, more replay submission options, flagging replays, and edit ratings as a high priority..

For now, ignore my priorities above or you could take them into consideration. Thanks!

[Stuka87]

Just one more suggestion, and this would mostly be for Adam. Be able to filter replays on who has reviewed them. This would be mostly to see who is actually reviewing games. If you filter on user X and there are no replays, then chances are they are not actively reviewing. Although it could also mean that tons of reviews are being submitted so older ones are being pruned sooner.

[Andy Pike]

Thanks for the feedback guys, very useful as normal :o)

I'm going to pull together some issues into the next release that I think fit the bill based on your feedback and we can go from there. Don't forget that we are planning to release small but often so if your issue doesn't make it this time don't worry as there will be another release around the corner.

I'll let you know when this is ready for you to look at.

Cheers

Andy

[Andy Pike]

Hi all,

Right I've been through all the issues and have an initial release setup here: https://github.com/andypike/lagtv/issues?milestone=11&state=open This release is focused on the forum mostly. This release is a bit bigger than I would ideally like but there are quite a few related forum issues and it'll probably be easier to deal with these all together. This biggest job is probably the upgrade to the latest Forem version. Depending on how long this takes, I might move out some of the other issues, but this is the current target.

Please let me know if I've missed something important that has to be done and I'll add it. The other issues in the backlog will be pulled into another release. 

Cheers

Andy

[Ludi Productions]

Sounds good, Andy. We have to get Forem up to date. Otherwise, those issues are ok with me for us to work on. I'll keep you guys posted if I find any issues and do some more investigating.

[Stuka87]

Looks good to me. Only one I kind of take issue with is letting users edit HTML. Really opens the door for people to put in code that we may not want them too. So I consider it kind of a security issue.

[Robert Johnston]

So then don't let them edit HTML. Use Markdown for simplicity, or
BBCode for compatibility with most (if not all) other forum systems, or
some other method to sanitize the user input.

[Andy Pike]

We have a sanitizer that cleans up the HTML to only tags and attributes that we allow. This is really to help when people paste content in and the format screws up.

Sent from my iPad