Open oliverlalan opened 7 months ago
@emmamarichal I am not sure if you are the right person to contact, but I have seen that you are very active here lately, so... I hope you can answer a couple of quick questions I have:
No pressure! I know your backlog is packed. I just want to know about the process ☺️
Thank you!
hello @oliverlalan thank you for your submission! At first glance, this project looks great! I'm going to discuss it with my colleagues, and we'll try to get back to you in the next few weeks :)
Thank you so much @emmamarichal! After all the strange looks I've received for spending time on this, that "looks great" feels like a real victory😂
It is my first time working with fonts so, if there is anything else I can do to make the cut, just let me know. I'll be glad to work on your feedback.
After all the strange looks I've received for spending time on this, that "looks great" feels like a real victory😂
Do not be discouraged by "strange looks" from non-believers. This is a very cool font. Very retro, nice niche, and variable! People are going to love and use this font.
Pretty excited for this, hope it gets accepted soon :)
@oliverlalan @sos0 I am happy to say this is accepted overall, and I'm so happy to see the axes already conform to the Google Fonts Axis Registry :)
Since it is UFO based, I am assigning to @emmamarichal who is seeking an opportunity to learn how to onboard UFOs; the most common source is .glyphs but the new builder2 tool is expected to handle designSpace/UFO sources just as well, so this project may be a good opportunity for Emma to test builder2.
@oliverlalan To answer your questions directly,
How often are submissions reviewed / assigned?
This year we are doing more strict quarterly planning, so we are working to clear out the || Submissions label at least every 3 months.
Is there any way of knowing if a proposal has already been discarded?
Yes, the issue's || Submission
label turns to || Accepted
or the issue is closed :)
@davelab6 Yeehaw! I am so happy with the news! Thank you for the answers :)
@emmamarichal I don't know what the next steps are. So, I hope you can guide me through the process. I am not a typographer, nor a full-time programmer, but I am quite good following instructions, so just tell me what you need me to do, and I'll do my best.
A couple of things before going further:
Regards!
@oliverlalan "Doto" sounds nice to me, any objections @davelab6? :)
I'll let you know when I start to review it, and probably send you a list of what you need to do (I'll inspect if the font respect the specs of Google Fonts). But maybe that's good enough, and you'll hardly have to do anything :)
When the fonts will be exported and tested, these are the following steps:
I'll send you a email later, about all of this. But no rush, once the fonts are ready, it can several weeks before appearing on the API :)
I'll let you know, thanks again for this submission!
No, it sounds kind of like Noto
but its fine to use :)
@oliverlalan, I opened an issue with the review in the repo: https://github.com/oliverlalan/PixelPanel/issues/2
Cheers :)
@emmamarichal
Got it!
I'm having busy days, I'll try to work on the pending things this and next week.
Thank you for the feedback
Doto is such a good name :')
Can be moved in Q3 @chrissimpkins
@emmamarichal I already merged your commits. Please, let me know if there is anything pending from my side.
Hello @oliverlalan! We are still working on this name ID question, and we need to finish that before pushing the font to the API. Maybe I'll need to update again the name table. I'll let you know :) thanks!
@emmamarichal Hi, is the upstream label still relevant?
@sos0 Yes, it informs us that the process is still ongoing.
Font Project Git Repo URL: https://github.com/oliverlalan/PixelPanel
Super short description of the Font Family: A 6x10 bitmap-inspired font featuring two variable axes: One that controls the pixel size, and another one that controls the pixel roundness.
Requirements:
Google Fonts will publish only fonts that match its requirements. Please familiarize yourself with the complete documentation in the Google Fonts Guide (GF-Guide) and ensure your font project complies with them before submitting the font family. You can also use the Google Fonts Project Template, which will help you create a repository that follows the needed structure and includes build requirements.
By filling this issue, you can confirm the project meets the requirements (by ticking the cases or putting x between the square brackets in text mode):
Image:
![sample2](https://github.com/google/fonts/assets/62823573/193113b2-4aef-48e5-8a6f-ea88391ea05b)
Attach here a pic or a screenshot of the font. One image is enough, it can be a few letters, to give a quick overview.