Atom-script: Call for maintainers

Created on 28 Feb 2018 · 15Comments · Source: atom-community/atom-script

Hey all!

If you're seeing this you're either:

Already a maintainer
Perusing issues as a friendly person

I'd really like to have someone take the mantle on this package as I cannot lead it whatsoever with my current obligations. I've added a _lot_ of maintainers, no one to fully take it on though.

Here's what I'm looking for:

Become a maintainer by submitting fixes to the current code base
Make a release of the package, announcing it as an issue
Make another release, announcing it again
I'm transferring the package to you
🎉

🙇 Thanks for your help

help wanted

Source

rgbkrk

👍9 😄1

Most helpful comment

🚧 Is this repo looking for support?
Hello, we created this issue becuase the user @sospedra told us you are calling for maintainers.
✅ If you're looking for collaborators no action is required.
👮🏻‍♂️ If this repo is well-supported please put a comment here https://github.com/sospedra/rfm/issues/57 and we'll close it immediately.
Sorry for any inconvinience. We understand this message can feel spammy but we really think is good to double-check first with the current owners :)

rfm-bot on 2 May 2020

👍4

All 15 comments

Hello there, I'm not a maintainer but I just wanted to tell you that you can fix a small bug while running python code. Just change "python" to "py". It was changed to be like that

Jerated on 15 Aug 2018

I would like to be a maintainer of this code.

akaashhazarika on 6 May 2019

Great, in order to complete step 0 you'll need to make a PR and get it merged. Let me know when ready.

rgbkrk on 12 May 2019

@rgbkrk great foundation for a package! I have some improvements I'm interested in making soon and may be open to taking the package over if I find I have bandwidth.

In no particular order:

1) Switch to using Atom's config API to persist saved profiles instead of the serialization API, so profile edits are free. (#787)

2) Maybe clean up some of the backlog of issues? Or least close duplicates. 1,027 total at time of writing. (Maybe also get rid of createGitHubIssueLink? 😬)

3) Longer term, I'd love to maybe improve the environment variables profile section by:

a) letting it be a key/value table (e.g. see Postman query params interface) rather than a single KEY1=value1; KEY2=value2 text box, and
b) _maybe_... have a "Secret" checkbox next to each key that
- (i) switches the value to a hidden password-style field, and
- (ii) persists the value in the OS keychain using node-keytar. 🤔

Thoughts?

vergenzt on 12 Feb 2020

I have like zero time for this project and am fully on VS Code now, so I'm just plain happy to have others on top of this stuff. I'll take a look at your PR @vergenzt and add you on as a maintainer.

rgbkrk on 23 Apr 2020

Ah, that PR you linked wasn't yours. Please make a PR for any of the areas you're mentioning and we'll have you maintain after that.

rgbkrk on 23 Apr 2020

Please add input support for script

AlexThundrous on 25 Apr 2020

👍1

rfm-bot on 2 May 2020

👍4

@rgbkrk We are interested to maintain this repository. I am the owner of @atom-ide-community. I have sent you an invitation. If you can transfer the repository to @atom-ide-community, we will maintain it.