Activity log for bug #941255

Date Who What changed Old value New value Message
2012-02-26 05:27:14 Duncan McGreggor bug added bug
2012-02-26 05:27:22 Duncan McGreggor ubuntu-accomplishments-system: assignee Duncan McGreggor (oubiwann)
2012-02-26 05:27:28 Duncan McGreggor ubuntu-accomplishments-system: status New In Progress
2012-02-26 06:20:31 Duncan McGreggor branch linked lp:~oubiwann/ubuntu-accomplishments-system/941255-unified-source-dir
2012-02-26 06:20:59 Duncan McGreggor description This project installs the following into the Python libs dir: * daemon * trophyinfo * trophyinfo_lib The first one isn't such a good idea, since it's such a generic name... and someone else might have already used that name. Even if that's not the case, it's not good practice to install something in the Python lib space that isn't readily identifiable. As for the second two, there's needless separation here: one is providing base classes for another. All told , there's no reason to separate these three. Ideally, the code would be refactored to include them all in the same Python package. This project installs the following into the Python libs dir:  * daemon  * trophyinfo  * trophyinfo_lib The first one isn't such a good idea, since it's such a generic name... and someone else might have already used that name. Even if that's not the case, it's not good practice to install something in the Python lib space that isn't readily identifiable. As for the second two, there's needless separation here: one is providing base classes for another. All told, there's no reason to separate these three. Ideally, the code would be refactored to include them all in the same Python package.
2012-03-05 03:00:58 Duncan McGreggor description This project installs the following into the Python libs dir:  * daemon  * trophyinfo  * trophyinfo_lib The first one isn't such a good idea, since it's such a generic name... and someone else might have already used that name. Even if that's not the case, it's not good practice to install something in the Python lib space that isn't readily identifiable. As for the second two, there's needless separation here: one is providing base classes for another. All told, there's no reason to separate these three. Ideally, the code would be refactored to include them all in the same Python package. This project installs the following into the Python libs dir:  * daemon  * trophyinfo  * trophyinfo_lib The first one isn't such a good idea, since it's such a generic name... and someone else might have already used that name. Even if that's not the case, it's not good practice to install something in the Python lib space that isn't readily identifiable. As for the second two, there's needless separation here: one is providing base classes for another. All told, there's no reason to separate these three. Ideally, the code would be refactored to include them all in the same Python package. Note that this also requires changes to the community contributions, and that work is being tracked in a separate ticket/branch: bug #946809.
2012-03-05 03:01:29 Duncan McGreggor branch linked lp:~oubiwann/ubuntu-community-accomplishments/946809-module-changes
2012-04-09 05:36:22 Jono Bacon ubuntu-accomplishments-system: status In Progress Invalid