Mailinglist Archive: opensuse-contrib (47 mails)
| < Previous | Next > |
[opensuse-contrib] open issues
- From: Michal Marek <mmarek@xxxxxxx>
- Date: Mon, 15 Sep 2008 14:30:07 +0200
- Message-id: <48CE554F.9050204@xxxxxxx>
Hi,
Let's identify the real issues and tackle them asap. From
http://en.opensuse.org/Contrib#Open_issues_and_packages:
# Security - perhaps Novell security guys can give us basic guidelines.
This has two parts
1) The hard part - monitoring upstream changelogs, bugtraq and the like
to identify security bugs. Should be probably maintainers'
responsibility.
2) Fixing security bugs: As not every package maintainer has to be a
programmer, we should allow version updates where it makes sense.
===
# Upstream vs. patched. (easy example: KVM from Alexander Graf, or from
Sourceforge.net - difference is big)
That should really be up to the package maintainer. If he is willing to
maintain the patches, there should be no problem.
-> not an issue
===
# Bugzilla integration (we need another discussion on that topic)
This is not specific to contrib, better bugzilla integration would be
beneficial for any build service project. For now, let's stick to
<person role="bugowner" userid="xxx"/>.
-> not an issue
===
# Who will be allowed to do what, see #Permissions
It seems that everybody agreed on the reviewers/maintainers model (at
least, I heard no objections)
-> not an issue
===
# What about updates for single packages in that repository? If the
repository is frozen after the release, we need an additional repository
just for packages containing bugfixes and security fixes. Who will
maintain this additional repository? Who will review the packages
submitted there? Should there be patches like for the official openSUSE
packages available? Related: [opensuse-factory] Contrib: Progress
Patches are not possible right now, having two repositories is not a
good idea. Let's just update packages in the repository.
===
# Forks ( fork is similar to duplicate packages; Think of Cinepaint and
GIMP. Should we allow forks? )
As long as the package follows the rules (esp. the one about no
conflicts with Factory packages), I see no problem here.
-> not an issue
===
I'll remove the non-issues from the wiki page and try to write some
rules about post-release updates, which is what the remaining two issues
are about (but we should be able to start even without these rules in
place).
Michal
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-contrib+help@xxxxxxxxxxxx
Let's identify the real issues and tackle them asap. From
http://en.opensuse.org/Contrib#Open_issues_and_packages:
# Security - perhaps Novell security guys can give us basic guidelines.
This has two parts
1) The hard part - monitoring upstream changelogs, bugtraq and the like
to identify security bugs. Should be probably maintainers'
responsibility.
2) Fixing security bugs: As not every package maintainer has to be a
programmer, we should allow version updates where it makes sense.
===
# Upstream vs. patched. (easy example: KVM from Alexander Graf, or from
Sourceforge.net - difference is big)
That should really be up to the package maintainer. If he is willing to
maintain the patches, there should be no problem.
-> not an issue
===
# Bugzilla integration (we need another discussion on that topic)
This is not specific to contrib, better bugzilla integration would be
beneficial for any build service project. For now, let's stick to
<person role="bugowner" userid="xxx"/>.
-> not an issue
===
# Who will be allowed to do what, see #Permissions
It seems that everybody agreed on the reviewers/maintainers model (at
least, I heard no objections)
-> not an issue
===
# What about updates for single packages in that repository? If the
repository is frozen after the release, we need an additional repository
just for packages containing bugfixes and security fixes. Who will
maintain this additional repository? Who will review the packages
submitted there? Should there be patches like for the official openSUSE
packages available? Related: [opensuse-factory] Contrib: Progress
Patches are not possible right now, having two repositories is not a
good idea. Let's just update packages in the repository.
===
# Forks ( fork is similar to duplicate packages; Think of Cinepaint and
GIMP. Should we allow forks? )
As long as the package follows the rules (esp. the one about no
conflicts with Factory packages), I see no problem here.
-> not an issue
===
I'll remove the non-issues from the wiki page and try to write some
rules about post-release updates, which is what the remaining two issues
are about (but we should be able to start even without these rules in
place).
Michal
--
To unsubscribe, e-mail: opensuse-contrib+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-contrib+help@xxxxxxxxxxxx
| < Previous | Next > |