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

Collaborators and/or converting to an organization #67

Closed
ryanoasis opened this issue Mar 14, 2016 · 22 comments
Closed

Collaborators and/or converting to an organization #67

ryanoasis opened this issue Mar 14, 2016 · 22 comments

Comments

@ryanoasis
Copy link
Owner

Debating converting to an organization or at least possibly inviting collaborators.

I would probably target starting with those who have already submitted PRs.

Any thoughts? Ping here if interested or have any suggestions.


I have not decided anything yet 😛 just jotting my thoughts down

@her
Copy link
Collaborator

her commented Jun 11, 2016

Hey @ryanoasis

I'd be happy to help. I'm taking a second to kinda catch up, I've been really busy with work and so I haven't had a lot of time to keep an eye on what's happened.

Is there any particular place that needs attention?

I noticed this issue discussing undocumented configuration. It would be good to get this added to the README and I can start working on that this weekend.

@ryanoasis
Copy link
Owner Author

@her Hey thanks 😄 . No worries, I've actually been very busy with work as well.

Particular? Not that I can think of. Anything that improves things I am open to 👍

For #152 I am not exactly sure there is a bug but probably options do need to be clarified in the readme.

I've been doing a lot of work on the readme lately, so if you want feel free to tweak things in the 0.8.4 branch

Thinking about making a collaborators only gitter chat or something as well.

I just thought it was about time I add some collaborators.. well the main reason just in case but also it is a good thing to do.

@her
Copy link
Collaborator

her commented Jun 12, 2016

Nice! Okay, got it. 🙂

As far as an Organization is concerned, were you thinking that would just make it easier to arrange the various repositories supporting the larger devicon concept? It may be beneficial to have them all organized in a central Devicon organization, with maybe a single point of release for users. Just kinda spit balling here 😄

Also, a collaborator gitter is a really good idea, I think. That way going forward it would be easier to just pop in to the chat and if people have been stating their efforts and work you can catch up efficiently.

@kierun
Copy link
Collaborator

kierun commented Aug 18, 2016

I would be willing to help… Although I am not sure how much help I would be ;)

@ryanoasis
Copy link
Owner Author

@kierun Cool thank you and yes I understand. I will take any help that is offered large or small 😄

@nogweii
Copy link
Collaborator

nogweii commented Mar 16, 2018

Bringing this up again, I think it might be worth it now.

@kierun
Copy link
Collaborator

kierun commented Mar 16, 2018

@ryanoasis I am been massively inefficient here. My apologies.

@ryanoasis
Copy link
Owner Author

@evaryont Yeah I think it's only inevitable at this point To be completely honest the main hold back is a very selfish reason, the other reasons after that are all just logistics and planning. I am not there yet 😞

@kierun You shouldn't have anything to apologize for! Glad to have you on board. 😄

@LuRsT
Copy link
Collaborator

LuRsT commented Apr 2, 2018

Hey @ryanoasis what can I do to help out with splitting this repo into just the patcher and something that builds all the fonts?

@ryanoasis
Copy link
Owner Author

Thanks @LuRsT I know this is a late reply. I'm thinking about this now again..

@ryanoasis
Copy link
Owner Author

This is a WIP, Organization was created a while back: https://github.com/NerdFonts

Next steps: adding collaborators, moving the website, the patcher, etc.

@her
Copy link
Collaborator

her commented Aug 13, 2019

@ryanoasis congratulations! 🍾

What’s next? How can we help?

@ryanoasis
Copy link
Owner Author

@her Thanks and thanks for all you were able to contribute.

Good question. I already added everyone who was already a collaborator here. I am not sure exactly what help particularly at this moment but I am completely open to any feedback/suggestions/PRs that make things easier/better/faster.

I don't see this repo going away anytime soon but my goal is to have the website and patcher at separate repos and maybe even removed from this repo..

@LuRsT
Copy link
Collaborator

LuRsT commented Aug 19, 2019

This is great, I'll do something when I got some time to spare regarding splitting the patcher from this repo

@ryanoasis
Copy link
Owner Author

I actually started on this but I wanted to preserve the git history of the patcher and relevant files, ran into some issues where I could see in git log but not github UI or something. This was months ago

@LuRsT
Copy link
Collaborator

LuRsT commented Apr 11, 2021

Are you planning to restart that work @ryanoasis ?

@ryanoasis
Copy link
Owner Author

Yep 😄 . Right now working on a release pipeline so we don't have to wait on one person to make releases.

I really would prefer to keep the git history of the files especially the patcher script

@TamaMcGlinn
Copy link

Using git subtree split or filter-branch you could keep only that history. The size of the repo will be much smaller if we don't keep all those binary diffs around.

@ryanoasis
Copy link
Owner Author

I am no longer in a big hurry to do this as I think providing the patcher (with all of it's required source files) in the release solves most problems, for example: https://github.com/ryanoasis/nerd-fonts/releases/download/2.2.0-RC/FontPatcher.zip

I'd appreciate any feedback though, also see: #716

@Finii
Copy link
Collaborator

Finii commented Jan 27, 2022

Additionally to FontPatcher.zip (which is excellent!) I believe a simple non-archive font-patcher script that fetches what it needs would further improve usability (#741).

@Finii
Copy link
Collaborator

Finii commented Jan 30, 2023

Closing this to clean up. Will be found via future tag.

@Finii Finii closed this as completed Jan 30, 2023
@Finii Finii added this to the The Future milestone Jan 30, 2023
@github-actions
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants