Warning: Official place is not here

[Neustradamus]

Hello @TheNicker, @vitaliyg2, and all,

The official place is here:

• https://github.com/doublecmd/doublecmd

Can you archive and plan to remove your repository and work directly into the official place?

Current forks of this repository: @antikruk, @dandv, @dkmkk, @GitCnSH-DSLIN, @phongth7

Thanks in advance.

Regards,

Neustradamus

[dandv]

Yeah, my fork only exists because of this PR to link to the official repo. I've deleted the fork.

Now that the official repo has migrated the code, it would probably be best to delete or at least archive this repo.

Thank you @Neustradamus for helping organize things.

[Neustradamus]

@dandv: Thanks for your reply, I have not seen your PR before ^^
Yes, it is really better now with the official place and changes done by @alexx2000!
The development will increase, I think :)

[TheNicker]

Hello @Neustradamus,
Thanks for the update about the official DVCS migration and thank you for your efforts for creating a single point of focus.
Having this reality was my intentions for many years, it wasn't possible then, perhaps now it is.

I'm more than happy to work with the "official" repo and get reviews for my PR's, nevertheless, for the near future I intend to keep this repo also active till it'll be evident that the official repo constitutes a stable and a healthy environment.

[Neustradamus]

@TheNicker, @vitaliyg2, @dandv, @rich2014, @Skif-off, @alexx2000, @exidler, @wesinator, @iglezz, @decart, @avmaksimov: The problem is always here!

• https://github.com/double-commander/doublecmd
• https://github.com/doublecmd/doublecmd

[TheNicker]

@TheNicker, @vitaliyg2, @dandv, @rich2014, @Skif-off, @alexx2000, @exidler, @wesinator, @iglezz, @decart, @vmaksimov: The problem is always here!

• https://github.com/double-commander/doublecmd
• https://github.com/doublecmd/doublecmd

I have started this repository long before the official dev team has moved to Github or a modern source versioning control system in general.
Nowadays when the official Github repo is alive and active. it has much precedence in search engines over this repo. I don't think people get confused like in the early days.
So what's exactly is the problem ?

Please be advised that this repo is currently being used and it is needed, that's why it is still open, otherwise I would have get rid of it long ago.
Ideally, I would use only the official repo and I wouldn't be writing any source code for double commander, but it is not the case.
For me double commander is a work tool, in recent times I'm working with Linux as well, so I'm relying on it to provide me what I need.

I would be happy to discuss about needed features and get feedback, it is okay to have different opinions and needs, and if someone don't like my idea it's fine as long as I am not depended on one's mindset, but till then I would require a solution now.

Ultimately it's people, not everyone sees everything, and it's a challenge to transfer ideas to a great precision to one another, not the least in the medium named Github

[Neustradamus]

@TheNicker, @vitaliyg2, @dandv, @rich2014, @Skif-off, @alexx2000, @exidler, @wesinator, @iglezz, @decart, @avmaksimov: The goal is to have only one!

The bad repo is https://github.com/double-commander/doublecmd/

To be perfect, the steps to do:

• Rename the bad repo by doublecmd-temp
• Move the bad repo in the good organization
• Transfer all issues in the good repo
• Remove the bad repo
• Move the good repo in bad organization
• Move the good repo in the good organization

Old bad organization links will be redirected to the good organization place.

Keep the bad organization and add text to people to go at the good place.

I can do it easily, I have already done it previously!

[dandv]

I've unstarred the "bad" repo (honestly, 2 years later, I don't remember the whole story, but the "bad" repo only has 83 stars). However, the "bad" repo has over 10k commits, and they're very recent, so users my get confused.

Who can update the description of the bad repo on GitHub to indicate its exact nature? Now it's this:

[Neustradamus]

@dandv: Warning: 2 repositories have been changed recently: The trunks have been modified.
It was not like it before.

The "good" has more, you can look.

---

Guys, it is needed to do steps that I have specified to be perfect.
I would like to do directly.

[vmaksimov]

Guys, you have been mistaken with @vmaksimov account, I suppose it has to be @avmaksimov Best regards, Viacheslav Maksimov

…

On 31. Jul 2023, at 22:21, Neustradamus ***@***.***> wrote:  @TheNicker, @vitaliyg2, @dandv, @rich2014, @Skif-off, @alexx2000, @exidler, @wesinator, @iglezz, @decart, @vmaksimov: The goal is to have only one! The bad repo is https://github.com/double-commander/doublecmd/ To be perfect, the steps to do: Rename the bad repo by doublecmd-temp Move the bad repo in the good organization Transfer all issues in the good repo Remove the bad repo Move the good repo in bad organization Move the good repo in the good organization Old bad organization links will be redirected to the good organization place. Keep the bad organization and add text to people to go at the good place. I can do it easily, I have already done it previously! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[Neustradamus]

Oups sorry, I have edited, thanks for information!

[Neustradamus]

Dear current @double-commander, and @doublecmd team,

I wait your news.

If you have a problem, I can do all steps to be perfect.

And I will move all tickets into the same repository and redirect from the bad repo to the good repo.

Can you add me like I have requested you at beginning?

Thanks in advance.

[dandv]

@Neustradamus: I've deleted my fork. Thanks for helping organize the project!