:) Bloc is in rapid development. Api/logic changes dramatically, not all concepts still clear and Pharo dev list creates to many noise about Bloc. People will start thinking that it is done and will start using it. Then they will ask noob questions or point to something that does not work/not implemented and we know that it is not implemented. Then they may complain about lack of documentation and no examples and in the end they will end up with not the best impression of Bloc and will likely not accept it when it is done. Also it is always complicated to change/remove something that is in use.
Pharo dev list is for "open-beta testing". Bloc list for "close testing". Having in a loop 10 people easier than 100-1000. Complains are acceptable ;) On Nov 6, 2015 11:15 AM, "Sven Van Caekenberghe" <[email protected]> wrote: > Why does it need a separate list ? > > If Bloc is/will become a fundamental part of Pharo it belongs to the > general dev list. > > > On 06 Nov 2015, at 11:07, Aliaksei Syrel <[email protected]> wrote: > > > > Hi Marcus > > > > How much effort would it take to make Bloc list public? > > > > Cheers > > > > On Nov 5, 2015 3:22 PM, "Marcus Denker" <[email protected]> wrote: > > > >> On 05 Nov 2015, at 09:54, Aliaksei Syrel <[email protected]> wrote: > >> > >> Hi > >> > >> Did you choose "Switch universe" or "Switch universe [OSWindow]"? > >> > >> I don't know about Linux but latest version of Brick with latest vm is > stable and confirmed to work on windows and Mac. > >> > >> P.S. For Bloc related stuff we have [email protected] > >> > > But this is a mailingst that is manually managed, if this is supposed to > be public we need to move to to Mailman. > > > > Marcus > > >
