Roadmap

[kaosine]

For anybody reading this wanting to help out but unsure where to look, here's all the major repos undergoing change:

• Pulsar Core
  • We have a ton of modernizations they still need to be completed. Checkout our projects tab in the org, or the issues/prs that are current still open.
• Pulsar Documentation and website
  • Site is live, and we're trying to get it finished up with the basics. We could use a helping hand in refactoring and rewriting the archived docs as they're copied into their new home. Especially to get it updated with our current progress
• Atom Backend/API @confused-Techie 's repo, if you have any question for now ask him. More explanation below

Major Development Items (all these are in some form of progress as of right now but all could use some help here and there)

1. CI reliably functioning across all systems (We're on Cirrus for this!)
   1. We can build for linux and mac, but windows is being impressively stubborn.
   2. Whether it's bugs or otherwise here, we could use your help!
2. Continue upgrading Electron
   1. We're up to V12 right now thanks to a PR by Mauricio, but we're still behind farther than we should be
   2. Realistically, we should probably stay at least 2-3 versions with in the current release in the future once we are caught up. This would hopefully be the maximum limit
   3. Implement linux auto updates
3. Backend development
   1. Thanks to @confused-Techie we have a api going. But it could use some help getting up to speed.
   2. It needs some features
   3. This is also vital to some workflows like getting the auth token for github with viewing the packages, updating and modifying entries on there.
   4. Improve ppm functionality and keep it on the path
4. Website and documentation
   1. This involves bringing the documentation and the site back online DONE!
   2. The site needs to be a good landing point outside of the github for all the resources we have.
   3. The documentation needs to be refactored and finished (these have been pulled from the old flightmanual repo)
   4. Update branding - We have a our name, and possible logo, but we need to make sure everything is consistent.

Check our project boards for further updates!

[kaosine]

@pulsar-edit/core @pulsar-edit/documentation I'm bumping this since I know it needs some updates.

[kaosine]

Updated a few misc things I'd noticed if anyone wants to see if I missed anything. I'm not sure if @confused-Techie 's api has been brought over in a way that we can see it here. I also remember @autumnblazey was working on cleaning up repo's using branches to do so, not sure where the progress ended on that either. I know the pulsar-edit/flight-manual.atom.io repo needs to be archived however and added to that archival process.

[meadowsys]

The archive repo should be done

[kaosine]

So maybe you could talk to @confused-Techie or @DeeDeeG and start the process to transfer ownership to the org? I just want to bring this stuff up while I'm thinking of it since I know we had discussed it but never moved on it since the last mention.

[kaosine]

I've updated this again, but check our project boards for more up-to-date information!

[sertonix]

can this roadmap also include moving to neutal names. Like renaming the global atom and methods with atom/pulsar in there name?

[mauricioszabo]

This will break 100% of Atom packages, so no...

Like literally 100% - every Atom package needs to use atom.<something> to even register...

[sertonix]

I mean that the core is renamed but a build-in legacy package would provide the old api. If possible it would be included as dependency if a legacy package is loaded. To do this it would make sense to set env to pulsar for non legacy packages

[sertonix]

I still see places where it can't break anything if atom would be replaced in the name. For example in local variables. Can we have a neutral name like editor to refactor to?

[mauricioszabo]

Editor is fine with me :)

[sertonix]

The name core suggested by Spiker985 seems better

[Spiker985]

I guess if it's local scoping, it doesn't matter much. The global `atom` declaration should probably be something like `core` instead, when we get to that point. That would allow for `core.project.get*` or `core.getReleaseChannel()` and can't be confused with `TextEditor` instances

…

On Fri, Oct 28, 2022, 14:35 Maurício Szabo ***@***.***> wrote: Editor is fine with me :) — Reply to this email directly, view it on GitHub <#28 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3XPS4YQJ7TUCLZPXMLQKLWFQMFXANCNFSM6AAAAAAQ3GG7D4> . You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>

[sertonix]

Maybe add teletype to this list since it is very nice but hasn't been updated/rebranded yet.
A server exists but the api documentation seems to be missing.
Also it would be nice to make self hosting and custom domains user friendly.