This repository was archived by the owner on Sep 6, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 6, 2021. It is now read-only.
Post-Adobe future : maintaining a new fork? #15333
Description
Forking the discussion in issue #15329 into one focused on the following question : is there anyone within the Brackets community who's willing to start a sustainable fork, and has the time, energy & skills to maintain it?
When I say "anyone", it's clearly not going to be a single person.
As users, are we willing to financially support that development (as much as we all can afford, of course), after years of using this Adobe-backed project for free?
(I'm just starting the discussion, not offering to start that fork)
Activity
killerog commentedon Mar 15, 2021
I wouldn't mind paying for Brackets, definitely if I could get some support why brackets has trouble starting up sometimes when windows 10 first starts ;-)
Same as everyone else though, no idea how brackets is build currently.
moeenio commentedon Apr 5, 2021
One man can't continue the effort of 100s of contributors, backed by a large company.
rafalkrupinski commentedon Apr 14, 2021
Obviously, it needs a group of maintainers, but someone has to start
Maniues commentedon Apr 18, 2021
I think it would be a good idea to submit brackets to various larger OSS communities like the Apache Software Foundation instead of trying to keep the project alive on your own.
However, if it doesn't then at least you need to make a copy of the repository and not a fork that doesn't handle issues and other features.
Maniues commentedon Apr 18, 2021
@fakerybakery
Apache Incubator from what I can see is a project where the whole community of a given program wants to enter Apache. In this case, it would have to look more like handing over OpenOffice to ASF. I will write to them if there is any option to accept such a project.
Maniues commentedon Apr 18, 2021
I sent an e-mail to Apache Software Foundation (apache@apache.org). As soon as I get a reply I will write here about it. Maybe I will publish full e-mail. ASF is currently the only possible idea that will keep Brackets alive at the moment. In fact, ASF is the only (or one of the few) chances of keeping Brackets alive.
Edit:
Creating a fork outside any foundation is possible, but someone would have to realistically take care of it, gather many people who co-created Brackets, look for people who did Pull Request, create one organization, and as we can see - no one is ready for such a step, especially, that Brackets is based on CEF (Chromium Embedded Framework), not Electron.js which means that for many people it is more difficult to understand Brackets and deal with it alone or with a smaller group. Therefore, Brackets needs a foundation to organize these people, find them, encourage them to participate, adapt a new server for add-ons, and relocate some of them. You can do it yourself, but for the new Brackets to work in the same way as Adobe Brackets, it would take months, maybe a year.
willnode commentedon May 9, 2021
So sad this unique editor will be abandoned. The live preview is very useful to me.
I created a fork and I've modified it a little so that it passes TravisCI build. Maybe I will tweak it a little over my free time to suit my needs. But I agree with @Maniues some orgs should have take over this project in order to get overall good support.
moeenio commentedon May 9, 2021
So that means no reply yet?
Maniues commentedon May 9, 2021
@locness3 I haven't received an answer yet. Today I will write whether the case is pending. If I don't get a reply within a week, I will write here about an alternative idea
PaulAtST commentedon May 10, 2021
That would be great if Apache could take over brackets. It would be a shame to see such a great tool go away.
moeenio commentedon May 14, 2021
@Maniues did you read the stuff over at https://incubator.apache.org/ ?
Maniues commentedon May 14, 2021
This excludes the participation of Apache Brackets. We don't want to join the project but get a fork from Apache
Maniues commentedon May 20, 2021
I didn't get any reply from ASF. I can write to Mozilla Foundation or to The Document Foundation. What you think about that?
flopezre commentedon May 29, 2021
Apache Brackets?
Maniues commentedon May 29, 2021
Please give like for Mozilla Foundation or rocket 🚀 for the document foundation
I will write to Mozilla or TDF tomorrow
moeenio commentedon May 29, 2021
I don't except the Document Foundation to be interested in this. However, Mozilla used Brackets as the basis for their now dead Thimble project. But I'm not sure they would maintain a "generic" fork of it.
Maniues commentedon May 29, 2021
@locness3 You're right that TDF may not be interested in this. However, I am afraid that Mozilla will want to make a strong integration with Firefox, leaving other things behind. But it's better than nothing, so I will write to Mozilla Foundation
bigrob1122 commentedon May 30, 2021
yogo1212 commentedon Jun 1, 2021
Hi :-)
TL;DR
https://github.com/brackets-cont/brackets
If you think you should be on the team, open an issue. Ideally, be someone who has contributed.
I'd say: This is a good opportunity to fork. Get away from the CLA.
It justs needs some organising.
Adobe was kind enough to place the emotional deadline in September.
De-facto there haven't been any commits since march.
The most that can be expected from this repo is to point to the fork in some way.
If a maintainer can put a link to the new repo in the description - wonderful.
I'm up for an adventure and willing to help organise a new project.
But i'm not really apt with HTTP/CSS so I will need at least some help for code review.
Here's a fork in a new organisation:
https://github.com/brackets-cont/brackets
The purpose of the organisation is to prevent Brackets to become a personal project. If you think, you belong in there, just open an issue in the repo!
These things have been or in the process of being done:
I've started collecting next steps here:
https://github.com/brackets-cont/brackets/projects/1
Please, join in!
I won't be doing it alone ;-)
Let's hope there's some genuine interest to improve behind the complaining to Adobe.
regards!
yogo1212 commentedon Jun 1, 2021
@willnode i had the audacity of just inviting you.
would you create a PR into https://github.com/brackets-cont/brackets from your repo?
willnode commentedon Jun 1, 2021
@yogo1212 will do it in a moment.
moeenio commentedon Jul 21, 2021
Is it too much to ask for an admin to pin this thread?
abose commentedon Aug 30, 2021
Hello everyone,
Just want to give a heads up on the Phoenix project to take brackets forward.
Phoenix brings brackets to native browsers with full extension support. Phoenix is free and MIT Licensed; based on the latest Brackets core and work done by the Mozilla thimble Project. Even though we have had web migration discussions in the community since the first days of brackets, it only became really possible with significant advances in browser capabilities from 2020(native fs access APIs, shared workers for IPC between Phoenix instances, virtualized node fs APIs in the browser). We have built phoenix for the web leveraging these. Phoenix will not have a native installable counterpart, unlike brackets-cont.
The builds are still in early alpha and can be tried out here: https://phoenix.core.ai/src/
We are working with devs involved with Mozilla thimble to update libraries part of the thimble project to the latest web technologies. Hopefully, we will be able to get native filesystem access working by September.
There are still a lot of essential features like live view, LSP support, node compatibility layer that are broken and are actively being worked on.
Requesting support from the brackets community for feedback, feature requests, and contributions.
Best,
Phoenix Team :)
#15373
Maniues commentedon Aug 30, 2021
@abose Thank you for forking brackets.
It would be nice if you provided a native version of Phoenix however.
Thanks to the @yogo1212 for forking brackets too.
abose commentedon Aug 30, 2021
Thanks for the suggestion @Maniues . Phoenix should be able to be hosted in an electron environment as we have migrated it away from brackets shell dependencies. But it should be able to provide all features that a native version does(including working on local projects) without any installs and directly in any device/browser. Will evaluate if a native version is needed once the browser port is complete.
Maniues commentedon Aug 30, 2021
@abose Thanks for replying. Development in browser can be uncomfortable for some people (including me), even more so if they do not program websites and web applications, but programs in Java, C # or C ++
xypd commentedon Aug 31, 2021
I actually welcome the chance to keep brackets in a portable form. I'd rather not use electron unless really needed. With that said, I agree that unless you keep a browser for just coding in, I think it could open the dev environment to random typical web slow downs and crashes.
I'm exited that this seem to be at least one viable path forward. And think it's smart to use the work others have done already. Cheers!