Open Letter, Maintenance, Project Adoption by @brushtechnology
nevercast opened this issue · comments
Hello fabricate!
This is an open letter to @SimonAlfie, @chriscz, contributors and fans of fabricate. My name is Josh Lloyd, I'm a software engineer at Brush Technology. I'm reaching out to the maintainers of this project on behalf of myself and Brush Technology. We use fabricate constantly at Brush, the company that developed fabricate originally; we love the project.
With the permission of the maintainers, Brush would like to help in maintaining this project. The project would remain the same, an open source community project, and our position would be in assisting with PRs, some fixes, and other maintenance tasks to keep the project alive. Brush Technology would be supporting me in this maintenance. Our hope is we can take some of the load off of the other maintainers who may be too busy to keep up with the abundance of pull requests and issues.
If you're open to this can someone please add me as a maintainer? Feel free to contact me at my Brush email, josh@brush.co.nz.
Kind regards,
Josh & @brushtechnology
Thank you very much for the add to the project @SimonAlfie , I look forward to working on this project. The community has been amazing maintaining fabricate all this time, and I hope my assistance will make it easier to keep the project moving forward.
I think the first step is get the repository to a stable state, so @chriscz if you want to go ahead and merge those changes sometime this week that's great.
Once everyone's local changes are merged upstream, I'll take some time to get familiar with the project state and then we go from there.
Cheers!
@nevercast I've taken a quick peek at my repository and it seems that I've already pushed all my changes!
Hello all, hope you had a great Christmas and New Years.
@chriscz The tests do not pass on Travis at this time it seems, do you know what is currently causing this? I would love to get that safety net back up, let me know if you've ideas regarding its failure. I can look in to it too.
Edit: Looking closer, the tests are being run against your personal fork. (Which is several commits behind). Let's get Travis on this repo. Do we need to also consider moving this repo to an org so that all org members can manage it? i.e. I'm not sure Travis will allow us to manage this repo's builds because its on a user account SimonAlfie.
What's the progress on this? Is there any interest in PRs to do things like link to the proper Travis for this repo (https://travis-ci.org/SimonAlfie/fabricate), fix the tests, etc, or is someone currently working on these tasks?
Hi @nevercast I'm not sure exactly why the tests fail. I haven't looked at this in a very long time, I did make some changes to the tests to make them a bit easier to use, but I'm sure I would've left them in the same state that I found them. And, yes, it will probably make more sense getting it moved to an organization. @palfrey I'm not sure, best wait for @palfrey to get it transitioned to an org, then work from there.
Hey all, I've a 3 week holiday coming up from the 1st of Feb so I'll be unable to make any progress during that time. @chriscz is right that we need to transition this to an org which is something only @SimonAlfie can do. I've allocated a team for Fabricate over at @brushtechnology if @SimonAlfie wishes to transfer it there. I can setup collab access and Travis and I should be able to get that done before I leave on Friday. Otherwise, @SimonAlfie you can transfer it elsewhere or wait until late Feb/March.
Hey Simon.
Here are the instructions on how to do the transfer:
I had assumed Github would ask me for confirmation before going ahead with the transfer, but it seems that isn't the case. You need write permissions on that organization to start the transfer. An unfortunate multi-step process, but go ahead and transfer to me if you can and I'll transfer to the org.
Josh.
Transfer done to your personal account @nevercast
Enjoy! :-)
We still use fabricate every day in our organisation, and will do for may year to come. Its a great tool.
Simon.
Thanks @SimonAlfie! We use it every day also, we hope to see the continued evolvement and adoption of the tool. It is great. I'll start the transfer to @brushtechnology now.
It seems somewhere in the transfer I lost my Super Admin Powers™. No fret, I'll talk with Github and get them to ensure all rights are preserved.
Update; I've contacted Github regarding this permission issue, will keep you up to date. Expect to be added to an Owners group in the near future.
Last update: All permissions should be as expected now :)
Can Travis get reconfigured with the new repo now?
Yes it can, if I've any free time over the next couple days i can set this up, but I'm actually away on my honeymoon from this weekend. @SimonAlfie and @chriscz should also be able to set this up if i don't get to it.
How's this getting on?
I'm still away for another couple days and can't get to this until after Monday 25. Sorry.
Sorry to be endlessly pinging this, but any progress on this? Alternately, if someone wants to add me as an admin, I can set this up myself...
ping @nevercast, etc. This looks like it's been moved, but the Travis link is still to the wrong repo.
ping Where are we on this one? Anything I can do to aid this?
Hey @berwynhoyt I've merged quite a few changes from @palfrey but could you please give him commit rights on this repository? I'm not sure when/if this project will get a maintainer but at least the community is keeping the wheels turning. I'm closing this issue in favor of #101
Happy to get commit rights, but odds are I won't get around to doing much more here any time soon as I've gained a lot of other things I'm working on as well in the meanwhile.
Thanks @palfrey -- I have given you commit rights now, so it's there if you need it, but completely understood that it may not translate into anything further at this point.
Thanks for all the contributions!