Giter Site home page Giter Site logo

inside.gratipay.com's Introduction

Build Status

Quickstart:

git clone https://github.com/gratipay/inside.gratipay.com.git
cd inside.gratipay.com
make run

Then: http://localhost:8536/.

You need python and make.

Deployment

Deployment of master to Heroku happens automatically from Travis. See also: .travis.yml.

Manual development setup

For Windows, which comes without make, you can create virtualenv, install dependencies and run it manually with:

virtualenv env
env\Scripts\pip install -f vendor -r requirements.txt
env\Scripts\python startapp.py

inside.gratipay.com's People

Contributors

0xibram avatar bmann avatar carols10cents avatar chadwhitacre avatar changaco avatar clone1018 avatar edoverflow avatar eswat avatar jessawitzel avatar kaguillera avatar krinkle avatar lode avatar mattbk avatar mlncn avatar patcon avatar peterdavehello avatar pjf avatar rohitpaulk avatar roryokane avatar seanlinsley avatar techtonik avatar timothyfcook avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

inside.gratipay.com's Issues

Brand guidelines

On /brand/ we should have documented brand guidelines around typography and colors.

User stories

After completion of #7 and #8 we should be able to start working through some sort of user stories that solve the needs of our users.

This is simply an issue to establish create these stories for the .com.

Process for handling nontechnical issues

We need a way to nicely handle issues that are of the nontechnical variety. When @juliepagano reported www.gittip.com#1683, it became painfully apparent that we didn't do very well with this. And #49 showed that we didn't really improve a heck of a lot (if at all).

The obvious first step is making the [email protected] email address more prominent -- but is there anything beyond that we should do?

I'm opening this issue here for the purposes of discussion, and will create an issue on the www.gittip.com repository once we decide on a final approach.

Policies for reigning in transparency

HI. DISREGARD THIS FOR NOW.

HIT SUBMIT ON THE WRONG ISSUE (currently writing like 5).


As was mentioned in #49 multiple times sometimes transparency can actually work against us.

We need:

1. A solid set of rules for when open vs private calls are preferred.
2. 

User advocates

An idea suggested by @juliepagano in #49 (comment) is having "user advocates."

Quote from her comment:

I think user advocates need to be people who are a bit more separated from the core structure of the company. Someone who is heavily invested can often feel the need to direct the user's conversations a certain way, take criticism personally, or even try to argue with the user. Think of doing user studies - it's often best when the developer of a feature doesn't run the study because they can be a bit too invested. Ideally, a user advocate is having a conversation with the user and learning about their wants, needs, concerns, etc. - they are listening and collecting information. They can then summarize that information, present it to developers, and advocate for changes that will value those users. It would be useful to have advocates who understand and have experience with the demographics you want to engage with (e.g. feminist activists, members of various marginalized groups, artists, OSS developers), so that they have a better sense of how to have meaningful dialogue with them.

Create webhook for notifying in chat of new issues/PR's

Setup details can be copied from here:
gratipay/gratipay.com#2115

This would help ensure that contributors in chat are not in the dark on conversations happening over building.gittip.com. A good safeguard, since design and dev are notorious for being fracture points in traditional orgs. Would be great to ensure there's some degree of cross-pollinating conversation :)

BG is confusing as a first impression

I linked to Mission from Gittip, Year Two, and got feedback on HN that the Mission page on BG is a bad place to start as someone exploring Gittip for the first time:

Same thing here, I had no idea about this site, so I click their mission from the article.

http://building.gittip.com/big-picture/mission

Well, that made it more confusing, so I click process at the bottom of the above page.

Now it sounds like it's a giant pool of money, anyone can volunteer for anything, and take some of that money. So, I can say I want to keep the elderly company and go play scrabble with them in the evenings, and take $10/hr from Gittip for my time? So, I visit the site directly to see if this is accurate...

https://www.gittip.com

Apparently not.

write policy for relating to media

I wrote a section about this on the Brand page:

