Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to improve communication between i) Piwik community ii) Piwik contributors iii) Piwik PRO contributors #8520

Closed
mattab opened this issue Aug 8, 2015 · 13 comments
Labels
answered For when a question was asked and we referred to forum or answered it. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. RFC Indicates the issue is a request for comments where the author is looking for feedback.

Comments

@mattab
Copy link
Member

mattab commented Aug 8, 2015

How can communication be improved between:

i) Piwik users community
ii) Piwik contributors
iii) Piwik PRO contributors

In private discussions and during the Piwik meetup in Berlin, this topic was raised several times by key contributors. One challenge is that Slack is being used by Piwik contributors, and another Slack account is used by Piwik PRO contributors.

Maybe there is for us a possibility to:

  • merge both Slack into one,
  • have some chatrooms made completely public (eg #dev-core),
  • open a new support channel that will be completely open (eg. as Wordpress has done WP Slack, WP Comm discussions
  • document Slack<>IRC relay (as IRC is a communication standard)
@mattab mattab added the RFC Indicates the issue is a request for comments where the author is looking for feedback. label Aug 8, 2015
@sgiehl
Copy link
Member

sgiehl commented Aug 8, 2015

+1 for merging slacks and making it public.

@MagicFab
Copy link

MagicFab commented Aug 9, 2015

I believe Slack should not be used here as it is a proprietary SaaS service and this in incoherent with Piwik's mission and values.
Other alternatives that may be more coherent to use may need some testing and evaluation, I know for example about https://rocket.chat ( see https://github.com/RocketChat/Rocket.Chat#features ) but there may be other better alternatives.

@gaumondp
Copy link

I don't think using Slack is incoherent. It's as incoherent as using the proprietary IDE PhpStorm for coding...

TYPO3 community has 109 channels on Slack and it just works fine.

That's my 0.02 canadian dollars opinion

@quba
Copy link
Contributor

quba commented Aug 11, 2015

+1 for public slack

@mattab mattab added this to the 2.15.0 milestone Aug 13, 2015
@MagicFab
Copy link

@gaumondp yes, I agree using a Free as in freedom IDE would be better, I suggest you open a bug report about it.

If the Typo3 community has a different set of values I don't see how that is relevant here or how it should make Slack use coherent with Piwik's own values.

I'll re-state the obvious, whenever the Piwik community is required to use tools and SaaS that go against such values in order to contribute, instead of valid existing alternatives, it is in fact incoherent with such mission and values.

We should at least consider an alternative and evaluate the feasibility of moving to it.

@mattab mattab modified the milestones: 2.15.0, 2.15.1 Aug 17, 2015
@mattab
Copy link
Member Author

mattab commented Aug 17, 2015

What are your thoughts on improving forum discussions?

It was suggested by a few community members that we could use a more modern forum software for the Piwik community, in particular http://www.discourse.org/ was suggested as an alternative to our current phorum-based forum.

Examples of other discourse forums:

What do you think about this?

@mnapoli
Copy link
Contributor

mnapoli commented Aug 17, 2015

@MagicFab Piwik uses many proprietary tools for its own development. A good example is GitHub.

Modernizing the forum would be great, Discourse is awesome.

@quba
Copy link
Contributor

quba commented Aug 17, 2015

+1 for public Slack and Discourse.

@MagicFab
Copy link

@mnapoli I know, it's not the topic here, though.

@mattab +1 on Discourse, it may be important to look at possible SSO setup to simplify contibutor's login to this and other tools.

@mnapoli
Copy link
Contributor

mnapoli commented Aug 17, 2015

@MagicFab I'm sorry, I'm probably missing it then :/

I'll re-state the obvious, whenever the Piwik community is required to use tools and SaaS that go against such values in order to contribute, instead of valid existing alternatives, it is in fact incoherent with such mission and values.

What is the problem with using Slack which isn't a problem when using e.g. GitHub?

@MagicFab
Copy link

@mnapoli AFAIK GitHub is not contributing to miscommunication issues, however I agree it's also problematic (for example it's restricted to 13 y.o. and +, you can't have more than 1 account, etc.). I am not involved in development, perhaps those who are will want to elaborate on that. It would certainly be useful to know more details on what you think.
Reading from the top I a realize I assumed this was about forums + chat only.

@mattab
Copy link
Member Author

mattab commented Sep 10, 2015

Good news: some progress has been made on testing Discourse for Piwik forums! See Migrating Piwik forums to use Discourse #8747

(opening Slack to the public is still planned, but I prefer to focus first on Discourse migration as it is more important. will get in touch with Slack for more details, after Discourse migration is successful)

@mattab mattab modified the milestones: 2.16.1, 2.16.0 Jan 10, 2016
@mattab mattab modified the milestones: 3.0.0, 2.16.x (LTS) Apr 1, 2016
@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Apr 1, 2016
@mattab
Copy link
Member Author

mattab commented Jan 2, 2017

Not working with Piwik PRO anymore so closing for now.

@mattab mattab closed this as completed Jan 2, 2017
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Jan 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. RFC Indicates the issue is a request for comments where the author is looking for feedback.
Projects
None yet
Development

No branches or pull requests

6 participants