Nice to see everyone on the same page. Slack is making the world a better place one team at a time
Based on your use case, you need a few integrations. Mconf itself does have an API, and so in principle you could set up a hubot or slack slash integration to talk to this API from within slack, as well as get data
out of mconf, into slack. If you've had a look at https://api.slack.com/ you'll know what I mean...
In order to get reminders into slack, you can already use slackbot or meekan to do this. Just integrate a calendar with your team and slackbot will bounce reminders to the teammates on calendar events (with a configurable advance notification). Another easy way to do this is set up a Zapier or IF rule. Again, none of these have Mconf channels, so
you'll have to write that little bit of code which talks to the mconf API (and @KasandraIsaac_9038 has to give you an API token, as well as set it up), and have a service which listens for events. It sounds a lot trickier than it actually is.
The very easy way is just to create a google calendar for the project, share it with your team mates, add the google calender integration to slack and bang you're done. If there's an event, your team gets reminded of it.
now, the more tricky bit of getting data out of mconf and into slack :
What I was thinking:
Have some way of being able to commit a note or chat segment to slack / trello as an actionable task for a member directly from mconf. Example, while running a meeting, we document the discussion / action items in the notes or chat section. I can then simply right click an action item and “commit” it to slack and point it to a slack team member. This action item is then trackable via slack and managed in trello this will reduce time and simplify following up on tasks assigned.
If you ask me, slack beats mconf when it comes to chat and notes. The kind of functionality you want here, from within Mconf, requires committing new code to the mconf code base, and I would hazard a guess that that's unfeasible. It's certainly possible, but wow, it would be much easier to just type
/remind @user to do something by sometime
Then you both get reminded. You can remind whole channels. You can set deadlines, etc...
Once the meeting is concluded, we can export the notes and chosen chat section / text to the mConf document repository or google and automatically be disseminated to members as the meeting notes this will reduce time spent on writing up minutes after meetings.
Again, why not just leave mconf to do the conf stuff ? Ie, video and voice. Leave the content in the app that's being used to edit it, and integrate that to Slack. If there are todos that you're managing with Trello, use the trello integration. If you're using github to track issues, or Zenhub or whatever, these already have integrations.... If you're using google docs to write notes, just use that integration in a channel. Personally, I prefer using the Slack notes themselves, since
they already have context and Markdown is sufficient for most needs (although your mileage may vary...)
Long story short, the collaboration platform is Slack , not mconf.
Send out automatic reminders of meetings and action item deadlines
See my opinions on this above.
@KasandraIsaac_9038 said :
"We use slack quite extensively across the network." - Who's we?
At the moment we at CBIO and H3ABioNet have several slack teams where we
interact with individuals from UCT, H3ABioNet nodes, CHPC,
Let's not forget literally everyone. Slack is basically the best thing ever, iyam
I think the head of an Mconf developer is necessary here. I would strongly support getting an Mconf app into slack, which could be hosted by SANREN - this would be great for the uptake of the service (mconf), since again, Slack is eating the world, and it would be nice to tell our researchers - "use slack, and then add the mconf integration to run
your web meetings". Then they can do
/app add mconf
We can certainly hack something together - a little api server listening to events from slack, a token here and there, a bit of json passed between the slack team and the mconf api, a callback... shouldn't be too hard. But it will be a hack without the guidance of a Mconf developer. I think the best thing to do would be to discuss this with them first and then take a stab at it.
In any case, I'm keen