Hi Andrei,

On 10/16/05, Andrei Dorofeev <dorofeev at gmail.com> wrote:
> Hi Cyril,
>
> I think we could put ath and wificonfig source code on genunix.org as
> long as the WiFi team at Sun agrees to putback all of their changes there
> as well.  Judy Chen and Cecilia Hu are both on this mailing list,
> and they can tell us if this will work for them or not.  I don't know if
> they've used SVN before, but it is probably going to take some time
> to adjust and switch from SCCS to SVN.

I tend to agree. However that shouldn't be a major problem. I went
through this migration once - it is not a rocket science :)

>
> Also, when the offical OpenSolaris SCM system is released, we're going
> to move these projects there.  How many developers outside of Sun

Definitely, no question about it. As soon as a "blessed" SCM will be defined
_and_ launched everything should go there.

> do you think will want to participate in these projects?  I have a feeling
> that the number is not going to be big.  In that case, if the official
> SCM solution is coming soon it might be worth just waiting for it a bit
> longer.

It is hard to say how many people would be involved. I can tell for sure,
however, that if no external SCM repository will be created people will
hardly participate at all. Hosting new and as important as WiFi support
project in externally visible SCM would be a huge example of what
"Open" stands for in OpenSolaris [if properly advertised].
Another thing to consider is that the first step in current plans of
providing "official" SCM solution is creating a SVN mirror of TW tree.
So WiFi project would be an early adaptor and its experience with
SVN would be a useful input for the CAB for making decision on
OpenSolaris-wide SCM tool.

Regards,
        Cyril


> - Andrei
>
> On 10/10/05, Cyril Plisko <cyril.plisko at gmail.com> wrote:
> > On 10/9/05, Andrei Dorofeev <dorofeev at gmail.com> wrote:
> > > Hi Cyril,
> > >
> > > This wasn't done initially becaused there was no official SCM for
> > > the OpenSolaris project at the time ath/wificonfig were released.
> > > Are you suggesting that we put these projects on svn.genunix.org
> > > in the mean time? I think we can do that. Subversion is new to me,
> > > and I am not sure about what exactly would have be done for this.
> > > Could you please explain it?
> > >
> >
> > Andrei,
> >
> > yes, I believe that hosting the project at svn.genunix.org
> > is a good idea. The subversion itself is very similar to the
> > CVS in day-to-day operations. The documentation is
> > excellent and can be found at subversion.tigris.org
> > As for the necessary svn.genunix.org setup - what
> > needs to be done is a new project directory created
> > and I'll need to setup username/passwords for all the
> > developers with commit privileges. All that can be done
> > in a moment. The usual directory structure used in subversion
> > is like that:
> >
> > projectdir/ - everything is here
> > projectdir/trunk - that is where HEAD is kept
> > projectdir/branches - different branches are kept here
> > projectdir/tags - tagged versions are found here
> >
> > However, that structure is by no means mandatory and each
> > project can choose whatever layout people feel suites them most.
> >
> > So, let me know if you want to proceed with it.
> >
> > I, personally, very interested in making it happen.
> >
> > Regards,
> >      Cyril
> >
> > > Thanks,
> > > - Andrei
> > >
> > > On 10/6/05, Cyril Plisko <cyril.plisko at gmail.com> wrote:
> > > > Ladies and gents,
> > > >
> > > > I'd like to suggest keeping ath and wificonfig sources in externally 
> > > > visible
> > > > SCM system. I believe that can engage community into more serious
> > > > particiaption and also will demonstrate Sun's ability to cooperate with
> > > > community. I also think that there are significant number of people out
> > > > there who could contribute to the project.
> > > >
> > > > Regards,
> > > >         Cyril
> > > > _______________________________________________
> > > > laptop-discuss mailing list
> > > > laptop-discuss at opensolaris.org
> > > >
> > >
> >
>

Reply via email to