We don't need the media at all. They need us. We're the ones doing something interesting enough to talk about, and if someone wants to talk about it, they're welcome to, but we don't need them and we don't owe them anything. We certainly don't depend on the media in order to communicate with our audience. We use Twitter, etc. for that.

If someone identifying with the media critiques Gittip, we welcome it and take it on board just like any other critique.

@patcon suggests at #10 (comment) that we need more work on this, so I'm ticketing it here.

fwiw, not sure I find the media section constructive:
http://building.gittip.com/brand/

To be honest, it comes across as pretty dismissive and self-aggrandizing, and seems to clash with the brand values we set out at the top of the page. It reads like it was written by someone who has had a bad experience. I would counter that not all journalists deserve the lack of respect that it seems to engender. It certainly doesn't seem like a voice I would claim as my own :)

using slack to organize a marketing / bizdev effort for gittip

Hi! I had a call with @whit537 this more and volunteered to do some work on organizing / scaling marketing efforts for Gittip.

So far, I've suggested that anyone that wants to participate in this effort join a new Slack at http://gittip.slack.com. You need to be invited by your email address and create an account, but then you can either use a Slack client or use the IRC gateway.

I'm just getting familiar with all of the moving pieces -- e.g. where do I go to try and self search / learn? Where do I sign up to help with support? In essence: how do I self-onboard with the Gittip team?

Allow easily moving between pages

Originally from @Aaron1011 at gratipay/gratipay.com#2342


Currently, there's no good way to move between different pages when you're reading http://building.gittip.com/.

For example, say I'm on the Brand Guidlines page. If I'm reading through the entire website, I'm want to go to Audience next, but there's no link on the Brand Guildlines page to do this.

I think the best thing to do is to have a button that says 'Next page', or possible the name of the next page, on each page of the website. This would make navigating between pages a lot easier.

Clearly document audience

We need to understand the two different types of user groups:

  1. Who is currently using Gittip
  2. Who we want to use Gittip

We then need to document who these people are, where they are, what they care about, and make them real.

Without a real understanding of the audience we don't know who we're designing for, what to say, how to say it, where to say it, etc.

process feedback from Camille B

I have a couple of pieces of (written) feedback from people. I am going to stick them in this issue for now, but something like using the Github wiki would be a much easier place.

[was "Where to put feedback?"]

Brand definition

We should clearly define the brand in accordance to goals and user perception. This is much more than just collecting assets.

On http://building.gittip.com/brand/ we should be able to outline the intended feeling of the brand. What do we want the audience to walk away with when reading/interacting with Gittip? This can manifest itself in the way of adjectives, emotions, or brand stories (or all of the above).

improve calendar

@patcon has been setting us up on Google+ and Google Calendar. We have a stubbed out calendar page. Let's make that more useful as the place to go to find out what events are going on in the Gittip world and how to join them.

do we want "Running Blah" or "Run Blah"?

For our Policy / Procedure / Process documents, do we want titles of the form "Running Blah Process" or "Run Blah Process"? Right now we have the latter. In #20 @pjf introduced the former. I standardized to the latter in 1e6c1a0, and am making this ticket to discuss.

Link to a style guide for CSS

Would be useful to have a convention going for CSS. Difficulty would be finding one with sane rules and works mostly with what we have already, so we don’t have to make a lot of changes to wedge into one.

The GitHub and mdo’s style guides come to mind right now, but by all means feel free to link to others that we can repurpose for our needs.

figure out how to ensure support coverage

Ping @pjf @patcon @bruceadams @clone1018 @seanlinsley et al.

Who is covering front line support this week? That's a question that I should know the answer to but I don't. Do we have an answer to that question already? Or do we need to come up with a process around this?

Assuming that you all aren't all ready on top of this, maybe we can use our Google Calendar and everyone takes a week at a time? What say you?

Add support processes

I'll be doing this soon, and I don't like making git commits without a ticket to associate them with. :)

