Hi there all Panopoly project maintainers :)

Our team is currently evaluating the possibility of making a large investment in time and energy into Panopoly project. Mostly in form of free contributions, such as suggested patches, documentation, and sponsorships without strings attached.

Community owned. Corporation owned.Something we find very attractive with Panopoly is the fact that the project, documentation and tickets/issues are all hosted on drupal.org. All Drupal users benefit from that. As you know Drupal.org is owned by you the users and the not-for-profit Drupal Association. Drupal.org is not owned by a Corporation.

Our question is, as project maintainers, do you intend to keep hosting the Panopoly project on Drupal.org for both D7 and D8?

Cheers,

Francewhoa

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Francewhoa created an issue. See original summary.

Francewhoa’s picture

Hi all Drupal contributors and users :) If you're reading this and you're not familiar with Community owned tools versus Corporate owned tools. Then you might be interested in the following.

Here are some benefits of hosting your project on drupal.org at https://www.drupal.org/node/648898

The following is the details version of what I mean by "community owned" versus "corporation owned" tools

In the following I'll use GitHub as an example of a Corporate owned tool. Github is owned by a Corporation. Compare to Drupal.org which is owned by you the community users and the not-for-profit Drupal Association (DA). The DA first priority is to serve you the users. Drupal.org is not owned by a Corporation. So no interference from Corporations. Corporations are really welcome but as contributors. Not owner.

Drupal.org forums first priority is to serve you the users. Github first priority is to serve their shareholders by hoarding money for them.

I suggest to Drupal users to consider using community owned tools instead of corporate owned tools. Because the first priority of community owned tools is to serve you the users ;)
- - -

Here are some benefits of community owned versus corporation owned

An increasing number of people realized that the Drupal community first priority is to serve you and all its users. Compare to Corporations, where their first priority is to serve their stakeholders. Corporations do so by hoarding money for their stakeholders. Yes serving the Community is often on a Corporation list of priorities but it's a much lower priority ;)

For example, when a Corporation is facing a challenging decision and have to choose an higher priority between:
• Option 1: Increase their profit/Hoard more money;
• Option 2: Serve the interest of the Community.

Then most Corporations will not hesitate to go with option 1. Hoarding money. One real practical example is tomorrow morning you could receive an announcement from Github saying that for now on you have to pay them money to access part of their services. Or announcing that they will provide part of your private information to third parties to increase their money hoarding. Or announcing that they will close their website because their stakeholders are unhappy with the amount of money hoarding. With a Community owned project you're protected against such behaviors.

As you know Corporations are really welcome in the Drupal community but as contributors. Not owner.

Corporations are not able to compete with the value of Community owned projects. Instead, they get value by both contributing to the Community owned project, and hoarding money via other channels. Conditional to not interfere with the Community decision making.

One clever action early taken by Dries, the founder of Drupal, was as early as 2001, to make the Drupal project Community owned. While at the same time welcoming contributions from anyone, including Corporations.

Sometime a website seem to be community owned because it uses wording such as "Creative Commons Attribution-ShareAlike (CC BY-SA)" or "Open Source". But if you search who owns that website you will find that it is owned by a corporation. Not owned by a community.

Here is the source that demonstrate that Github is owned by the corporation "GitHub, Inc." at https://en.wikipedia.org/wiki/GitHub

Source about DA being owned by a not-for-profit organization at https://assoc.drupal.org/about

Francewhoa’s picture

Issue summary: View changes
Francewhoa’s picture

Title: Keep hosting Panopoly on the community owned Drupal.org » Keep hosting Panopoly on the community owned Drupal.org?
dsnopek’s picture

Status: Active » Fixed

Of course, we'll keep hosting the project on Drupal.org! We have no plans to move Panopoly anywhere else. The D8 -dev version are already here.

We have a mirror of Panopoly on GitHub, but that's only to integrate with Travis-CI that we use for testing. We don't accept contributions there, only here. :-)

I'm sorry if we gave the impression anywhere that we were moving? If so, please let me know, and we'll make updates to remove any confusion.

Francewhoa’s picture

dsnopek :) Yay. Sounds great.

Having a mirror make sense. While keeping the primary hosting on drupal.org. So all users are free to use a tool convenient for them, which best fit their needs, and values.

I'm sorry if we gave the impression anywhere that we were moving? If so, please let me know, and we'll make updates to remove any confusion.

Thanks for expressing your concern. We never had that impression actually. I was asking because we committed to the folks we collaborate with to spend time, energy, and their budget wisely. Panopoly seems like a lovely project, friendly community, and a wise option.

We extended the same invitation and suggestion to various projects, such as Kalatheme. Which has some similarities with Panopoly. But Kalatheme declined, they are really not interested to host their project primarily on the community owned drupal.org They choose to primarily host it on the corporate owned Github. Oh well so it is.

I look forward to contributing to Panopoly. Assuming we reach a consensus with all fellows in our team.

dsnopek’s picture

Great! I look forward to seeing you around the issue queue. :-)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.