Parse-server: Feature request: Donations / Commercial Support

[markuswinkler]

Hi!

I am wondering if there are plans to add a donation site for the parse platform.
You guys put in a tremendous amount of time and love into this which is truly amazing
and much appreciated.
Truth though is everyone has bills to pay.
With some many projects out there relying on parse (and I bet a good junk of it
commercial ones) I think a call for donations to keep it alive is more than fair.
It would just be such a shame if people switch away from parse away because of longevity concerns.

As for the commercial support, I am thinking in the direction of linux and such.
The source code, support, fixes to the plattform and general questions is free
like it is now, but if you need custom code or someone to dig
through your code base for a fix it has a price tag.

Thoughts anyone?

[natanrolnik]

Hey @markuswinkler - there is already an Open Collective with existing donations: https://opencollective.com/parse-server

Commercial support is something that was talked about, but no real measures taken. Can you extend more on the direction you mentioned?

[markuswinkler]

Ah! Didn't know that (and I bet a lot of others as well).
I highly recommend to include this link in the readme.md for all parse plattforms/sdks.

Commercial support:
A lot of (semi) commercial platforms run on parse-server.
If there is a critical bug needed (or a feature request) a lot of
people who make money with their services would be willing to pay
for a quick fix instead of waiting for it to be solved by the community.
That should also take one of the core team a lot less time to implement than
any other developer since you are so familiar with the platform.

I would suggest the following approach:
Critical fixes:
critical fixes always go back into the public code base.

Feature requests:
Feature requests go on default back into the public code base immediately
or after x months on client request. (x something between e.g. 2 - 5 months).

I think this would be a very fair approach that also keeps parse server growing.

Curious to hear what others have to say about this.

[montymxb]

That sounds like a good idea, regarding the support/donate links on the SDK pages themselves. There are some people that may want to support us but use a hosted server solution, and as such may never look beyond the SDKs specifically.

[flovilmart]

we could add the open collective to all pages, as well as post install scripts on all our package manager scripts, something in the tune of:

Thanks for ❤️ing parse! Support us on Open Collective https://opencollective.com/parse-server

[markuswinkler]

Sounds like a good idea to me. Easy & non-obtrusive.

[flovilmart]

@markuswinkler would you be willing to chip in? adding some post install scripts to the node base projects, as well as the update in the readmes (based on this README, nametly shield at the top + backers/contribs at the bottom)

[dplewis]

@flovilmart This PR https://github.com/parse-community/parse-server/pull/3806 had postinstall script but it didn’t make it into the repo any reason why?

[flovilmart]

Because it added a dependency on the opencollective package and I’m not for adding non critical packages to production :)

[dplewis]

@flovilmart Would something like this work or is this too much?

[flovilmart]

hahah :) that's cute :) it's quite big but I like :)

[flovilmart]

we could put that script as a gist, and just curl it no? we could put that perfectly centered with tput cols and a bit of artithmetic

[montymxb]

That's in the right direction, but maybe something a bit smaller if it's
possible? A small terminal window might not even show that properly haha.

On Jan 16, 2018 07:48, "Florent Vilmart" [e-mail] wrote:

hahah :) that's cute :) it's quite big but I like :)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/parse-community/parse-server/issues/4498#issuecomment-358006081,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE1d4Ct_YpseNE_k4h2_d_kWFtIOZ73Kks5tLMTSgaJpZM4RduIZ
.

[dplewis]

@flovilmart If you can create a gist that would be great. We can always trim fat and center it.
This is about 50 column terminal.

opencollective-postinstall.sh

#!/bin/sh
UNDERLINE='\033[4m'
NC='\033[0m'
echo ""
echo "
                   1111111111
               1111111111111111
            1111111111111111111111
          11111111111111111111111111
        111111111111111       11111111
       1111111111111             111111
      1111111111111   111111111   111111
      111111111111   11111111111   111111
     1111111111111   11111111111   111111
     1111111111111   1111111111    111111
     1111111111111111111111111    1111111
     11111111                    11111111
      111111         1111111111111111111
      11111   11111  111111111111111111
       11111         11111111111111111
        111111     111111111111111111
          11111111111111111111111111
            1111111111111111111111
              111111111111111111
                  11111111111


        Thanks for installing parse 🙏
  Please consider donating to our open collective
      to help us maintain this package.

  👉 ${UNDERLINE}https://opencollective.com/parse-server${NC}
"
echo ""

[flovilmart]

I’ll create it :)

[flovilmart]

@montymxb @dplewis can you check that this command work?

sh <(curl -fsSL http://parseplatform.org/opencollective.sh)

[dplewis]

@flovilmart It works for me directly in terminal but not in a package.json

Edit: Wouldn't curl -fsSL http://parseplatform.org/opencollective.sh | sh be better?

[montymxb]

sh isn't necessarily available when using package.json. You can reference /bin/sh instead to reference it properly. A good example of this (but in ruby) is homebrew's installation.

[addisonElliott]

This is good to be closed, right?