Forked packages of abandoned projects

Plone Support Add-on Development
1

Hey all,

I’m seeking some legal-ish advice: we are integratingftw.slackerin our website, and as the code was quite outdated I made a refresh of it on the fork I made:

Cleanup and port to plone.meta by gforcada · Pull Request #1 · derFreitag/ftw.slacker · GitHub

Now the question is: we can not release it to pypi as I don’t have access to the pypi page for that distribution.

Is a rename to collective.slacker keeping the license and credits, etc legally sound and a way to be able to make pypi releases? Otherwise I can keep cutting internal releases, but it would be nicer if this could be shared with the wider Plone community :smiley:

Opinions? advice?

2

ftw.slacker is licensed under GNU General Public License, version 2.

Unless you follow the GPL v2, you're ok.

3

Some months ago, a similar discussion was raised here regarding ftw.upgrade:

@maethu forked the package to the collective and named it collective.ftw.upgrade

2 Likes
4

It’s not possible to get pypi ownership transferred for those packages?

5

I at least know the names listed there: ftw.slacker but most probably they don’t know me :upside_down_face:

6

@maethu is one of them

7

I was a maintainer, but not an owner, so I can’t move ownership.
I would suggest to do the same here :slight_smile: as I did for ftw.upgrades.

I’m currently also working on collective.deletepermission (same issue).

1 Like
8

Thanks, I created collective.ftwslacker then :slight_smile:

9

And a first alpha release of it is out: collective.ftwslacker==2.0.0a1 :tada:

2 Likes
10

I hate being late :frowning:

I faced the same problem years ago and vendored their package inside contentrules.slack.