Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack-www/pull/20#issuecomment-159583159
well, it got evolved during the 4.0 release and no one objected.
May be, first we should start a discuss/vote first on what can we include.
community maintenance comes in because issues are reported on users@/dev@
list and users do ask questions on which rpms/templates to use when there are
multiple. When the source bits are same and build in the same way, why should
we list another one?
I completely agree that they are not official. But, not official and
community build is different. As I said before, I see it as temporary spot
before we get them in ASF.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
