Upstream migration.

[pktiuk]

Recently we have been granted access to legacy AntiMicro repository.

Our further steps are listed below:

[gombosg]

Maybe there was some misunderstanding, but my proposal is to touch antimicro as little as possible, treating it as legacy code, and not waste our time with backporting and maintaining 2 code bases. IMO we just don't have the time and resources for that.

There is no 'upstream' antimicro, since it hasn't been in development for years. This antimicrox code is the upstream now.

My proposal is to

• Leave a README notice in antimicro so that users know what is going on and how they can contribute. chore: README update - new maintainers AntiMicro/antimicro#352
• If not present already, provide config migration & compatibility for antimicro users, first under Linux. You already did similar stuff when renaming the repo so this should be doable. antimicro config migration #86
• In the meantime, contact the Debian maintainer so that once we have a migration path, they could deprecate antimicro in favor of antimicrox. Migrate DEB packages to antimicrox #87
• Fix the Windows build in antimicrox, also check for config compatibility. Restore Windows support #4
• Then migrate Windows antimicro users to antimicrox by a README notice and possibly by archiving the antimicro repo once we reach feature parity.

What do you think about these steps? I can create issues for missing stuff.

[pktiuk]

I agree with everything, but I am not sure about migrating Windows users to AntiMicroX, because most of regular Windows users do not use sites as GitHub, bot other general purpose download sites like SourceForge etc and they will never see its GitHub page.

[pktiuk]

We could just leave the entire development on AntiMicroX side, but it would be good to use traction this repository already has and push here something from time to time.

[gombosg]

bot other general purpose download sites like SourceForge etc and they will never see its GitHub page

This is a logistics problem: identifying where users find antimicro. As I see the SF page: https://sourceforge.net/projects/antimicro.mirror/ is just a dumb mirror, and can simply be updated by adding a feature-compatible antimicrox release to the antimicro page.

We can also notify download sites like softpedia to update their releases once we have something useful released.

I'm just saying that our resources are limited, and if these problems can be answered by something else than doing more coding 🙂 then we should prefer that.

[pktiuk]

But there much more smaller, local sites like this , this, this
And updating and finding all of them is nearly impossible.

We should wait with final decision until we will find out what exactly broke Windows and then decide.
We have time, this repository was waiting 4 years, it can wait several additional months.
Maybe we will find in the meantime some windows-savvy developers.

[gombosg]

I totally agree, what I'm saying is that these sites also only know about updates if
a) we notify them
b) they see a release a GH, and we can add an antimicrox release then.

I also hope that we can get some Windows help, too. :)

[pktiuk]

I have opened an issue for discussion about this topic:

AntiMicro/antimicro#351

[gombosg]

Great! I opened issues here, see the checklist above.

[pktiuk]

According to last point:

Then migrate Windows antimicro users to antimicrox by a README notice and possibly by archiving the antimicro repo once we reach feature parity.

I think we should wait for release 3.2.1. 3.2.0 May have some bugs and lacks making migration annoying.

[avinal]

We can still put a notice for beta-testing for windows users. This will attract interested people into installing and then finding more bugs. And we can add a new window's label for issues if not already or put all windows-related issues into the project board for easier access. Then add a link with the notice saying "See known issues here"

[pktiuk]

• Then migrate Windows antimicro users to antimicrox by a README notice and possibly by archiving the antimicro repo once we reach feature parity.

Before proceeding with the last point from this list I would like to discuss it here: AntiMicro/antimicro#351

[pktiuk]

I think Now, after archiving legacy repository, we can tell, that we finished this migration.