Replies: 35 comments 84 replies
-
Beta Was this translation helpful? Give feedback.
-
I like the idea of having a logo for fpm. Some technical details on the fortran-lang logo for anyone giving this a try, the color is |
Beta Was this translation helpful? Give feedback.
-
Thanks @aslozada, I agree some branding is required for fpm in the long term, starting with a logo. I'd recommend introducing some noticeable distinction between the branding of fpm and that of the parent organisation Fortran-Lang; specifically by using a colour variation/combination and/or by using a different font. My preference would be to adopt a lowercase non-serif font to emphasise the modernity of fpm. Also worth considering with logos:
I think we should keep this discussion going and invite people to submit/discuss their ideas over time. fpm is still quite young and so there's no need to rush the branding at this stage IMO. Below are some rough concepts I started last year using colour and font variations, but I didn't have time to pursue them further: |
Beta Was this translation helpful? Give feedback.
-
About the creation of another build system logo: |
Beta Was this translation helpful? Give feedback.
-
Designing logos is not my area of expertise, but I like the box logo above.
However, I would combine it with the font used by the Fortran-lang logo,
only in lowercase. Just a few cents, slightly less than 2, I'd say.
Op di 9 mrt. 2021 om 10:49 schreef Vincent Magnin <[email protected]
…:
About the creation of another build system logo:
https://nibblestew.blogspot.com/2019/02/mesons-new-logo-design-process.html
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#380 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN6YR5XI3XUQTB25WPQFGDTCXVJPANCNFSM4YYX7IMQ>
.
|
Beta Was this translation helpful? Give feedback.
-
A logo without boxes. |
Beta Was this translation helpful? Give feedback.
-
A logo with a Penrose triangle? (or square) |
Beta Was this translation helpful? Give feedback.
-
Opinions may vary, but anything that helps you Develop, Build, and Share Fortran-based projects is in scope. The building components are already powerful; with the biggest issue being allowing compile and load options that let you incorporate Coarray, OpenMP, MPI, CUDA, and the many special-purpose load and build requirements in a format that supports packaging. The major development capability is currently the ability to incorporate external dependencies. Sharing primarily relies on github and the nascent repository and package searching via fpm-search. Anything that helps development (stdlib (especially via an fpm package), preprocessors, document generators, interactive Fortran, ...) is fair game IMO. Improving the quality of development (unit testing tools) and hooks into spack, jenkins, Cmake, meson, apt-get, ... packaging seem reasonable. Improving the ease that you can use debuggers, profiling tools, coverage tools, optimization, ... seems like a noble goal. I thought I saw a "Mission Statement" somewhere but so far the growth has been largely organic and concentrated on implementing in Fortran the basic capabilities of the Haskell fpm version and the basic functionality of other source package managers (Cargo, meson, pip, ...). There has been enough basic functionality to do that there has not been much discussion about what not to do but something as broad as "Facilitating Fortran-based program development" does beg questions, I suppose. There are several other Issues concerning a project plan and related issues such as developer documentation that have started to firm that up. |
Beta Was this translation helpful? Give feedback.
-
Thank you all for the creative ideas and effort. My comments:
|
Beta Was this translation helpful? Give feedback.
-
Personally, I like to imagine If the box in the first concept image of @LKedward was full of punch cards that would be a nice a tribute to the history of Fortran. I should note that @awvwgk is already using a punch card logo for his toml-f package. |
Beta Was this translation helpful? Give feedback.
-
I think the packages most universally liked are gifts, especially when delivered by hand from a close friend or family member. A celebratory gift would often be wrapped in a ribbon tied in a bow. The following sketch demonstrates these basic concepts: Possibly someone can draw it better. |
Beta Was this translation helpful? Give feedback.
-
Combining some ideas presented here |
Beta Was this translation helpful? Give feedback.
-
With all respect, please, no punchcards. Also this. 🙂 |
Beta Was this translation helpful? Give feedback.
-
I would prefer that any logo you end up with not be too similar to the one I am using. It was indeed inspired by the DVF logo. |
Beta Was this translation helpful? Give feedback.
-
I liked @LKedward's cube. Here's an idea with putting the letters on the cube: Not super wild about it though... [note to self: Inkscape Extensions -> Modify Path -> Envelope was how I got the letters to skew to the cube sides.] |
Beta Was this translation helpful? Give feedback.
-
The idea came up to include one of the logo drafts in the FortranCon talk to get feedback or encourage people to contribute their vision of an fpm logo. What do you think? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Concept 2a Concept 2b |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I like all of the logos that play on the "package" metaphor. This issue was posted ~7 months ago and has generated 24 comments and 41 replies. Hopefully that's enough time and feedback for a decision. Is there a process for deciding? |
Beta Was this translation helpful? Give feedback.
-
@rouson I tried to include a bow in the design 2a but that does not work well with the other elements. It is probably best to keep the "package" metaphor subtle, even if it means it is less visible. concept 2d |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
A little difficult to reduce to a small icon, I'm afraid (a necessary feature). It would make a beautiful cover for a Fortran book though. The symbolism is great but even though I have used fifty-year old Fortran code without alteration 1 300 years is a high hurdle to match! I would bet anyone who has stood there on a misty morning watching the sun come up would be inspired to be optimistic though. |
Beta Was this translation helpful? Give feedback.
-
You may be interested to discuss "Choosing a license for logo and other artistic assets" here: |
Beta Was this translation helpful? Give feedback.
-
I created a version of the 2a concept with a bit more color: |
Beta Was this translation helpful? Give feedback.
-
Can we finalize this logo? It's time. |
Beta Was this translation helpful? Give feedback.
-
To put the logo in practice, I made some banners examples. Some are in monochrome and some with color, following the idea of @awvwgk. Monochrome: Color: I wish this will help to decide! |
Beta Was this translation helpful? Give feedback.
-
I edited the banner as requested. After a few trial I also made a slight modification of the bow to make it look more like a bow (only visible at larger scale). Let's confirm the version below and finalize if it works for you. |
Beta Was this translation helpful? Give feedback.
-
I prepared the files. Please find them here fmp-1984logo.zip. |
Beta Was this translation helpful? Give feedback.
-
@1984logo We have moved all the assets of fortran-lang into a centralised repository https://github.com/fortran-lang/assets. Could you please verify the license of the fpm artwork you submitted? We have assumed that it's licensed under MIT, but please correct me if I am mistaken. |
Beta Was this translation helpful? Give feedback.
-
It will be nice to have a logo for the Fortran Package Manager.
This is a simple example,
I saw some logos of other package managers. These use a box or some type of packaging in their images.
P.S. I am not sure if this issue has been discussed.
Beta Was this translation helpful? Give feedback.
All reactions