On Mon, 17 Oct 2005, Aschwin Marsman wrote:
> > > > The development is already open - just use Bugzilla to interact
> > > > with the YaST developers on this. But please note, that there will
> > > > be quite some redevelopment on the YaST2 Packagemanager + YOU for
> > > > 10.1...
>
> Where can I read what the current plans are for YaST2? I can only spent
> my time once like everybody else, is it discussed on the opensuse-edge
> mailing list? Where can I find it on the opensuse.org website?
As of now there hasn't been much dicussion on the plans for YaST2
development. I'll try to get the YaST people to publish some kind of
rough outline on what they are planning for 10.1...
> > > That depends on your definition of open: using Bugzilla to report a
> > > bug or issue a feature request is usefull, but open development to
> > > me would be that I can take the source, make a patch which does what
> > > I would like and sent that to a mailing list for discussion/review.
> > > Do we have that kind of openess already? Is it supposed to be like
> > > that in the (near) future?
> >
> > We had that kind of openness from day 0 - just go ahead, file a
> > bugreport, attach a patch and discuss it with the developers. But be
> > aware of the fact that we might not accept your patch - which has
> > nothing todo with openness, but with the fact that the responsible
> > developer / project manager will have the final say.
>
> This means Novell employees are the responsible developer / project
> manager? Are can somebody from the opensuse community be also
> responsible for certain packages? E.g. vim 6.4 is released this weekend
> and I would like a rpm for this: will it be available in the SUSE or
> other available YaST repositories or should I create my own?
... well, this is a classical example that will be solved, as soon as we
have the public build infrastrucutre in place ;)
Regards
Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
