Comment # 12 on bug 1203423 from Viktor Kov���cs

(In reply to Thomas Schraitle from comment #5)
> Thank you for your efforts, Viktor.
> 
> (In reply to Viktor Kov���cs from comment #0)
> > [...]
> > I grant this font:
> >
> > https://github.com/rovasiras/noto-font

Sorry, I wrote wrong link.


> This link gave me a 404, "Page not found".
> 
> Not sure why I got assigned to this bug. ;)
> 
> Apart from that, I have some questions (and maybe concerns). Let me address
> these:
> 
> 1. What do you expect?
>    Maybe I missed that part, but it's not clear for me. 
>    Could you clarify that?
> 
> 2. Why is the above GH repo NOT accessible?
>    Can it be that your GH repo is private?
>    Having a private repo, but a font released under an open source license
>    just don't work well together. It causes lots of problems, be it for you
>    and your audience:
>    * You exclude potential collaborators.
>    * You don't get any feedback as most people won't know how to contact you.
>    * You miss some cool automation features (although that can be done
>      also with a private repo. However, it can add additional burden.)
>    * People can't see any bugs and how they got fixed.
>    * People can't download different releases and the source code (very
>      useful for packaging).
>    * People can't check which is the current release (or in Git terms, what
>      was the published commit).
> 
> 3. Where are the consumable formats?
>    Publishing just the source code is not enough. Every font designer
>    publishes their fonts in an format consumable by users. That is mostly
>    OTF, TTF, or WOFF.
>    With all due respect, this is your responsibility. :)
>    (See also point 2 as you can do that automatically in GH.
> 
> 4. Where is "the project"?
>    Again, having just the source code is nice, but there are still some
>    things missing.
>    Those are not mandatory, but I think it would give a better impression
>    about your work. For example:
>    - purpose and goal of your work
>    - contact information
>    - a changelog of what changed in the font.
>    - a font spec, preferably in PDF. That contains all available glyphs,
>      some example sentences etc. so the reader gets an impression
>    - some additional meta information, like which languages does the
>      font supports, Unicode coverage
> 
> Maybe I missed some things, but it looks there there is no project, just a
> source code. Although I appreciate your efforts, maybe try to fix the above
> issues first and set up a correct project.
> 
> Hope that helps. :)