[opensuse-packaging] New packages for factory
Hi, I would like to point out something that seems not obvious to everyone: Everyone can maintain packages in factory now There is no limitation anymore on who can maintain packages, _BUT_: - the package has to be submitted and reviewed into an _existant_ devel project - it has to build successfully against factory - the devel project has set a bugowner and maintainer for the package - preferably someone else from the devel project submits it to factory, but this is not a strict requirement - the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest. The information we need are things like this: - who is the bugowner (has to be set in the package)? - how long has it been around? - how well has it been tested? - what is the upstream project? - does it have a track record of security issues? - what is the purpose of having it in the distribution? - what are its users? - what is the license (has to be set in the package)? The main purpose of requiring this informations in the submitrequest is that you think about such things before you write a script that dumps all of freshmeat into factory. I don't want to stop anyone from maintaining a package in our distribution, but I want every package to be maintained, not to be packaged - I hope you understand the difference. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Stephan Kulow wrote:
- the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest.
Fedora just uses bugzilla to request package inclusion in the distro, maybe we could adapt the workflow: https://fedoraproject.org/wiki/Package_Review_Process https://fedoraproject.org/wiki/Packaging:ReviewGuidelines cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag 24 Juli 2009 schrieb Ludwig Nussel:
Stephan Kulow wrote:
- the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest.
Fedora just uses bugzilla to request package inclusion in the distro, maybe we could adapt the workflow: https://fedoraproject.org/wiki/Package_Review_Process https://fedoraproject.org/wiki/Packaging:ReviewGuidelines
I don't see any need for a formal review at this point. Not yet. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 7/24/2009 at 11:30, Stephan Kulow
wrote: Fedora just uses bugzilla to request package inclusion in the distro, maybe we could adapt the workflow: https://fedoraproject.org/wiki/Package_Review_Process https://fedoraproject.org/wiki/Packaging:ReviewGuidelines I don't see any need for a formal review at this point. Not yet.
What I don't like in this sentence is the 'not yet'. This means we expect it to come and again we'll be one step behind, not having the proper process in place when we actually need it. I'd vote to try to go ahead, prepare the process, get the tools, for when the requests and submits get to a to high number to be handled on the ML that we're ready for it and can just do it(tm). Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le vendredi 24 juillet 2009, à 11:30 +0200, Stephan Kulow a écrit :
Am Freitag 24 Juli 2009 schrieb Ludwig Nussel:
Stephan Kulow wrote:
- the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest.
Fedora just uses bugzilla to request package inclusion in the distro, maybe we could adapt the workflow: https://fedoraproject.org/wiki/Package_Review_Process https://fedoraproject.org/wiki/Packaging:ReviewGuidelines
I don't see any need for a formal review at this point. Not yet.
It doesn't have to be a formal review. But it's really not convenient to put the information you're requesting in a submitrequest, while it could be easy to put it in a web form and link the web page from the submitrequest (or even create the submitrequest automatically from there). (no, I'm not volunteering to implement this at the moment, sorry :/) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2009-07-25T15:18:40, Vincent Untz
It doesn't have to be a formal review. But it's really not convenient to put the information you're requesting in a submitrequest, while it could be easy to put it in a web form and link the web page from the submitrequest (or even create the submitrequest automatically from there).
Special mailing list and refer to the posting in the SR? But really, bugzilla already provides tracking functionality, which would make this a bit better integrated. Even though I think bz sucks for discussion, the tracking would allow everyone to see who is responsible for the next step etc. Maybe the SR could automatically create a bugzilla request and assign it to the submission target's maintainer, and accepting it could create an automatic update message. (Or maybe the other way around - RESOLVED FIXED accepts, RESOLVED INVALID etc reject.) It would immediately make features such as voting, priorities, severity, reassignment etc available, it would allow us to put dependencies on other bugs (those which are mentioned in the changelog, for example) ... Regards, Lars -- Architect Storage/HA, OPS Engineering, Novell, Inc. SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2009-07-24T10:17:21, Stephan Kulow
- the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest.
So what is the process that happens after the sr is created? Who makes the decision, and how? Regards, Lars -- Architect Storage/HA, OPS Engineering, Novell, Inc. SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Dienstag 04 August 2009 schrieb Lars Marowsky-Bree:
On 2009-07-24T10:17:21, Stephan Kulow
wrote: - the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest.
So what is the process that happens after the sr is created?
Who makes the decision, and how?
If it's not obvious to the one checking in, it's left for me to decide and I will discuss alternatives with the person submitting if I don't like what I see (as I said: the main objective is avoiding careless submissions of generated packages). Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 2009-08-05T09:47:18, Stephan Kulow
- the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest. So what is the process that happens after the sr is created?
Who makes the decision, and how? If it's not obvious to the one checking in, it's left for me to decide and I will discuss alternatives with the person submitting if I don't like what I see (as I said: the main objective is avoiding careless submissions of generated packages).
Don't you think tracking this via bugzilla for example might provide a bit more transparency than 1:1 e-mail? Regards, Lars -- Architect Storage/HA, OPS Engineering, Novell, Inc. SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Mittwoch 05 August 2009 schrieb Lars Marowsky-Bree:
On 2009-08-05T09:47:18, Stephan Kulow
wrote: - the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest.
So what is the process that happens after the sr is created?
Who makes the decision, and how?
If it's not obvious to the one checking in, it's left for me to decide and I will discuss alternatives with the person submitting if I don't like what I see (as I said: the main objective is avoiding careless submissions of generated packages).
Don't you think tracking this via bugzilla for example might provide a bit more transparency than 1:1 e-mail?
Lars, if you want to volunteer to come up with a process to document, I'm fine with you stepping up. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
At Wed, 5 Aug 2009 10:42:40 +0200, Lars Marowsky-Bree wrote:
On 2009-08-05T09:47:18, Stephan Kulow
wrote: - the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest. So what is the process that happens after the sr is created?
Who makes the decision, and how? If it's not obvious to the one checking in, it's left for me to decide and I will discuss alternatives with the person submitting if I don't like what I see (as I said: the main objective is avoiding careless submissions of generated packages).
Don't you think tracking this via bugzilla for example might provide a bit more transparency than 1:1 e-mail?
The discussion can be open, simply as follow ups to the original post to ML, just like we've done on suse-dist ML. Takashi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (6)
-
Dominique Leuenberger
-
Lars Marowsky-Bree
-
Ludwig Nussel
-
Stephan Kulow
-
Takashi Iwai
-
Vincent Untz