What is that? R3N?<\/p>\n
Maybe you are aware of the open sourcing of Rebol on 12-12-2012. The sources to an incomplete Rebol3 that used to be in development were given a chance to survive.<\/p>\n
There was much enthousiasm but when Pull Requests were not applied by the owner and the second in command all of a sudden disappeared from the scene without any notification and the community was left adrift in the ocean.<\/p>\n
Nobody wanted the responsibility nor was there any chance of getting control of the repo. The only way to go was to proceed on a personal forked branch. But this brings the problem that changes are considered personal wishes, not communicated within the community, not the way Rebol 3 should develop.\u00a0 But this kind of criticism coming from people that had merely turned away or did nothing, to me it does not make sense.<\/p>\n
So lucky for our community one single person with the aid of the friends that stayed or came by to discuss took it upon himself to push the repo along in his fork. He wanted to get rid of the flaws that were in the repository, making it compile under much stricter C compilers, get rid of wrong developments, integrating the code that was contributed by the companies Saphirion and Atronix, making the codebase solid.<\/p>\n
This now has reached a point where the company Atronix even considers to start and use this fork as the base for one of their main products. So definite kudos to Brian for this achievement.<\/p>\n
So with the original repo open sourced but in a ‘cast in stone’ sense and the only fork that has been seriously developed in a private repo it was clear that something had to be done to get the community out of the impasse.<\/p>\n
There had been a tiny discussion about the original repo being r3a (alpha), the new version could become a r3b, but as it already had a project name of REN-C so probably r3c would be better as not to suggest Beta using r3b. So this is where my tiny part comes in play. I did suggest to skip right over to using r3n. R3 Next generation(?). This would be a nice wordplay of using the 3 as E and the name of the project would become REN. As a welcome coincidence there is also a Rebol offspring project that is called REN. This REN stands for REadable Notation and is sort of a generalisation of using a Rebol like language to describe information, just like the popular JSON. (But better of course \ud83d\ude09 ) https:\/\/github.com\/humanistic\/REN<\/a> and http:\/\/pointillistic.com\/ren\/<\/a><\/p>\n I got in contact with the nice folks at github when I discovered the name r3n had already been taken but unused since 2009. Lucky for me they were able to free up the name for reason of inactivity. So I created the r3n github organisation\u00a0https:\/\/github.com\/r3n<\/a> and forked the REN-C fork by HostileFork https:\/\/github.com\/r3n\/ren-c<\/a>.<\/p>\n I invited Graham Chiu and Giulio Lunati to become co-owners of the organisation because they are serious users of the REN-C codebase and were willing to join. I did not invite Brian (yet) because I do not want him to feel pressed with this and give him the freedom to play around end experiment with his views on the language. I think that is also good for the project, to get others involved.<\/p>\n It was about time the Rebol community to take things in their own hand, so that is what happened. I am very confident the R3N organisation will become the place to re-group and start building the next generation Rebol.<\/p>\n Well as always curious about what you have to say, except for you folks that always post info about certain medication \ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":" What is that? R3N? Maybe you are aware of the open sourcing of Rebol on 12-12-2012. The sources to an incomplete Rebol3 that used to be in development were given a chance to survive. There was much enthousiasm but when … Continue reading