Oh! I didn’t say they are not production ready. Of course we’ve some issues and but it’s working pretty well and there are no more major issues. We’re planning for 2.x release soon and basically, we remove some stuff and introduce more patterns when developing apps.
What is not production ready is flow-components and it’ll stay the same. It’ll be our toy project
Has there been a conversation somewhere on Iron Router vs Flow Components and Flow Layout? I wonder what the pros and cons are of both, and if anyone has been using Flow Router extensively and has some feedback on it (who isn’t @arunoda :] )
as in "Ground Control to Major Tom . . . Slack is about communication.
Mission Control
could be a good alternate. Slack is also where you manage your business/mission–if you are using it right. (I’m from Houston, home of NASA. Plus I’m good at naming things.)
@timbrandin I started MRC a couple weeks ago but haven’t had a ton of time to get everything going on it but it’s started. It was planned to be an IRC/Slack/HipChat type app and I was hoping with meteor and such it would be easy to put it on every screen (Cordova for native apps as well).
I’m interested in helping and if it would be similar to my current project we could merge or I could drop that to help with this. I preferred a more simplistic or minimal layout but , to be honest, it would be ideal if we made a choice in preferences to have a bubbly IM type feel or simple/condensed IRC feel as it’s all the same.
my original idea was to copy everything IRC can do with the multi-rooms, admins (ircops) and so on but in a meteor way… was definitely looking at HipChat/Slack as well. What do you think?
@m0g if you could easily roll it out on every platform with apps on top of the meteor core would be nice, similar to Telegram (www.telegram.org) and how they have an app for every platform. My inspiration for starting MRC a couple weeks back was to have a branded chat solution that allowed for public chat server/rooms like IRC as well as private rooms and user controls.
some reasons:
its simpler. shorter.
its totally inside of the meteor naming system
its the most used key during chatting…
i can also help you, but i think much more structurewise than developing.
The most important feature with chat apps is the alerting when someone is offline. that you do not miss the important stuff, but also are not bothered with useless emails all the time. Slack were the first one to get this right…
It looks like there is some interest, we have a stub of an application and a name to go with. So where do we go from here?
I know nothing about running open source projects so correct me if I’m wrong but it would be helpful to have the following:
A vision for the product, who does it serve, what does it do, what does it not do
A clear and visible roadmap so that people can jump in if they desire
Lastly, two quick things I might suggest to garner more interest:
Make the default branch for the app to be ‘step-25’. When you checkout the github project you get a stock Meteor application. This makes it look like nothing has been done which is clearly not the case.
Put a demo online somewhere and a screenshot of the app in the readme. It’s a lot easier to get excited about something you can see.
I’d be glad to spend a couple of cycles hacking and designing on this project but want some direction before I start sending unsolicited pull requests.