Where does documentation such as this belong?

I am trying to put on the user's hat and trying to find out what I would expect not knowing the insides of gittip. I'd like to talk about user identification which does somewhat fall into IA but some might argue it is SA. It partially documents the current behavior and partially suggests some changes (maybe it is the equivalent of a PEP?) I have in mind a text such as this:

Gittip user is identified by an immutable numerical id that is currently unaccessible from the UI. The user can change its username which changes the url to get to the profile. Changing the username does not change the users identity.

Similar behavior can be seen on other sites, most notably Github, Twitter or Google (principle of least surprise). In addition Google provides immutable url exposing the internal id as well as the url based on the username.

When a gittip user (with immutable numerical id) tips someone using the /on/* pages, the intention is to give money to the person represented by that account. The user expects to see such an action represented in its history overview (events, audits..?). The platform and username of the receiver at the time the tip was initiated should be noted. If the receiver changes its name over time or its elsewhere account is attached to a gittip user id, the current info should be shown with a link to the current destination.

When elsewhere account is attached to a gittip user id, all tips associated with the elsewhere account should go to the governing gittip user id. However when the elsewhere account is detached again, all tips to this account should become hanging again (not claimed).

There is no principal reason why only one account from each platform should be allowed to be connected to a gittip user id.

The common property of an elsewhere account is the ability of its owner to prove the ownership. Therefore email, persona and similar fail under this category. However bitcoin address does not (unless there exist a way to prove ownership which I doubt).

fix edit/discuss icons

Turns out the free plan from IcoMoon times out project links after 24 hours. Probably easiest to just download from them and host the font files locally for now.

write a few user personas

Reticketing from #12 because I think user stories are more narrowly focused and worthwhile in their own right as a tool if we want to use them. We did some work related to personas in #7 and #8 but I think the "Audience" doc we ended up with is not pointed enough.

Personas are fictionalized one-pagers describing certain types of users. The purpose is to understand who we're building Gittip for. Insofar as we have sales and marketing people selling our product, then personas are a point of contact between sales/marketing on the customer-facing side, and design/development on the product delivery side.

I think the two personas we want to start with are:

  • Developer Evangelist
  • Open-source Project Owner

There are other ways to use Gittip (content creators, artists, writers, etc.), but let's not kid ourselves: Gittip's big win so far is funding for open-source, and we need to serve that market first and foremost right now.

Enable Wiki for Github

For now I think a good way to track general thinking is in Github's Wiki. This would be entirely unstructured.

I think this makes sense given that we're already using Github and the issue system for this project.

Heuristic Evaluation

We need to evaluate the existing site and determine what's good and bad based on current knowledge. This is a qualitative exercise to fully understand how the team views the existing experience and capture hidden requirements.

process feedback from User9812

Found at https://news.ycombinator.com/item?id=7844633:

Same thing here, I had no idea about this site, so I click their mission from the article.
http://building.gittip.com/big-picture/mission

Well, that made it more confusing, so I click process at the bottom of the above page.

Now it sounds like it's a giant pool of money, anyone can volunteer for anything, and take some of that money. So, I can say I want to keep the elderly company and go play scrabble with them in the evenings, and take $10/hr from Gittip for my time? So, I visit the site directly to see if this is accurate...

https://www.gittip.com

Apparently not. Ok, now I'm suppose to enter a Twitter username? This is to donate money to Twitter users? Still confused, so I click a random profile of someone receiving money. It starts to make more sense, so these are just people marketing themselves, and asking for weekly donations. The about page confirms this...

https://www.gittip.com/about/

Far too much work to figure out what's happening here. I still have no idea what I can donate money towards. I mean, how do I browse causes? If I want to support musicians, or people cleaning up garbage on their beaches, where do I go? I can't find any type of listings, or categories here. Is this just for programmers? I need to know their Twitter/Github username, or randomly click profiles on the site?

I give up, I've spent 20 minutes reading, and browsing this site, and my only conclusion is that it's a place to sponsor your favorite programmers, by giving them a weekly donation. I've been programming and freelancing for over a decade, and I can't think of anyone by name that I'd donate towards. This site gives me zero help in finding people to donate towards, aside from aimlessly browsing hundreds of profiles, hoping for someone to catch my attention. I don't have that kind of time.

This entire thing is too frustrating. I don't have a Twitter, GitHub, Bitbucket, or OSM account, so they won't even let me sign-up anyway. However, they say, 'Gittip's audience is everyone; it's intended to be a mass-market consumer product.'

http://building.gittip.com

Browsing the above, it looks like they spent way too much effort on over-analyzing everything. They have widgets, an API, browser extensions, but they're missing the most important thing, I working business model. It seems like the result of too many engineers and programmers in a room, while no one is spending a minute thinking about marketing, sales, or the user experience.

process feedback from Alex M

[Reticketed from #60.]

Alex M has volunteered to help out with Gittip marketing. He is a developer at a tech company that uses open source.

In terms of Open Source at my company:

  • Android
  • Apache Tomcat
  • Apache HTTP Server
  • Linux (Ubuntu)
  • MySQL
  • PostgreSQL
  • SQLite
  • PHP including CakePHP, Composer and several libraries
  • Javascript including jQuery, BackboneJS, RequireJS and several other libraries

I'm sure there's more there that I haven't covered.

One thought I've had while testing. Gittip is usually setup by a developer "after the fact" - once they've released a repo which people find popular and useful.

An idea already touched on by several projects on Kickstarter and Indiegogo - such as Light Table http://www.lighttable.com/ - is crowd funding but I believe that Beacon Reader https://www.beaconreader.com/ provides a much nicer concept which would be easy to follow.

  • A developer create a Gittip project.
  • Several support tiers are created "Gold Tier, Silver Tier, Bronze Tier etc" - each with their own payback - Gold perks get first access, joint developer access to the git repo etc, Silver gets the first alpha, Bronze gets beta etc etc. Perhaps even the twist on this model is there is always a $1+ tier.
  • Developer is aiming to get recurring funding - not 1 off payments, so $5 a week/month to work on this project
  • Once they get to their target, the funding strategy is kicked off - so if I back a project I'm immediately charged $5 a week/month on the day of funding, and then every week/month thereafter.
  • Each developer signs up to a "manifesto" where they draft up a brief agreement e.g. delivering X hours work, fixing 5 issues, or reviewing 3 Pull Requests on this project per month / quarter. If they fail to meet the target they set themselves, backers can elect to suspend all funding through an arbitration process on Gittip.
  • Call it "We the Backers" - where backers contact Gittip if the project is dying a slow death, so the money can be halted, or put into Escrow. While in Escrow the money could sit in the Gittip account earning interest.

Guidelines and rules for communication

As @whit537 mentioned in #49 (comment), there are four main areas where Gittip communicates with others:

  • Conversations we have with each other in the course of building Gittip.
  • Conversations we have about our users.
  • Conversations we have with our users.
  • Conversations we have with our business partners.

We should come up with a set of guidelines and rules, including whether to use public or private communication, for each of these situations.

Tone and Messaging

I know @whit537 is going to roll his eyes at this!

But we should think about defining some high level suggestions for how Gittip communicates. While individuals may shine at times, Gittip as a thing should be consistent.

This is strictly a design requirement. Uniformed tone and messaging creates a consistent and therefore trustworthy user experience.

process Shanley's feedback

I had a conversation with Shanley on Twitter last night, in which she provided a good deal of feedback on "open companies" vis-a-vis marginalized people. I've collected her feedback here:

https://medium.com/building-gittip/2e39b7ed12d
                       ^^^ Raw tweets there, see below for a copy/paste edited for readability.

What do we need to learn from this?

[Posting in the BG repo instead of www because this is big picture. Since this is important and not everyone is watching BG yet, I'll post and close an issue in www as a notification.]

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.