I think, that we should not use "Edition" at all. The Center includes most distributors like OberonCore and Helmut Zinn. The idea is to come to the general distribution. There was no "Oberon microsystems Edition", and from my point of view, should not be "Center Edition". Simply — "BlackBox Component Builder".
I am suggesting next points for voting:
* Community Edition
* Center Edition
* BBFWC Edition
* no Edition label, we are making "general" BlackBox like Oberon microsystems did.
issue-#14: Blackbox building pipeline
-
Ivan Denisov
- Posts: 1700
- Joined: Tue Sep 17, 2013 12:21 am
- Location: Russia
-
DGDanforth
- Posts: 1061
- Joined: Tue Sep 17, 2013 1:16 am
- Location: Palo Alto, California, USA
- Contact:
Re: blackbox-1.7-a1-setup (building pipeline)
"no Edition label, we are making "general" BlackBox like Oberon microsystems did"
That would be my preference.
That would be my preference.
-
Josef Templ
- Posts: 2047
- Joined: Tue Sep 17, 2013 6:50 am
Re: blackbox-1.7-a1-setup (building pipeline)
As I see it now, there are two decisions to be made:
1. should we introduce a name at all?
2. if yes, which name?
I would prefer to have a name that clearly distinguishes
our distribution from possible other distributions.
There is at least the OberonCore distribution, the original ominc
distribution, the CPC distributions and in the future there may
even be more distributions.
A possible alternative name would be 'Center Edition'.
May be a native speaker could comment on how this sounds.
Is it more 'professional' style? Is it too general? Is it nonsense?
Other ideas?
- Josef
1. should we introduce a name at all?
2. if yes, which name?
I would prefer to have a name that clearly distinguishes
our distribution from possible other distributions.
There is at least the OberonCore distribution, the original ominc
distribution, the CPC distributions and in the future there may
even be more distributions.
A possible alternative name would be 'Center Edition'.
May be a native speaker could comment on how this sounds.
Is it more 'professional' style? Is it too general? Is it nonsense?
Other ideas?
- Josef
-
Josef Templ
- Posts: 2047
- Joined: Tue Sep 17, 2013 6:50 am
Re: blackbox-1.7-a1-setup (building pipeline)
This seems a bit over-optimistic to me. There are alreadyDGDanforth wrote:"no Edition label, we are making "general" BlackBox like Oberon microsystems did"
That would be my preference.
multiple existing distributions. We have no exclusive rights on this
and by omitting a name it will not change that fact but only add confusion.
- Josef
-
Ivan Denisov
- Posts: 1700
- Joined: Tue Sep 17, 2013 12:21 am
- Location: Russia
Re: blackbox-1.7-a1-setup (building pipeline)
+ 1 option
* change the name of distribution, for example "BlackBox Component Framework" or "Component Pascal Framework" or "YellowPuzzle Component Builder"
Component Pascal Framework can be better for googling than BlackBox ... there are so much other BlackBoxes.
* change the name of distribution, for example "BlackBox Component Framework" or "Component Pascal Framework" or "YellowPuzzle Component Builder"
Component Pascal Framework can be better for googling than BlackBox ... there are so much other BlackBoxes.
-
DGDanforth
- Posts: 1061
- Joined: Tue Sep 17, 2013 1:16 am
- Location: Palo Alto, California, USA
- Contact:
Re: blackbox-1.7-a1-setup (building pipeline)
Perhaps we should get some feedback from the remants of Omic?
Is it important to them to make a distinction between their code and derivatives
of it? Do they wish to 'bless' our efforts by making us the official legacy developers?
-Doug
Is it important to them to make a distinction between their code and derivatives
of it? Do they wish to 'bless' our efforts by making us the official legacy developers?
-Doug
-
Josef Templ
- Posts: 2047
- Joined: Tue Sep 17, 2013 6:50 am
Re: blackbox-1.7-a1-setup (building pipeline)
I just want to let everybody know that Ivan and me have succeeded in setting up the
build engine on our Edis host. It is ready for use, stable, and well tuned for our needs.
Small fixes or improvements may be required but I don't expect any bigger problems.
Some background information can be found on our Wiki.
http://wiki.blackboxframework.org/index ... ild_Engine
and
http://wiki.blackboxframework.org/index ... g_Strategy.
Ivan pointed out correctly that using Jenkins would be a tremendous overkill. Doing it via a simple
cron job that activates the build engine periodically serves our needs perfectly.
The current implementation must be seen as a proposal to the center.
I would, however, like to ask the center members to be careful with
alternative suggestions before fully understanding all the concepts and its application to our repository.
The current proposal follows best practices where possible and meaningful while at the same time
it tries to keep simple things simple. I am convinced that it is not easy to come up with a
much better solution by now.
The current solution supports for example building for topic branches as well as for master, it supports
development stages, it provides consistent version information etc. etc.
It also does a rigorous self test before creating a distribution.
There is only one single place (appbuild/AppVersion.txt) where the currently built version is specified.
This information goes automatically to the About dialog, to Dialog.version and to the generated file names.
There is only one single place where new modules must be added to be compiled and distributed and this place
is the well-known file Dev/Docu/Build-Tool.odc. From here the build engine takes the information which
files to compile and in which order.
- Josef
build engine on our Edis host. It is ready for use, stable, and well tuned for our needs.
Small fixes or improvements may be required but I don't expect any bigger problems.
Some background information can be found on our Wiki.
http://wiki.blackboxframework.org/index ... ild_Engine
and
http://wiki.blackboxframework.org/index ... g_Strategy.
Ivan pointed out correctly that using Jenkins would be a tremendous overkill. Doing it via a simple
cron job that activates the build engine periodically serves our needs perfectly.
The current implementation must be seen as a proposal to the center.
I would, however, like to ask the center members to be careful with
alternative suggestions before fully understanding all the concepts and its application to our repository.
The current proposal follows best practices where possible and meaningful while at the same time
it tries to keep simple things simple. I am convinced that it is not easy to come up with a
much better solution by now.
The current solution supports for example building for topic branches as well as for master, it supports
development stages, it provides consistent version information etc. etc.
It also does a rigorous self test before creating a distribution.
There is only one single place (appbuild/AppVersion.txt) where the currently built version is specified.
This information goes automatically to the About dialog, to Dialog.version and to the generated file names.
There is only one single place where new modules must be added to be compiled and distributed and this place
is the well-known file Dev/Docu/Build-Tool.odc. From here the build engine takes the information which
files to compile and in which order.
- Josef
-
Ivan Denisov
- Posts: 1700
- Joined: Tue Sep 17, 2013 12:21 am
- Location: Russia
Re: blackbox-1.7-a1-setup (building pipeline)
I have started repository and issues tracker from the scratch (links at the top of this board ⇑ ).
After Josef will setup development branch a bit by a single commit, the pipeline will be waiting for our work
Everybody who does not registered in Redmine, please, join us here:
http://redmine.blackboxframework.org/account/register
After Josef will setup development branch a bit by a single commit, the pipeline will be waiting for our work
Everybody who does not registered in Redmine, please, join us here:
http://redmine.blackboxframework.org/account/register
-
Josef Templ
- Posts: 2047
- Joined: Tue Sep 17, 2013 6:50 am
Re: blackbox-1.7-a1-setup (building pipeline)
The build engine is now also available and activated for the cleaned up repository 'blackbox'.
- Josef
- Josef