The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Would appreciate your thoughts.
Thanks, --Mike
On May 29, 2018, at 11:23 AM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Slack! It's the answer to everything!!
Seriously, though, there are a lot of things to consider. Is the team co-located? Spread across different offices? Different time zones?
Since you mention several organizations, I will assume that they are geographically disperse; in such cases, some form of asynchronous communication is best. Otherwise, people will miss out on things because they are in a different time zone. Email is great for async communication, but hard to use as a reference document. Wikis are accessible, but suffer from bit rot. I prefer to use GitHub, assuming that people have ability to handle the basics of git. You can write docs using ReStructured Text (.rst), and view them on GitHub in their rendered form. For an example, see the style guide for the OpenStack project I work on (Nova): https://github.com/openstack/nova/blob/master/HACKING.rst. After you see that, click the 'Raw' button on the top right to see the original .rst file.
One of the nice things is that it is easy to update the doc using pull requests. These can be reviewed and merged as needed. This allows teams to collaborate easily, and helps ensure that a consistent style is used for all docs. You might also consider GitHub Pages (https://pages.github.com/) for a more website-y look.
-- Ed Leafe
--- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/pgp-signature ---
On 2018-05-29 12:39, Ed Leafe wrote:
On May 29, 2018, at 11:23 AM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Slack! It's the answer to everything!!
Seriously, though, there are a lot of things to consider. Is the team co-located? Spread across different offices? Different time zones?
Since you mention several organizations, I will assume that they are geographically disperse; in such cases, some form of asynchronous communication is best. Otherwise, people will miss out on things because they are in a different time zone. Email is great for async communication, but hard to use as a reference document. Wikis are accessible, but suffer from bit rot. I prefer to use GitHub, assuming that people have ability to handle the basics of git. You can write docs using ReStructured Text (.rst), and view them on GitHub in their rendered form. For an example, see the style guide for the OpenStack project I work on (Nova): https://github.com/openstack/nova/blob/master/HACKING.rst. After you see that, click the 'Raw' button on the top right to see the original .rst file.
One of the nice things is that it is easy to update the doc using pull requests. These can be reviewed and merged as needed. This allows teams to collaborate easily, and helps ensure that a consistent style is used for all docs. You might also consider GitHub Pages (https://pages.github.com/) for a more website-y look.
-- Ed Leafe
Thanks, Ed. I'll review that. The end-users are NOT tech-savvy folks, most likely, so it'll have to be a super-user-friendly UI.
On 2018-05-29 12:39, Ed Leafe wrote:
On May 29, 2018, at 11:23 AM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Slack! It's the answer to everything!!
Seriously, though, there are a lot of things to consider. Is the team co-located? Spread across different offices? Different time zones?
Since you mention several organizations, I will assume that they are geographically disperse; in such cases, some form of asynchronous communication is best. Otherwise, people will miss out on things because they are in a different time zone. Email is great for async communication, but hard to use as a reference document. Wikis are accessible, but suffer from bit rot. I prefer to use GitHub, assuming that people have ability to handle the basics of git. You can write docs using ReStructured Text (.rst), and view them on GitHub in their rendered form. For an example, see the style guide for the OpenStack project I work on (Nova): https://github.com/openstack/nova/blob/master/HACKING.rst. After you see that, click the 'Raw' button on the top right to see the original .rst file.
One of the nice things is that it is easy to update the doc using pull requests. These can be reviewed and merged as needed. This allows teams to collaborate easily, and helps ensure that a consistent style is used for all docs. You might also consider GitHub Pages (https://pages.github.com/) for a more website-y look.
Here's something we found today in our searching; a nice "18 best tools for online collaboration" : https://www.creativebloq.com/design/online-collaboration-tools-912855
My colleague is liking what she's seeing about Yammer, a Microsoft product. Apparently we do have some Microsoft servers here (although I haven't researched it fully yet; maybe we could host this in "The Cloud" too).
Ed beat me to Slack. We use it with the KofC to keep small groups working on a project together in touch with one another. None of us work together but we can all hook up as needed to share via Slack.
On Tue, May 29, 2018 at 11:23 AM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Would appreciate your thoughts.
Thanks, --Mike
[excessive quoting removed by server]
Another +1 for Slack.
Fred
On Tue, May 29, 2018 at 10:02 AM, Stephen Russell srussell705@gmail.com wrote:
Ed beat me to Slack. We use it with the KofC to keep small groups working on a project together in touch with one another. None of us work together but we can all hook up as needed to share via Slack.
On Tue, May 29, 2018 at 11:23 AM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be
best.
Would appreciate your thoughts.
Thanks, --Mike
[excessive quoting removed by server]
On May 29, 2018, at 12:15 PM, Fred Taylor fbtaylor@gmail.com wrote:
Another +1 for Slack.
Slack works well for synchronous communication, not as well for async, and is worthless as a document store.
-- Ed Leafe
--- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/pgp-signature ---
We use Google Drive for the necessary file sharing.
Fred
On Tue, May 29, 2018 at 10:18 AM, Ed Leafe ed@leafe.com wrote:
On May 29, 2018, at 12:15 PM, Fred Taylor fbtaylor@gmail.com wrote:
Another +1 for Slack.
Slack works well for synchronous communication, not as well for async, and is worthless as a document store.
-- Ed Leafe
--- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/pgp-signature
[excessive quoting removed by server]
On 2018-05-29 13:18, Ed Leafe wrote:
On May 29, 2018, at 12:15 PM, Fred Taylor fbtaylor@gmail.com wrote:
Another +1 for Slack.
Slack works well for synchronous communication, not as well for async, and is worthless as a document store.
This need is for information sharing on a permanent level, with thread history and file sharing; there's really no need for instant messaging.
What are the list's thoughts on Drupal?
Wiki.
You need to have a Wikimaster and/or volunteers/power-users who can step in and refactor things, clean up threaded discussions into outlines, etc.
Best practices become static, organized documents, easy to index and cross-reference.
Many support file upload/download for a shared repository.
They're cheap, easy to self-host, (relatively, mostly) easy to migrate from one to another.
Mostly, they've got long-term staying power. No single vendor to pull the plug. (cite: http://wiki.c2.com/?WelcomeVisitors)
On Tue, May 29, 2018 at 12:23 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Would appreciate your thoughts.
Thanks, --Mike
[excessive quoting removed by server]
I'm with Ted - wikis are great for this type of thing. We're using a hosted version of Atlassian Confluence. No fuss - no muss. Works well. Recommended.
Malcolm
As many of you know from my SW Fox session. I'm an advocate of OneNote. If you have a SharePoint site you can share it on it's amazing as a collaboration tool.
Eric
On Tue, May 29, 2018 at 1:58 PM, Malcolm Greene profox@bdurham.com wrote:
I'm with Ted - wikis are great for this type of thing. We're using a hosted version of Atlassian Confluence. No fuss - no muss. Works well. Recommended.
Malcolm
[excessive quoting removed by server]
On Tue, May 29, 2018 at 3:40 PM, Eric Selje Eric@saltydogllc.com wrote:
As many of you know from my SW Fox session. I'm an advocate of OneNote.
And if you don't, you can read it here:
http://saltydogllc.com/wp-content/uploads/OneNote-to-Rule-Them-All.pdf
If you have a SharePoint site you can share it on it's amazing as a collaboration tool.
I'm just a bit gun-shy about single-vendor solutions from MSFT, for some reason ;)
Justified.
On Tue, May 29, 2018 at 3:28 PM, Ted Roche tedroche@gmail.com wrote:
On Tue, May 29, 2018 at 3:40 PM, Eric Selje Eric@saltydogllc.com wrote:
As many of you know from my SW Fox session. I'm an advocate of OneNote.
And if you don't, you can read it here:
http://saltydogllc.com/wp-content/uploads/OneNote-to-Rule-Them-All.pdf
If you have a SharePoint site you can share it on it's amazing as a collaboration tool.
I'm just a bit gun-shy about single-vendor solutions from MSFT, for some reason ;)
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
[excessive quoting removed by server]
And nothing in our current solution stack in Microsoft. Java shop running JSP pages on Linux servers and Oracle database.
On 2018-05-29 17:47, Eric Selje wrote:
Justified.
On Tue, May 29, 2018 at 3:28 PM, Ted Roche tedroche@gmail.com wrote:
On Tue, May 29, 2018 at 3:40 PM, Eric Selje Eric@saltydogllc.com wrote:
As many of you know from my SW Fox session. I'm an advocate of OneNote.
And if you don't, you can read it here:
http://saltydogllc.com/wp-content/uploads/OneNote-to-Rule-Them-All.pdf
If you have a SharePoint site you can share it on it's amazing as a collaboration tool.
I'm just a bit gun-shy about single-vendor solutions from MSFT, for some reason ;)
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
[excessive quoting removed by server]
I think that a CMS could be an option
El mar., 29 may. 2018 18:22, mbsoftwaresolutions@mbsoftwaresolutions.com escribió:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Would appreciate your thoughts.
Thanks, --Mike
[excessive quoting removed by server]
So many points have been made that cover a variety of this major request.
Can you describe in more detail what you want to achieve? What is the mission statement or the executive view for this functionality? From that, we might get you closer to a PRODUCT that scales in multiple directions. Are you looking to keep documents across versions for a project, or are you looking to bolster communication to a team that may be operating outside of your main building? Will this be a source control center or a PM one that identifies agile stories that are involved in a sprint?
On Wed, May 30, 2018 at 9:50 AM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2018-05-30 01:20, Fernando D. Bozzo wrote:
I think that a CMS could be an option
Any you would recommend in particular?
[excessive quoting removed by server]
Mike, SweetCRM is a particularly good open source CRM that is constantly evolving with loads of free "addins". Paid version is cloud hosted but the open source version you can host on either your own or an external ISP's server
Dave
Dave Crozier Software Development Manager Flexipol Packaging Ltd.
--------------------------------------------------------------- This communication and the information it contains is intended for the person or organisation to whom it is addressed. Its contents are confidential and may be protected in law. If you have received this e-mail in error you must not copy, distribute or take any action in reliance on it. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
Flexipol Packaging Ltd. has taken every reasonable precaution to minimise the risk of virus transmission through email and therefore any files sent via e-mail will have been checked for known viruses. However, you are advised to run your own virus check before opening any attachments received as Flexipol Packaging Ltd will not in any event accept any liability whatsoever once an e-mail and/or any attachment is received.
It is the responsibility of the recipient to ensure that they have adequate virus protection.
Flexipol Packaging Ltd. Unit 14 Bentwood Road Carrs Industrial Estate Haslingden Rossendale Lancashire BB4 5HH
Tel:01706-222792 Fax: 01706-224683 www.Flexipol.co.uk ---------------------------------------------------------------
Terms & Conditions:
Notwithstanding delivery and the passing of risk in the goods, the property in the goods shall not pass to the buyer until the seller Flexipol Packaging Ltd. ("The Company") has received in cash or cleared funds payment in full of the price of the goods and all other goods agreed to be sold by the seller to the buyer for which payment is then due. Until such time as the property in the goods passes to the buyer, the buyer shall hold the goods as the seller's fiduciary agent and bailee and keep the goods separate from those of the buyer and third parties and properly stored protected and insured and identified as the seller's property but shall be entitled to resell or use the goods in the ordinary course of its business. Until such time as the property in the goods passes to the buyer the seller shall be entitled at any time
-----Original Message----- From: ProFox profox-bounces@leafe.com On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: 30 May 2018 15:51 To: ProFox Email List profox@leafe.com Subject: Re: [NF] Best Practices for collaborative sharing of information
On 2018-05-30 01:20, Fernando D. Bozzo wrote:
I think that a CMS could be an option
Any you would recommend in particular?
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/2ac6fd39c0b592d0fbc3c38f058c485c@mbso... ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 2018-05-30 11:05, Dave Crozier wrote:
Mike, SweetCRM is a particularly good open source CRM that is constantly evolving with loads of free "addins". Paid version is cloud hosted but the open source version you can host on either your own or an external ISP's server
Dave
Dave Crozier Software Development Manager Flexipol Packaging Ltd.
Hi Dave,
Did you mean https://suitecrm.com/ ?
Or maybe SugarCRM? Sugar is sweet.
On Thu, May 31, 2018 at 6:12 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2018-05-30 11:05, Dave Crozier wrote:
Mike, SweetCRM is a particularly good open source CRM that is constantly evolving with loads of free "addins". Paid version is cloud hosted but the open source version you can host on either your own or an external ISP's server
Dave
Dave Crozier Software Development Manager Flexipol Packaging Ltd.
Hi Dave,
Did you mean https://suitecrm.com/ ?
[excessive quoting removed by server]
My goodness, there IS a product called SugarCRM!!
So which is it, Dave? :-)
On 2018-06-01 10:46, Eric Selje wrote:
Or maybe SugarCRM? Sugar is sweet.
On Thu, May 31, 2018 at 6:12 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2018-05-30 11:05, Dave Crozier wrote:
Mike, SweetCRM is a particularly good open source CRM that is constantly evolving with loads of free "addins". Paid version is cloud hosted but the open source version you can host on either your own or an external ISP's server
Dave
Dave Crozier Software Development Manager Flexipol Packaging Ltd.
Hi Dave,
Did you mean https://suitecrm.com/ ?
[excessive quoting removed by server]
On Wed, May 30, 2018 at 1:20 AM, Fernando D. Bozzo fdbozzo@gmail.com wrote:
I think that a CMS could be an option
ION, everything on the internet is a CMS ;)
Not to disagree with you, Fernando, but just to ask if you had a specific product in mind.
A CMS primarily designed for chronological journal entries is a blog, A CMS primarily focused on managing a web of editable information is a wiki A CMS primarily focused on managing uploaded documents and their changes is a document management system.
And many products combine these things, as in some sense, these are just different views of the same data, as browse and edit screens are two views into the same data.
One of my faves for development use is RedMine (https://redmine.org/). It has a wiki, a document upload/download, a bug tracker and links directly to your source control provider of choice (SVN, CVS, Git, Mercurial and Bazaar) as long as that choice isn't MSFT. It lets you set up multiple projects and limit access to projects by login account. Best of all, it comes in an easy-to-use Ruby environment! (Highly recommend you find a VM image to run if you're not a Ruby goo-roo.)
Really, any basic wiki will do, given the general question and lack of specific needs. You can shop at cmsmatrix.org and be overwhelmed by too many choices, or start with your chosen platform and language and narrow it down to a few.
A simple IMAP server should do, one that supports shared mailboxes. Basically, you can run a BBS or web-forum with it.
On Tue, May 29, 2018 at 9:23 AM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Not a good option for this nationally shared information vehicle.
On 2018-06-02 05:38, Man-wai Chang wrote:
A simple IMAP server should do, one that supports shared mailboxes. Basically, you can run a BBS or web-forum with it.
On Tue, May 29, 2018 at 9:23 AM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
On 2018-05-29 12:23, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Would appreciate your thoughts.
Thanks, --Mike
I'm told by our SalesForce people that they have a product called Chatter that would probably work well for our needs. Just FYI in case anyone is looking for something like this, or if anyone has used Chatter and can comment on it here???
tia
Mike,
Are you just focused on collaboration or are you looking to build a sustainable knowledgebase?
We looked at Chatter - its a cool tool - but went the route of a wiki because our goal was not only to collaborate, but to build, as an internal community, a shared knowledgebase of re-usable content. We went with Confluence as a hosted wiki and are happy with the results. Not sexy but works well ... kinda like those of us on this list?! Anyway, a repeat endorsement for Confluence. Highly recommended.
Malcolm
On 2018-06-15 13:00, Malcolm Greene wrote:
Mike,
Are you just focused on collaboration or are you looking to build a sustainable knowledgebase?
We looked at Chatter - its a cool tool - but went the route of a wiki because our goal was not only to collaborate, but to build, as an internal community, a shared knowledgebase of re-usable content. We went with Confluence as a hosted wiki and are happy with the results. Not sexy but works well ... kinda like those of us on this list?! Anyway, a repeat endorsement for Confluence. Highly recommended.
I'd say this is mostly for collaboration and timely information sharing moreso than a sustainable knowledgebase.
On Fri, 15 Jun 2018 at 18:00, Malcolm Greene profox@bdurham.com wrote:
Mike,
Are you just focused on collaboration or are you looking to build a sustainable knowledgebase?
We looked at Chatter - its a cool tool - but went the route of a wiki because our goal was not only to collaborate, but to build, as an internal community, a shared knowledgebase of re-usable content. We went with Confluence as a hosted wiki and are happy with the results. Not sexy but works well ... kinda like those of us on this list?! Anyway, a repeat endorsement for Confluence. Highly recommended.
We also use Confluence extensively.
We even use it for our help pages. Messing with CHM files gets old fast. I added a property to all UI controls which contains the short URL (or part of it anyway).
-
Dave Crozier -
Ed Leafe -
Eric Selje -
Fernando D. Bozzo -
Fred Taylor -
Malcolm Greene -
Man-wai Chang -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Paul Hill -
Stephen Russell -
Ted Roche