[Pharo-dev] CodeImporter and Rubric will not be external projects managed by configurations

Nicolai Hess nicolaihess at gmail.com
Fri Jun 10 04:55:14 EDT 2016


I don't much about code importer, but
+1 for rubric

2016-06-10 10:50 GMT+02:00 Sven Van Caekenberghe <sven at stfx.eu>:

> Yes, good idea, external projects only make sense if they really can exist
> outside Pharo and if they are actively maintained as such.
>
> > On 10 Jun 2016, at 10:43, Pavel Krivanek <pavel.krivanek at gmail.com>
> wrote:
> >
> > Hi,
> >
> > to make our and your lifes easier we want to stop to manage CodeImporter
> and Rubric as external projects. For CodeImporter it makes no sense to have
> it as external project and moreover why to have special configuration for
> only one package. The Rubric has a lot of small updates, not defined
> maintainer and manage it externally is a pain for everyone.
> >
> > Let us know if you have something against it.
> >
> > Cheers,
> > -- Pavel
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20160610/a9d3a052/attachment-0002.html>


More information about the Pharo-dev mailing list