Stefan Schweizer wrote: > ..commit their changes to the overlay instead of updating the bugzilla > every time. it is actually encouraged to update bugzilla when changes are made in the overlay.
Here are some more things I found in the current thread: chris > It also doesn't answer the questions of security and maintenance. Are > genstef and jokey going to be responsible for the security of every > single package in the overlay? Yes, we will be acting upon all issues that we hear about. chris > How are > ebuilds going to get from this overlay into the official repository? The people who committed them to the overlay will move them to the tree eventually when they are developers - otherwise any developer can move them if he likes to. Of course taking full responsibility of it, it is also mentioned in the overlay project documentation, that automatic tools for committing to the tree are not allowed. antarus > The point of the > Sunrise project as I understand it is to aid in the development of > ebuilds in maintainer-wanted, such that they may improve and be added to > the tree; as well as to give frequent 'not quite a dev' and 'I don't > have a bunch of time but would like to help' people a place to commit to. Have to agree here :) chris > Why is there access controls? Because we are just following the overlays.g.o standards. There is no actual access controls, because we are not refusing valid requests currently. valid requests = come with a valid change they want to make. carlo > that is neither supported security wise, nor is > ensured that the ebuilds have a minimal quality (do not fubar a users > system). we do support it security wise, we will be reacting upon security issues. We do have package.mask support in the overlay and we are going to use it. The ebuilds have a quality, repoman is required to be run. Also contributors should be knowing what they are doing - they are submitting an ebuild to the sunrise overlay, it needs to follow certain standards. peter > The sunshine overlay nice name :) > Warn users that ebuild in o.g.o come with no assurances whatsoever, and > let the market decide if this is a source worthy of use! That is the plan. g2boojum made some interesting suggestions about how bugzilla could be automatically connected with an overlay - unfortunately no one is working on that. flameeyes 21:38:17 > I would prefer if people would still comment on the bugs when they do some > changes on the overlay so that at least we know that. yeah that is already suggested by the current guide it is useful for maintainers to know about contributors. > eclasses The eclass/ subdirectory has been blocked in the overlay - It is not possible to commit there. If eclasses are needed they need to go through the usual gentoo-dev-review and need to be committed to the main portage tree. - Stefan -- gentoo-dev@gentoo.org mailing list
