Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Communicate approval process and queue times #2022

Open
kontur opened this issue Jun 12, 2019 · 7 comments
Open

Communicate approval process and queue times #2022

kontur opened this issue Jun 12, 2019 · 7 comments

Comments

@kontur
Copy link
Contributor

kontur commented Jun 12, 2019

It is fairly hard to comprehend what the approval process and actual timeline for including new fonts in the Google Font library is. When looking at the issues there seem to be cases in which fonts have been pending addition and review for months without obvious reason or communication of schedules for inclusion.

While the diligence to make new additions adhere to quality standards is commendable I am wondering if Google could be more transparent on what are the issues behind the scenes that are stopping new additions. I am specifically talking about cases where the open issue does not give indication that something is still amiss with the sources, but that appear fixed and ready for shipping but simply hang in the queue. Sorting the issues by oldest or most commented there appear to be pages full of new addition requests which are not blocked but not added either, some open for years?

For a more concrete example: A design agency has a client that might be interested in financing the creation of a Open Source font for their own branding use with the prerequisite that it will be available via GF. As a type designer subcontracting for the design agency I can estimate my ability to adhere to various GF quality guidelines and procedures, yet I still can not give the client or design agency any confirmation that a font will find inclusion in the GF library and at what time frame. Obviously, that makes such a project impossible and a potential new font for eventual wider circulation will not get commissioned.

I understand that I am presuming technical fitness and adherence to GF standards, which often seem to set font projects back in the queue. Yet there are issues where seemingly the process is just on hold from the side of GF. Can you elaborate on this and how GF can be more transparent in this?

Or more concretely: If I have a font that qualifies under all the contributing guidelines what is GF’s promise response time window for inclusion in the catalog?

@m4rc1e
Copy link
Collaborator

m4rc1e commented Aug 21, 2019

Apologies for the delayed reply.

We spent the last year and a half improving our tooling. We now have automated tests and dispatching in place so it's much easier to approve families and push them into production. In the past two months, we've pushed over 50 updates. We aim to push font updates weekly. We are also actively working on the back log.

We recently just pushed Livvic which was commissioned by LV, a UK insurance company, https://fonts.google.com/specimen/Livvic. Since this family met our quality standards, we were able to push it within a week of clearing our QA process.

Darker Grotesque was submitted by a third party and pushed into production within two weeks since the author also met all of our requirements.

If you have a family and it passes our linter FontBakery and meets our general requirements, we'll try and push it within a two week window. This may not be possible if the engineers in the USA who are responsible for on boarding are away on holiday, sick or have other tasks which are more urgent. I will do my best to communicate whether we have any hold ups on our side if we do.

@santhoshtr
Copy link

santhoshtr commented Aug 21, 2019

@m4rc1e I am surprised to hear two weeks is the time window. For example, #1843 merged on May 8 and I don't see it in production. And you people stopped responding my emails too :(

@m4rc1e
Copy link
Collaborator

m4rc1e commented Aug 21, 2019

Added to our pipeline. Sorry it fell through the cracks.

@santhoshtr
Copy link

santhoshtr commented Aug 21, 2019 via email

@m4rc1e
Copy link
Collaborator

m4rc1e commented Aug 21, 2019

Sure thing

@santhoshtr
Copy link

@m4rc1e Once a font appeared in google fonts, How long it takes to appear in products like Google docs and ready to use by its users? I see that it took 3+ months for IBM plex. Is that still a reasonable expectation?

@kontur
Copy link
Contributor Author

kontur commented Aug 26, 2019

Great to see movement on this. I was expecting that fontbakery and other integration workflows are related to this and will to some degree alleviate this. I suppose what I am looking for is more of a general and public "integration promise" that is not documented in and depending on shout outs in a github issue. GF leverages the open source fonts in its repository for their service, so there should be an explicit, not implicit, promise to providers of such fonts. (cc @davelab6 )

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

No branches or pull requests

3 participants