The name of GitHub repository

[Ivan Denisov]

Nobody will develop repository tool for BlackBox, because it is a time waste to do this, when there are a lot of free tools.

Actually I am in the process of doing that. Mostly for my own teaching (edification). It forces me to address the needed issues in source code control. I can also use the tool for keeping track of my own projects.

I suspect that the resulting tool (BBGit?) will be tiny compared to git. It will not have all the bells and whistles (features) of git but should be sufficient.

Doug, that is good, that you will develop your tool in future. Now we need to maintain the BlackBox and people voted for GitHub with Redmine. Let's vote again and add in the poll list the point "Some version control tool from Doug" and if the most people voted for this we will wait for your tool.

[Josef Templ]

In my experience, it is a complete waste of time to develop your own tools for
the use cases already covered by standard tools that are well tested and freely available.
I cannot see any advantage. I use svn since many years with BlackBox and never
felt like I need anything integrated into BlackBox for that purpose.
The same is with Git. Do yourself a favor and focus on the missing parts
of the tool chain we need. The build machine for a continuous build process,
for example. We need something like a command-line BlackBox compiler,
for automating the build. I don't know if something like this already exists.
If not, this is an important work package.

- Josef

[Ivan Denisov]

In my experience, it is a complete waste of time to develop your own tools for
the use cases already covered by standard tools that are well tested and freely available.
I cannot see any advantage. I use svn since many years with BlackBox and never
felt like I need anything integrated into BlackBox for that purpose.
The same is with Git.

I agree with you, however if the Center will consolidate around Doug point of view we should look at this carefully.

Do yourself a favor and focus on the missing parts
of the tool chain we need. The build machine for a continuous build process,
for example. We need something like a command-line BlackBox compiler,
for automating the build. I don't know if something like this already exists.
If not, this is an important work package.

It exists and used in Linux project. http://gitlab.molpit.com/oberon/blackbox-freenix
It works very well, so will be no problem. I will test it for our purpose soon.

[Josef Templ]

It exists and used in Linux project. http://gitlab.molpit.com/oberon/blackbox-freenix
It works very well, so will be no problem. I will test it for our purpose soon.

This is good news. So we are only a few configuration steps away from an automated
build process. When this approach works it can be shown to the center members and
it can be decided whether we stick to it or if we need some other approach.

- Josef

[DGDanforth]

In my experience, it is a complete waste of time to develop your own tools for
the use cases already covered by standard tools that are well tested and freely available.
I cannot see any advantage. I use svn since many years with BlackBox and never
felt like I need anything integrated into BlackBox for that purpose.
The same is with Git. Do yourself a favor and focus on the missing parts
of the tool chain we need. The build machine for a continuous build process,
for example. We need something like a command-line BlackBox compiler,
for automating the build. I don't know if something like this already exists.
If not, this is an important work package.

- Josef

I have a program I wrote called MyBuilder which takes a module name as the root of a module hierarchy that is built automatically from the imports the root uses (and on out from each import). It separates the BB core files from the user files so that a build does not recompile the BB core files. The separation is maintained internally by specifying a 'set' of files. MyBuilder also keeps tract of menus and includes them. Hence with two mouse clicks I can specify the root and then create an executable (if that is what I want). I have used MyBuilder successfully to release software to a client of mine. Without MyBuilder I was making too many mistakes in the release process.

For building BlackBox, the set of files could easily be changed to include the BB core files.

[DGDanforth]

In my experience, it is a complete waste of time to develop your own tools for
the use cases already covered by standard tools that are well tested and freely available.
I cannot see any advantage. I use svn since many years with BlackBox and never
felt like I need anything integrated into BlackBox for that purpose.
- Josef

Fine. I still need to do this so I can understand the parts and needs of git.

-Doug

[ReneK]

I am totally disagree with Rene position about repository. Because we did not have the tools we do nothing for one year. Now members voted and we have Center decision about GitHub, Redmine and 1.6 as start point. Now we can start working discussing changes. We have tools for discussion and fixations. Nobody will develop repository tool for BlackBox, because it is a time waste to do this, when there are a lot of free tools.

10 people voted. Right.

Of those, only 4 rallied around one option.

Now, where do we have a rule that a minority vote (40%) is enough to decide an issue?

[Ivan Denisov]

Rene, there are three rules about voting accepted by the Center:
1. Only chairperson start Centrer decision votes (that does not mean that other can not create polls for knowing the Center opinion, but this results will have no value except information)
2. Three Center members can ask chairperson to make voting
3. 80% quorum is required for decision became valid

We have no accepted rules more.

Abstained people counted as people with no opinion about this question, but they counted for quorum. Abstained are delegating the decision to members, who have the knowledge about this question. That is exact that happened, as I see, many people do not care about the place for sources, however repository is required (that is the reason why the voting was initiated and conducted). As you can see from the vote 6 of 10 understands the repository needs very well and suggest their options.

If you think that we need some more strict rules, lets vote about this. However I do not want such strict rules about majority...