Mailinglist Archive: opensuse-project (73 mails)
| < Previous | Next > |
Re: [opensuse-project] I propose a packagers meeting
- From: Bryen <suserocks@xxxxxxxxx>
- Date: Fri, 03 Oct 2008 09:44:38 -0500
- Message-id: <1223045078.3333.69.camel@xxxxxxxxxxxxxxx>
On Fri, 2008-10-03 at 14:35 +0200, Jakub 'Livio' Rusinek wrote:
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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
| < Previous | Next > |