The name of GitHub repository

[cfbsoftware]

Helmut seems to operate just fine with his Dos and dif capabilities to produce his BB1.7
Why not adopt his technique (and generalize if necessary)?

Sounds good to me. The KISS principle is very much in line with the Oberon philosophy. I also like the 'eat your own dog food principle' - it is always encouraging when a software tools developer uses his own tools. It is also a good way of testing your own tools and identifying any deficiencies in user-friendliness. I have found that to be so when using CPIde to develop Astrobe.

If the Centre version of BlackBox was likely to be actively worked on by more than a couple of people at the same time we would need something more sophisticated but that appears to be unlikely in the immediate future.

[DGDanforth]

If BlackBox is so good then why aren't we using it to maintain it?
So I agree with you Chris. I did work for a company that required us to use the
software it developed in its own development process. That works nicely and
keeps one honest.

[Ivan Denisov]

Helmut seems to operate just fine with his Dos and dif capabilities to produce his BB1.7
Why not adopt his technique (and generalize if necessary)?

Dear, Douglas, and others who are not in touch with version controls systems, we have no resources to develop our own system. The world uses git, and half of the team for sure ready to keep it on. You will see the brilliance of that approach later. That does not mean that you can not use Dos or other tools. The solved question is about public repository and track of our development.

Now the question is, how to name the repository?

[DGDanforth]

Helmut seems to operate just fine with his Dos and dif capabilities to produce his BB1.7
Why not adopt his technique (and generalize if necessary)?

Dear, Douglas, and others who are not in touch with version controls systems, we have no resources to develop our own system. The world uses git, and half of the team for sure ready to keep it on. You will see the brilliance of that approach later. That does not mean that you can not use Dos or other tools. The solved question is about public repository and track of our development.

Now the question is, how to name the repository?

"We have no resources to develop our own system". If that is true then we have no resources to maintain our system.
"The solved question is about public repository and track of our development". What do you mean by 'public'? Do you mean by people other than the members of the center, or do you mean the center members?
If you want to get me involved with the development process then I need a system that is simple.
Git is not simple. When I finally got it installed and running it eat up 1.9 GB of my disk.

Now, I assume that 'GitHub' is related to 'Git' by making 'Git' accessible 'in the cloud' i.e. on a server somewhere so that we (center members) don't need to have a copy of 'Git' on our own machines. Is that correct?

I really abhor Unix (even though I was paid in 1979 $3,000 to develop a Unix shell to run on a P-Code machine). So the more we stay away from Unix based systems (or at least hide the mind set) the better, in my opinion.

The name: BBDev is also a possibility

[cfbsoftware]

So the more we stay away from Unix based systems (or at least hide the mind set) the better, in my opinion.

Absolutely! BlackBox 1.6 is a Windows system. If it is not feasible to use a BlackBox tool to perform the extremely simple tasks involved in maintaining BlackBox then we should at least use a Windows-based solution. BlackBox is a relatively simple system - it is not a bloatware monstrosity like gcc or FreePascal that that needs a bloatware SCCS just to prevent it from imploding.

There already exists an alternative BlackBox for Linux group for those who are interested in going down that path.

[Ivan Denisov]

"We have no resources to develop our own system". If that is true then we have no resources to maintain our system.
"The solved question is about public repository and track of our development". What do you mean by 'public'? Do you mean by people other than the members of the center, or do you mean the center members?
If you want to get me involved with the development process then I need a system that is simple.
Git is not simple. When I finally got it installed and running it eat up 1.9 GB of my disk.

Now, I assume that 'GitHub' is related to 'Git' by making 'Git' accessible 'in the cloud' i.e. on a server somewhere so that we (center members) don't need to have a copy of 'Git' on our own machines. Is that correct?

I really abhor Unix (even though I was paid in 1979 $3,000 to develop a Unix shell to run on a P-Code machine). So the more we stay away from Unix based systems (or at least hide the mind set) the better, in my opinion.

The name: BBDev is also a possibility

The resources for using is less than for developing. Will you argue with what point?

Regular Git can not take 1.9 Gb of your space. Use this site to download 15Mb distributive: http://git-scm.com/download/win

It will take ~82Mb of your disk after been installed:

git-r.png (24.27 KiB) Viewed 10281 times

If you do not want to use it THAT IS NOT PROBLEM! You can always download ZIP archive with last commit and make some test changes there. Then you can propose your solution on the forum here or in Bug tracker and somebody will include you fix with marking the authorship.

'Public' means open for download and push request, that means that any person can have access to each step of development and suggest some fix, however it will not be written in the repository until the center does not take this solution.

[Ivan Denisov]

So the more we stay away from Unix based systems (or at least hide the mind set) the better, in my opinion.

Absolutely! BlackBox 1.6 is a Windows system. If it is not feasible to use a BlackBox tool to perform the extremely simple tasks involved in maintaining BlackBox then we should at least use a Windows-based solution. BlackBox is a relatively simple system - it is not a bloatware monstrosity like gcc or FreePascal that that needs a bloatware SCCS just to prevent it from imploding.

Each developer can use any tool he wants. We chose the repository system, not the tool for everybody. It does not require any Unix behaviour from you. So please, do not panic!

There already exists an alternative BlackBox for Linux group for those who are interested in going down that path.

You misunderstood that point, there are no group, this is thread in the forum with no group. Each member can participate in discussions there, not only some Linux fans. Second point is that there is GUI version of BlackBox for Linux that does not need command line communication.

[DGDanforth]

Ivan,
Thank you for the link : http://git-scm.com/download/win
I have download and installed Git from it.

I have started a discussion (under Discussions) called How to Use Git.
Please take look at it.

-Doug

[Ivan Denisov]

According the voting results I made the organisation in GitHub and push the final Oberon microsystems 1.6 version of BlackBox there.
https://github.com/BlackBoxCenter

Now everybody can download latest BlackBox Component Builder by the link:
https://github.com/BlackBoxCenter/bbcb/ ... master.zip

Also there are public platform for posting issues:
https://github.com/BlackBoxCenter/bbcb/issues

We can rename organisation or repository any time if there will be some necessity and decision.

Please, send me your GitHub account names or post them here for I can add everybody to the organisation members.

[Josef Templ]

In general, a VCS (version control system) is intended to be used for maintaining the sources of a project,
not the downloadable executable or zip file. In the case of BlackBox this includes the module sources,
the resources and the documentation files. The object files, symbol files, and and exe file
are not to be kept under version control. This would blow up the repository and introduce a lot
of changed files whenever you recompile.

A download page must be maintained (in addition to the Git repository) as it has been done before
by ominc or CPC. The download page should also have a history of older downloads and
a description of changes for every new version. This is what the regular user of BlackBox sees.

- Josef