Open Collective budget / finding new contributors / strategy

#1

The Parse Platform Open Collective now has a balance of ~$9,500 but it seems that it currently has only been used to pay for this forum as I think @flovilmart was unsure what to do with it.

I thought it would be a good idea to start an open discussion for people to voice their ideas on how it could be used (to be clear I’m not a core contributor I’m just a user of Parse who would like to see it have a positive future).

Personally I was wondering whether some of the budget could be used to reward contributors for making pull requests (relative to the magnitude of the changes) and bug reports. I’m not entirely sure how this would be implemented in practice.

Perhaps this would encourage more contribution and contribution of a higher standard?

Any ideas or thoughts?

#2

Personally I’ve got invested interest in parse continuing to move forwards and am forever grateful to contributors for their work. It would be great to see them rewarded. Some swag / direct payment would be great, any sort of pat on the back :slight_smile:

1 Like
#3

Quick idea - after a contributor makes say 3 pull requests they get a thank you letter with a couple of Parse stickers.

#4

I agree that the existing core contributors deserve a ton of love but I think it is perhaps more important to encourage new contributors especially as we have just lost @flovilmart.

New contributors will make the future of Parse more sustainable and hopefully take some of the pressure off the existing core contributors.

#5

Another idea - we could have a community email newsletter (which could also go on the Parse Platform blog).

This could include:

  • Summary of recent changes + releases
  • Community highlight - thanking contributors
  • Help required - running list of things that need doing - bugs to fix, sections of docs that need updating

Perhaps such a newsletter could be sent out once a month or every two months?

1 Like
#6

Like this idea, although running a newsletter is a real pain, it takes some significant effort to keep it going for a long time. I think to attract more contributors there needs to be some sort of outreach to attract new users who are keen to contribute.

1 Like
#7

Fair point, with regard to outreach do you have any ideas as to what we could do specifically?

#8

Great question! I think that we first need to consider why people would choose Parse over another platform which most probably have an easier barrier of entry (i.e. Firebase). For example, would I have chosen Parse for my SaaS in 2019, rather than when I did make that decision 5 years ago when Parse was backed by Facebook. I’m sorry to say that I don’t think I would, I would be fearful of open source software without any large backing. I’m unsure if this fear is echoed elsewhere, or if it’s just my personal view. If it is echoed elsewhere then providing the reassurance that ‘Parse is still very much alive and a great option for you’. Moving forwards from that I can only think of having some really great tutorials (Wes Bos style) to give really clear direction on how people can setup their API etc.

As I type this, I’m thinking that those people who need a tutorial aren’t exactly those who are going to be diving into complex issues / PRs. However, if the base of the pyramid is wide then the community has enough critical mass to drive the project forwards and most importantly keep it alive.

On the other side of the fence there are a number of companies that have built their whole business on Parse (sashido, back4app etc etc). Surely they have invested interest in continuing to drive things forwards? Can we reach out to them to see if there are opportunities to reward / encourage / drive forwards?

With the industry going crazy over GraphQL, I’m unsure if there is a wave crest to be ridden with that, but i’m sure there is a significant amount of work to get a layer running with that!

1 Like
#9

I actually chose Parse in 2018 mainly because I don’t agree with the data privacy values of companies like Google (in the case of Firebase). I’m using Parse on Back4App because my experience is in iOS dev.

Whilst I’m not going to be diving into complex issues anytime soon I have made various contributions to the docs and now the Parse Platform website which will hopefully make Parse more approachable and appealing to people so I think there is definitely still value in inexperienced programmers etc.

Reaching out to Back4App and Sashido could be a good idea.

I’m not particularly aware of GraphQL but there is a pull request from @flovilmart to implement it on Parse Server - I’m not sure how far out this is or whether someone else needs to take that over.

1 Like
split this topic #10

7 posts were split to a new topic: Creating a roadmap

#13

Maybe step one is to share the news about @flovilmart departure - I for one thought he was only stepping down from the SDK support libraries, not the server itself. We should at least utilise https://blog.parseplatform.org to send a message of thanks and to drum up support to this forum, I don’t believe the main website has a link to this? I’ll open a PR now.

#14

Edit: sorry @TomWFox - Missed your PRs.

#16

I would be happy to put together a blog post detailing @flovilmart’s departure and the new community forum. I think it might also be good to add a section summarising 2018 for Parse Platform.

#17

the two things I’ve been thinking about tapping the open collective budget for:

  1. Penetration testing using hacker one or similar service.

  2. Maybe some marketing on twitter. It’s pretty cheap and our twitter handle only has 200 followers. I’d want to see more activity on it (thanks Tom-Fox1 for getting started on this already!).

I don’t really think that with just 10k we’d really be able to make much of a difference in terms of incentivizing contributions.

Personally, I think that rationalizing all of the documentation, discussions like this and then developing and posting a reasonable roadmap would go further to elicit contributions…

1 Like
#18

Hello guys,

I’m a rep from one of the companies mentioned above. (pls see my profile for more info). I joined this discussion because I liked the energy and the passion you guys are sharing about the Parse and the community. @flovilmart will miss to all of us, but I’m positive that he left the Parse platform is in good hands as well.

For us always was a great pleasure to share ideas and to help @flovilmart with everything we can. We are still all ears, so if we can help you with something please let us know.

Regarding future developments and strategy, I think that a good roadmap will be a great start because it will be much easier to involve more contributors and more sponsors.

Keeping the Parse hosting providers close to the community for me is a crucial task because they have a lot of feedback and requirements coming directly from the customers and developers building thousands of apps :slight_smile: but, of course, this is my opinion … the decision is entirely yours.

Thanks again for the passion and energy and I’m looking forward to the awesome contributions you’re about to make :slight_smile:

p.s. You can always chat with me in https://parse-opensource.sapp.io/ slack community. Please ask @flovilmart for admin access in this slack as well.

1 Like
#19

I think that running some twitter ads would be a good idea.

It seems there is plenty of agreement over having a roadmap - perhaps we should open a new thread so we can discuss this further e.g. who wants to take the lead on it? where should it be displayed/hosted? how should it be organised? etc

#20

Thanks for joining the discussion!

I agree that keeping close communication between the community and hosting providers is mutually beneficial - in my opinion it would be great to hear the feedback coming from your customers.

In terms of specific areas where we could do with help - the iOS SDK has seen better days and is still lacking a committed maintainer - I think that it would be great if we have a comprehensive Swift iOS SDK.

1 Like
#21

Twitter ads are super expensive and will be useless for awareness (you will spend the money super fast and will not have a good effect). The approach should be entirely different.

In my opinion investing in good articles, tutorials, howtos, boilerplates, SDKs and etc will generate more value, as well as organising meetups, participating events and giving talks.

If you create some of the things mentioned above that relieve a big pain of the developers I think it could become viral in lots of networks, because will solve a real problem and then could be boosted with some money for ads as well :slight_smile:

1 Like
#22

A Hangouts where all of this can be discussed will be a good start :slight_smile:

#23

Have you already thought about the future of parse? maybe this can give you some ideas.

For example, I have seen other technologies (Strapi, Hasura) and I think we can improve the dashboard to make it more usable and friendly for new users. The plugin system can be a excellent integration to parse-dashboard

Strapi plugins:

1 Like