LOOKING FOR MAINTAINERS/SUCCESSORS

[aviaryan]

[AutoHotkey forum follow-up]

Hi.
I just want to say that I am now on MacOSX and therefore will not be able to continue development. Therefore it will be great if anyone can pick up this project. ..

How to continue this project?

1. Your own fork

Clipjump is an open source project under the Apache v2.0 license. Under the license terms, you are free to create a fork of this project and develop it.
But it should always respect the original source and provide credit to this project wherever necessary.
You will have to choose a project name (Clipjump2, ClipjumpX, ClipFly ..etc works) different than Clipjump and also use a different website.
Clipjump's real repository and website may link to your fork in case it has improved considerably over Clipjump.

Note - I will not have a special say on your project's matters. If your fork is good, then only I will link it on the Clipjump's original website.

2. Working under this project

We can also work on developing Clipjump under this repo.
The current master branch will be renamed 'legacy' and a fork of master's will become the master where development will happpen.
Clipjump's website will host the new fork as well as the legacy, and after some great improvements, hopefully we can remove 'legacy' Clipjump from the website.

---

Please provide your proposal as a different issue on this repo if you want to work on this project. It should answer questions like --

1. What do you want to do?  ---- Fork or Work on this repo
2. What prior experience do you have in AutoHotkey? Write with examples.
3. What is your relationship with Clipjump?
4. What are the features/bug fixes that you would like to add ASAP when you start working on the project?

These things probably don't matter much if you are going for a fork of Clipjump but it would be great to have a record here anyway.

If you have any questions or need clarifications, please ask?

[hoppfrosch]

Just for information: I already have a fork https://github.com/hoppfrosch/clipjump on which I already collaborated with Avi via pull requests.

Things I've done in the past: mostly worked on the documentation

I also did a little development for my own pleasure as documented in #88 - the main focus was using SQLite as database storage engine for clips. This development has been paused quite a while yet ....

[Kristinita]

@hoppfrosch , @aviaryan , see QTranslate and Jumpshare issues.

I enjoy Clipjump, but due to conflicts with other programs, use clipboard, I will be forced to use other clipboard manager, if bugs will not fixed.

Thanks.

[sergeevabc]

Is it dead?

[aviaryan]

@sergeevabc Yes, the development of this project has completely stopped.
I have switched to MacOS now and I don't think I would be going back to Windows anytime soon.
Also, I don't see any possibility that AutoHotkey might support MacOS.

So yes, the best chance for Clipjump's future is when any Windows-based developer takes over the project. Sorry for the trouble, @sergeevabc. Do you have any suggestions for this situation?

[sergeevabc]

Do you have any suggestions for this situation?

You can use Bootcamp or Virtualbox to install Windows 10 for free and continue the development.

[steliyan]

@aviaryan, a bit of offtopic, but I switched to MacOS recently and I really can't find any alternative to ClipJump. It's just awesome and I really got used to its workflow.
What do you use under MacOS, any recommendations are welcomed. :)

[aviaryan]

@steliyan I use Alfred with the clip history feature now. It's very basic but I have got used to it.

You can use Bootcamp or Virtualbox to install Windows 10 for free and continue the development.

I have tried it but's not much fun doing it. Plus since I won't be using the software on a regular basis, it won't be much effective to do it.

[mattlacey]

@aviaryan, a bit of offtopic, but I switched to MacOS recently and I really can't find any alternative to ClipJump. It's just awesome and I really got used to its workflow.
What do you use under MacOS, any recommendations are welcomed. :)

I know this is way after the fact, but Jumpcut on the Mac is a great tool, and I've always been stuck trying to find something as simple and clean as it for Windows!

[PavelDvorak]

Too bad the development is no longer running. It has been (and will still be for months to come) a great tool, Avi!

One thing I was really hoping for was a batch export/import, along with tags. Boy wouldnt that be awesome.

[aviaryan]

@PavelDvorak Aah. Feels man. I am on MacOS and I really like it so unfortunately can't develop Clipjump on Windows anymore. But I have heard Windows is doing good too. Talking about that, I remember Windows 10 came with a multiple clipboard features built in. And I tested it for a while and I think it was very similar to core Clipjump features. What do you think about that?

[PavelDvorak]

"Windows 10 came with a multiple clipboard features built in. "

Yes, maybe, I am mostly using it at work, and here we have an older version of Windows, so not applicable for me at the moment. But thanks! Hopefully someone with solid skills picks this up. Take care!

[aviaryan]

@PavelDvorak thanks! To be honest, earlier in the year I was thinking of starting this project again by asking a junior dev to build it but we got discouraged by Windows 10 clipboard feature.

[sergeevabc]

@aviaryan, Windows 7 is still the most popular desktop OS and it will remain so in the nearest future, regardless of EOL in 2020. Windows 10 is nowhere near in terms of predictability (updates change the experience now and then, sometimes irreversibly) and transparency (telemetry all around), not to mention it brings no tangible breakthroughs for home users.

[Kristinita]

@sergeevabc:

Windows 7 is still the most popular desktop OS and it will remain so in the nearest future, regardless of EOL in 2020

For November 2018:

• Windows 10 — 50%
• Windows 7 — 19,3%

---

But this does not mean that need to stop developing Clipjump — best clipboard program of the world.

Thanks.

[sergeevabc]

@Kristinita, I prefer widely quoted sources with more or less known details of data collection.
Windows 10 share is surely increasing (as new devices got it pre-installed), but it’s unlikely 50% vs 19,3%.