Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

announce the new system #3419

Closed
chadwhitacre opened this issue May 14, 2015 · 22 comments
Closed

announce the new system #3419

chadwhitacre opened this issue May 14, 2015 · 22 comments
Milestone

Comments

@chadwhitacre
Copy link
Contributor

Reticketing from @webmaven at #3390 (comment).

@chadwhitacre chadwhitacre added this to the Pivot milestone May 14, 2015
@mattbk
Copy link
Contributor

mattbk commented May 14, 2015

Includes updating the front page at all?

@ehmatthes
Copy link

Includes updating the front page at all?

It has to; Gratipay needs to pull people in, both project leaders and potential funders.

@chadwhitacre
Copy link
Contributor Author

+1 from @kaguillera on #3428:

I suggest apart from answering this comment/thread/issue directly that it should be emailed/posted/blogged/tweeted/etc somewhere so that users like myself know what is going on.

@chadwhitacre
Copy link
Contributor Author

I put up a simple notice in #3452. This ticket is for a proper blog post.

@chadwhitacre
Copy link
Contributor Author

Here's a draft: https://medium.com/@Gratipay/2453d3c53077 (still very much in-process).

chadwhitacre added a commit to gratipay/inside.gratipay.com that referenced this issue May 20, 2015
With Gratipay 2.0 (gratipay/gratipay.com#3419), we are taking a more proactive approach to our community. It's fitting, then, to change the verb in our mission from "enable," which we adopted because of its laissez-faire implications, to something stronger. I am choosing "cultivate" because I like the organic and agrarian overtones (as opposed to, e.g., "build" or "create" or "develop"). Thinking of our work as cultivation recognizes that Gratipay has a life of its own, and implies that we see ourselves as proactively yet carefully and sensitively shaping the direction this life takes in such a way that helps it to reach its fullest potential.
@chadwhitacre
Copy link
Contributor Author

Blocking on:

@webmaven
Copy link
Contributor

Left some feedback on the draft.

@chadwhitacre
Copy link
Contributor Author

Thanks! :)

@chadwhitacre
Copy link
Contributor Author

#3458 is too much work to get done before tomorrow. :-( I'm striking it from the punchlist.

@chadwhitacre
Copy link
Contributor Author

Ready for final review: https://medium.com/@Gratipay/2453d3c53077.

@clone1018
Copy link
Contributor

@whit537 Every team link in that post 404's for me.

@chadwhitacre
Copy link
Contributor Author

@clone1018 Yeah, pending #3464—added to punchlist.

@chadwhitacre
Copy link
Contributor Author

Outta time. :-(

I'll be back later tonight ...

This was referenced May 21, 2015
@chadwhitacre
Copy link
Contributor Author

Okay! We have PRs open for #3432 and #3456. Once we land those we can give https://medium.com/@Gratipay/2453d3c53077 a once-over and then publish. Then we can follow up with lots of users who are waiting for this post.

This was referenced May 21, 2015
@chadwhitacre
Copy link
Contributor Author

@chadwhitacre
Copy link
Contributor Author

@chadwhitacre
Copy link
Contributor Author

I followed up with everyone in our support queue and in my private email.

@webmaven
Copy link
Contributor

Was the feedback I gave on the post helpful or just distracting (I can't see what I said anymore, or if you responded)?

@chadwhitacre
Copy link
Contributor Author

@webmaven Helpful! I believe I incorporated all or almost all of your suggestions, though further editing may have obscured that.

@chadwhitacre
Copy link
Contributor Author

Reopening to send an email blast. We did this for "Gratipocalypse", so we should do the same for "Gratipay 2.0" to maintain parallelism.

@rohitpaulk
Copy link
Contributor

We did this for "Gratipocalypse", so we should do the same for "Gratipay 2.0" to maintain parallelism.

+1. A friend of mine asked me whether Gratipay is still processing payments, coz he 'didn't receive an email after the Gratipocalypse one'

@chadwhitacre
Copy link
Contributor Author

Done in #3510.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants