Display some kind of monthly financial report on the website

[floehopper]

I'm sure you've already thought of this, @chrislo, but I think the sooner we can start doing this the better even if it starts off being very basic, because it will enhance our transparency credentials. Some initial thoughts...

• Publicly accessible or at least available to artists
• Some kind of summary (or anonymized details) of customer purchases, Stripe fees, jam.coop fees, payouts to artists, Wise fees, etc
• Some kind of breakdown of costs for 3rd party services, e.g. Render, Postmark, AWS, etc
• Some kind of breakdown of developer-hours worked on the project
• Maybe some kind of summary of the number of artists, number of albums, number of tracks, etc?
• Maybe some indication of traffic to the website?

[chrislo]

Oh, I *love* this. To start we could probably generate those figures by hand and update the report once a month? Just have a static site for now? On the site traffic front, I've been meaning to add some privacy friendly analytics for a while (plausible.io) and you can set their dashboard to be public I believe.

…

On Fri, 5 Jan 2024, 12:30 James Mead, ***@***.***> wrote: I'm sure you've already thought of this, @chrislo <https://github.com/chrislo>, but I think the sooner we can start doing this the better even if it starts off being very basic, because it will enhance our transparency credentials. Some initial thoughts... - Publicly accessible or at least available to artists - Some kind of summary (or anonymized details) of customer purchases, Stripe fees, jam.coop fees, payouts to artists, Wise fees, etc - Some kind of breakdown of costs for 3rd party services, e.g. Render, Postmark, AWS, etc - Some kind of breakdown of developer-hours worked on the project - Maybe some kind of summary of the number of artists, number of albums, number of tracks, etc? - Maybe some indication of traffic to the website? — Reply to this email directly, view it on GitHub <#127>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAECQYPH4WZ4JF6KEBCAZ3YM7W53AVCNFSM6AAAAABBOLQMNKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DOMRWHEYDMNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[chrislo]

A static *page* I mean.

…

On Fri, 5 Jan 2024, 13:01 Chris Lowis, ***@***.***> wrote: Oh, I *love* this. To start we could probably generate those figures by hand and update the report once a month? Just have a static site for now? On the site traffic front, I've been meaning to add some privacy friendly analytics for a while (plausible.io) and you can set their dashboard to be public I believe. On Fri, 5 Jan 2024, 12:30 James Mead, ***@***.***> wrote: > I'm sure you've already thought of this, @chrislo > <https://github.com/chrislo>, but I think the sooner we can start doing > this the better even if it starts off being very basic, because it will > enhance our transparency credentials. Some initial thoughts... > > - Publicly accessible or at least available to artists > - Some kind of summary (or anonymized details) of customer purchases, > Stripe fees, jam.coop fees, payouts to artists, Wise fees, etc > - Some kind of breakdown of costs for 3rd party services, e.g. > Render, Postmark, AWS, etc > - Some kind of breakdown of developer-hours worked on the project > - Maybe some kind of summary of the number of artists, number of > albums, number of tracks, etc? > - Maybe some indication of traffic to the website? > > — > Reply to this email directly, view it on GitHub > <#127>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAAECQYPH4WZ4JF6KEBCAZ3YM7W53AVCNFSM6AAAAABBOLQMNKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DOMRWHEYDMNA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[chrislo]

I wrote something for January '24 in d01bf29. This might be a good basis if we want to automate something or create some templates etc.