Community
Participate
Working Groups
The heart of this proposal is to move the "b3 aggregator" to CBI. This seems logical, since while it may have some "outside" users, it is primarily used for our yearly Simultaneous Release, AFAIK. My motivation is to give that aggregator a more visible, central home to both make it easier to maintain and encourage contributions. One issue is what to do with the "beelang" modules. As far as I know, the "b-language" effort stopped long ago. I propose to "move them" with the aggregator modules, for simplicity, but then they would soon be removed from 'master' in their CBI home. In effect, this would "archive" the b3 project. I am open to suggestions! I do have a "draft" of a Tycho build running (see bug 487478) and think I have identified the main modules that make up the b3 aggregator editor. I am opening this bug for discussion, and eventually, will document the concrete steps needed to make "the move". Typically when a project like this moves to another project, all the committers also move to the new project. I am very open to suggestions on this point, but since the existing committers have all been very inactive, for a very long time, I suggest they not move automatically. Of course, if any of them say they do want to keep commit rights, that is fine with me. Similarly, if, in the future, an existing committer wants to work on it again, I am sure they could be voted into CBI relatively easily. Suggestions welcome. I would expect that things like package names (for the aggregator related bundles) would change to contain 'cbi' instead of 'b3'. Comments?
* +1 to the move. * beelang can be archived as Cloudsmith was the only user, and the code base is not maintained. It is referenced a lot in older comments on the Xtext mailing list, but that is no longer relevant. * I do not need to be a comitter on the project where the b3 aggregator is moved. I have no time to contribute.
(In reply to David Williams from comment #0) > In effect, this would "archive" the b3 project. I am open to suggestions! I don't mean to "bait and switch", but perhaps the cleanest solution is to formally archive (terminate) the whole b3 project so it can be found in the future following the typical paths. But at the same time move the b3 aggregator related bits to the CBI project. And, IMHO, probably still easiest to move the whole git repo, and then just remove the beelang modules from the master branch. I am not that familiar with moving subsets repositories, but familiar enough to know it is not as easy as copying files. (Like in good 'ol CVS :)
[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI. This bug was previous part of "meta" component in EMFT.b3]
I think THIS bug should not have moved so am moving it back. It was the counter part to a similar bug in CBI (bug 487543) and I think *this* bug is now about "shutting down" EMFT.b3 once the "transfer" is complete to CBI.
the Git repositories, Wiki pages, and the 4.4 update site have all been moved to "CBI space", so as far as I am concerned, the project has "moved", and EMFT.b3 can now be archived.
