We don't trust the maintainer field as the user that forks it and republishes it now has given false information to users. We determine the author/owner from the bzr branch it's under. in the case of etherpad-lite the one in question doesn't have bzr info.
Note the lack of the bzr history on the right compared to other charms:
This is because the charmstore currently pulls this from the old manage.jujucharms.com. If it doesn't have bzr info we list 'no owner'. As we work on the new juju upload/pubilsh workflow this will be the logged in user that uploads a charm and will always be available and always correct. I'm marking this as wishlist as spending the time to work on getting old bzr history into manage.jujucharms.com will take away from the true fix, moving towards the new workflow with user login.
We don't trust the maintainer field as the user that forks it and republishes it now has given false information to users. We determine the author/owner from the bzr branch it's under. in the case of etherpad-lite the one in question doesn't have bzr info.
Note the lack of the bzr history on the right compared to other charms:
https:/ /jujucharms. com/etherpad- lite/trusty/ 1
vs
https:/ /jujucharms. com/mysql/ precise/ 51
This is because the charmstore currently pulls this from the old manage. jujucharms. com. If it doesn't have bzr info we list 'no owner'. As we work on the new juju upload/pubilsh workflow this will be the logged in user that uploads a charm and will always be available and always correct. I'm marking this as wishlist as spending the time to work on getting old bzr history into manage. jujucharms. com will take away from the true fix, moving towards the new workflow with user login.