Next steps for the Yarn repo

[desplesda]

Issue by desplesda
Tuesday Sep 17, 2019 at 04:17 GMT
Originally opened as InfiniteAmmoInc/Yarn#104

---

Hi, all.

As you may have heard, @InfiniteAmmoInc recently passed away. This has been a very difficult time for those of us who worked with him, and I'm grateful for those who reached out to me with condolences.

One of the difficulties surrounding his passing has been the fact that this repository on GitHub was one owned by Alec's personal account, which means that - as per GitHub's setup - he was the only person with the ability to administer the repo.

I'd like to make sure that Yarn remains a vibrant and useful project, and this repo has remainded under active development. As I posted to the Yarn Spinner repo, we are moving Yarn Spinner to a new organisation, @YarnSpinnerTool, in support of the plans we have for building out the Yarn ecosystem.

This morning, I had a conversation with @blurymind, who's been the most active contributor to the repo over the last year, to explore what we should do. I suggested that we fork this repo, and bring it over to the @YarnSpinnerTool organisation, to put this project under the same umbrella. @blurymind agreed to be an administrator of this new repo. The full git history of the repo will be preserved, and I'll do what I can to copy over the issues as well. The new repo will be hosted at https://github.com/YarnSpinnerTool/YarnEditor.

If you have any opinions about this plan, please share. This is an open source community and your input is crucial.

I'm also putting the call out to anyone who's been a contributor to Yarn to see whether you'd like to be given the same write or admin access as you currently have on the moved repo. We value you and your contributions and would love to have you stick around.

If you'd like to talk to me privately about this, my DMs are open on Twitter at @desplesda, and you can also email me at [email protected].

Thank you all for everything, and I'm looking forward to continuing the project with you. We're gonna keep being useful to people who want to make things.

[desplesda]

Comment by ScrapGames
Tuesday Sep 17, 2019 at 04:51 GMT

---

I'm activily using YarnSpinner with my current project and will continue to contribute as I see needed :)
I can't see that being often enough for the elevated priviliges however - I'm just happy to be part of the community :)

[desplesda]

Comment by blurymind
Tuesday Sep 17, 2019 at 17:39 GMT

---

I will continue to work on the editor and improve it. Especially now that it is about to get bundled with
https://github.com/4ian/GDevelop
and be a key feature of the engine - to be used by storytellers, who don't necessarily know any programming languages, but want to make a game.

The long therm plan is to make it bundable via npm. Hopefully hosting it under a subdirectory of yarnspinner won't affect these two future feature goals:

• hosting yarn's web build on its own github as a live webapp that runs in the browser and can be used by any device with a web browser
• registering it at npm as a library that other js developers can easily fetch and incorporate in their apps :)
  The facebook guys kind of stole our spot there:
  https://www.npmjs.com/package/yarn
  so I guess it will have to be registered there as yarn-editor or something like that

[julsam]

I haven't been active in months on this project, but I just wanted to say that I'm happy to see it's still alive and thriving. Nice work everyone! 😄
I don't see myself needing write privileges, I'm just happy to be here.

[ghhjklkljlkjlkjkl]

The https://github.com/YarnSpinnerTool/YarnEditor/releases link is broken and I cannot find anywhere else to download the yarn editor installer. It says there are no releases.

[blurymind]

The https://github.com/YarnSpinnerTool/YarnEditor/releases link is broken and I cannot find anywhere else to download the yarn editor installer. It says there are no releases.

We plan to setup some sort of a build process that automatically populates releases there. For now you have to either build the electron app manually or use the webapp

[FaultyFunctions]

This seems to have been inactive for a while now. I'm closing this since this has been resolved.