Re: [eclipse.org-eclipsecon-program-committee] Build and Continuous Inte

[David Carver <d_a_carver@xxxxxxxxx>]

Again, let's find the tutorial time, and we can add it in.  But 
something is going to have to give, and I think tutorials on 
Buckminster,  Athena, B3, and Tycho are just as important as P2.

Some tutorial is going to have to get hacked and slashed in order to 
make the time for some other tutorial, so somebody isn't going to be happy.

Dave

Chris Aniszczyk wrote:
> 2010/1/7 David Carver <d_a_carver@xxxxxxxxx <mailto:d_a_carver@xxxxxxxxx>>
>
>     I think P2 is important, but it is only a part of the build story.
>      Yes provisioning is important, but only a piece and a step in the
>     overall build story.   Can you build and use plugins with out P2,
>     sure.
>
>
> It may be part of the build story, but it is the underlying 
> foundation. It's the way people acquire and share Eclipse-based 
> artifacts moving forward.
>
> Our annual release builds a large p2 repository. We have a 
> provisioning technology finally that allows us to produce artifacts 
> and stuff them into a repository and query them.
>
> Like I said before, under the covers, Buckminster, Athena, Tycho use 
> p2 to build things like repositories.
>
>  
>
>     If we can find the time, and somebody wants to drop another
>     Tutorial to make way for it then by all means.  But I think
>     technologies like Buckminster, Buildr for OSGI, Athena, and
>     Maven/Tycho are just as important to the community as a whole, and
>     cover a much wider story in Build and Continuous Integration.
>
>     I would favor even 50 minutes 1 hour hands one sessions like
>     Athena had proposed, so that people can come and ask questions.
>
>     Find the time and we give equal weight to Buckminster, Athena,
>     Tycho, and P2/PDE then we can go from there.
>
>     As for documentation, for P2 that is a whole nother issue all
>     together, and honestly, should be done anyways not just for a
>     conference.
>
>
> This is an advantage of a conference as for some developers, this is 
> the time they can get paid to do documentation exclusively and make it 
> available for everyone.
>
> I like the way the B&CI track is structured now giving equal time to 
> most of the technologies but we would be doing a disservice to our 
> users and adopters if there wasn't solid p2 hands on content in the 
> program. I spend a good part of my work life helping people with p2 
> issues and adoption. The more content we have the better.
>  
> --
> Cheers,
>
> Chris Aniszczyk
> http://aniszczyk.org
> ------------------------------------------------------------------------
>
> _______________________________________________
> eclipse.org-eclipsecon-program-committee mailing list
> eclipse.org-eclipsecon-program-committee@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-eclipsecon-program-committee
>