Ownable contract owner is always the 0 address

[abcoathup]

Hi @Chrissie,

It would be good to improve this experience to save other community members from what you went through.
Where would you have expected to see a note on the upgradeable version, so that we can look to add one there.

Linking the Contracts Ethereum Package OpenZeppelin SDK documentation has the following note:

Make sure you install @openzeppelin/contracts-ethereum-package and not the vanilla @openzeppelin/contracts. The latter is set up for general usage, while @openzeppelin/contracts-ethereum-package is tailored for being used with the OpenZeppelin SDK. This means that its contracts are already set up to be upgradeable.

There is also a discussion on how contracts and contracts-ethereum-package could be made into a single offering:

Planning the demise of OpenZeppelin Contracts' evil twin

TL;DR: How can we merge contracts and contracts-ethereum-package into a single offering, making it transparent to the user whether they are using upgradeable contracts or not? If you are here in the OpenZeppelin forum, dear reader, you are probably familiar with our @openzeppelin/contracts library, which sports popular contracts like SafeMath, Ownable, or the most widely used ERC20 implementation. However, it's possible that you have missed our @openzeppelin/contracts-ethereum-package. This is…