Migration of packages from ferventcoder's repository

[AdmiringWorm]

I'm opening this issue for tracking purposes and for having a list to work against for packages that should/could be migrated from @ferventcoder's repository.
The repo is located at:
https://github.com/ferventcoder/chocolatey-packages

The list is as following:

• 1password High Priority
• 7zip.install-beta Should be easy enough, now that we have streams
• CloudBerryExplorer.S3
• Compass
• PhantomJS Priority?
• StExBar
• VirtualCloneDrive
• Yeoman Deprecated. Yo already here
• adobereader
• anyvideoconverter
• appharbordcli.install
• attributechanger
• expresso
• filezilla.commandline
• filezilla.server
• filezilla
• fluffyapp
• foobar2000
• gitextensions
• googledrive Is it still supported?
• grepwin
• httrack.app
• httrack.tool
• httrack
• jetty
• jruby
• ketarin Yes, we should keep the competitor updated
• maxthon.commandline Personal Priority
• maxthon.install
• miranda
• mono High Priority
• mysql
• netbalancer
• nodejs.commandline MAYBE? Is there still a portable edition of this one?
• nodejs.commandline.lts See above
• nodejs.install.lts Already supported by the way of streams
• pip Deprecated, comes with python
• pngoptimizer.commandline
• pngoptimizer
• postgresql.v8 High Priority
• postgresql.v9 High Priority
• pspad
• puppet-agent.portable
• puppet-agent High Priority
• puppet
• resharper maintained by JetBrains
• skype [Hi priority]
• sliksvn
• sqlite.analyzer [ contained in sqlite ]
• sqlite.shell [ contained in sqlite ]
• sqliteadmin [ contained in sqlite ]
• sumatrapdf.commandline
• sumatrapdf.install
• sumatrapdf
• vim

Some of the above may not necessarily need to be converted to AU automatic packages, but can be changed to manual packages.

EDIT:
Updated with link to repository, just in case.

[pascalberger]

Ferventcoders Yeoman is already moved to this repository: yo

[majkinetor]

all sqlite stuff is already under single sqlite package here so that should be deprecated.

[gep13]

@AdmiringWorm historically, there were two fiddler packages, because one (fiddler) specifically targetted .Net Framework 2.0. Where as the other (fiddler4) targetted .Net Framework. This may no longer be important.

[pascalberger]

pip Deprecated, comes with nodejs
I don't think thats true. pip is the python package manager (npm is the bundled node package manager)

[AdmiringWorm]

@gep13 yeah, I'm not sure if it's important anymore or not, but it should be updated with checksums anyhow.

@pascalberger Yeah, that isn't true, it is included with python, not nodejs. Huge typo on my part

[ferventcoder]

ReSharper is now maintained by the ReSharper team.

[ferventcoder]

The 7zip beta, not sure it's important anymore.

[AdmiringWorm]

The 7zip beta, not sure it's important anymore.

probably not that important, but it could still be added as an additional stream on the existing 7zip package.
I don't think it would hurt too much to have it though

[ferventcoder]

@AdmiringWorm FYI, 1password v4 and v6 are nearly two different products. If we have a v6, there needs to be a 1password4 package.

[AdmiringWorm]

@ferventcoder well, we can certainly create a package solely for that version.
I won't be able to look at that today though, as I'll be gone the whole day, but I'll try to look into it later this week

[majkinetor]

I think we should close this. Number of most important packages are already migrated, vast majority of what is left is either already taken by somebody else or not updated any more or not used any more or not requested in comments etc.

Personally I think that only the following should be done:

• mysql
• filezilla.server
• postgresql
• puppet
• pngoptimzer

and I will probably do them all in the future.

In any way, I don't think that we should keep this open, it will stay here forever basically like it is always the case with huge issues like this one.

[AdmiringWorm]

I'm sorry, but I disagree. IMO it's still useful to have this open.
Originally, it was the intention of migrating all of @ferventcoder's packages to this repository, otherwise it wouldn't be a need to create this issue.

[majkinetor]

Originally, it was the intention of migrating all of @ferventcoder's packages to this repository, otherwise it wouldn't be a need to create this issue.

I am aware of your original intention (not mine). I think it was bad decision then to create such massive ticket that probably requires years to resolve fully, if it ever gets resolved. But I didn't want to rant then, I always like to give chance. Its soon almost a year old without any activity for ~6mo, and with diminishing return, it's not hard to extrapolate how long we will have it here open. Not to mention, ALL tickets have a lifetime here as per guidelines, this one included and should already have 'pending closure' tag.

We are not here to migrate random third party repositories - maintaining this repository is job for itself. - if you didn't notice issues started to pile up, and we still have 0 new maintainers.

It's not particularly important who's repository is it. If you want to do this, you can keep private notes on it and create issue/PR here at the moment you choose to do some actual work . Otherwise, ticketing system will become huge hole of random tickets that scratch particular itch that somebody had once and that doesn't inspire confidence to any potential newcomers - it reflects that we can't cope with the demand here, that we don't know how to resolve priorities and assign resources we have at the moment.

Having issues like this is total anti-pattern in project management. I care about this repository, and others can do on their whatever they want. Its probably for the best we move this ticket to ferventcoder's repository, since that is the place where it should have been originally created. Imagine everybody starts to create massive migration tickets here ?

A question for everybody - would you rather have huge package repository that isn't maintained and presents bad public image for most-used packages on the public gallery, or smaller set of packages that always work and are polished and maintained all the time ? First time I came here, it was case one. We worked very hard to move it to the case 2.

[stale]

Dear contributor,
because this issue seems to be inactive for quite some time now, I've automatically closed it. If you still feel this is a valid issue, please feel free to re-open the issue. Thank you for your contribution.