Re: [opensuse-project] I propose a packagers meeting
On Thu, 02 Oct 2008 11:05:33 -0500, Bryen
On Thu, 2008-10-02 at 09:50 -0600, Stephen Shaw wrote:
I think it would be useful to gather all packagers together and have a meeting. I think this would help maximize our efforts and help out new comers to opensuse packaging. Maybe once a week on Wednesday.
With community/contrib repos and being able to contribute to openSUSE factory, more organization among the packagers in the community could help develop a great set of repositories and help share the work load that the current packages have.
Last night made me think about this. I packaged up the new gimp 2.6 for factory and submitted it (which took some time to get everything together). It was rejected because someone else already had done it. If I had known that someone else was working on it, I could have put all of that effort into another package.
Thanks, Stephen Shaw Proud 2008 openSUSE Board Candidate
I think that's a great idea. I also observed when several people worked together trying to package a component for mouseTrap, only to discover that after all their work, they realized someone else already did that component.
There needs to be a better awareness thus reducing duplication of efforts.
-- Bryen Yunashko Proud 2008 Candidate for openSUSE Board
I Also think this is great idea that would help to coordinate at least contrib. If packager doesn't appear in IRC or some other (Mailing list) he could not commit packages to contrib. Then there should be 'Official' marked contrib packages (Those should be endorsed in search) and there should be normal packages that are mentioned with warning that this ain't anyhow supported by openSUSE community (or they are not tested). Support is provided only by packager (Same like horrible SSL marker as Firefox 3.x has). Duplication is not bad as we think is just stupid in this case. First we need Wiki page and times there when appear in place (Then I think little advertisiment) and some to keep IRC minutes up as secretary. Tuukka Currently very drunk candidate of openSUSE Board :P -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Hi, I want to add my $0,05 into discussion. Before I started packaging for openSUSE, I used Fedora. Fedora has well organized packaging. 1) You create SPEC, SRPM; 2) submit them to new bug in bugzilla, as review request; 3) fix all "bugs" resubmitting SPEC and SRPM every time 4) wait for review and approval 5) compile package and watch via Koji 6) add to Bodhi and wait for tests and 7) when updating, just rebuild in Koji 8) add to Bodhi as update and wait for tests I thought I bit about openSUSE situation and made a draft. 1) You prepare package in oBS (doesn't matter which client with) 2) click "request contrib review" / trigger (Web/console) 3) wait for reviewer, fix bugs and wait for final review 4) when package is in contrib (*), every time you want to do an update, you click/trigger "submit update" (Web/console) and wait for tests (*) I think contrib is quite bad name, since most people of the world know "community" better than "contrib(ution)", but one man can't change the world. At least not if he's wanting this to do alone. Tell me what to do you think. -- Jakub 'Livio' Rusinek http://liviopl.jogger.pl/
On Fri, 2008-10-03 at 14:35 +0200, Jakub 'Livio' Rusinek wrote:
Hi,
I want to add my $0,05 into discussion.
Before I started packaging for openSUSE, I used Fedora. Fedora has well organized packaging.
1) You create SPEC, SRPM; 2) submit them to new bug in bugzilla, as review request; 3) fix all "bugs" resubmitting SPEC and SRPM every time 4) wait for review and approval 5) compile package and watch via Koji 6) add to Bodhi and wait for tests
and
7) when updating, just rebuild in Koji 8) add to Bodhi as update and wait for tests
I thought I bit about openSUSE situation and made a draft.
1) You prepare package in oBS (doesn't matter which client with) 2) click "request contrib review" / trigger (Web/console) 3) wait for reviewer, fix bugs and wait for final review 4) when package is in contrib (*), every time you want to do an update, you click/trigger "submit update" (Web/console) and wait for tests
(*) I think contrib is quite bad name, since most people of the world know "community" better than "contrib(ution)", but one man can't change the world. At least not if he's wanting this to do alone.
Tell me what to do you think.
First of all, please don't completely delete out the contents of the previous message you're responding to, as we don't know which portion of a thread you're responding to when you do that. Second of all, I think you missed the point of Stephen's original email. The point is not to assess how the procedures are implemented, but how to coordinate acknowledging and being aware when the work you're doing is already being done by others, even simultaneously. There's too much overlapping going on diverting the community's ability to build *more* packages rather than the same packages over and over. I think Stephen is pursuing an excellent goal, which is to gather everyone together to first commiserate :-) and then come up with a unified plan that everyone can be a part of and be more productive. -- Bryen Yunashko Proud 2008 Candidate for openSUSE Board -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
participants (3)
-
Bryen
-
Jakub 'Livio' Rusinek
-
tuukka.pasanen@ilmi.fi