Rename project from `core` to `harbour` about core HOT 4 CLOSED

I think such double naming is 1. redundant, 2. leaves no room for other components, f.e. 'contribs', or individual contrib names, like 'hbtest', 3. 'harbour-core' might solve that, but it's long and not 8.3 compatible, 4. it's very easy to rename it in forks if someone wants to.

from core.

1 redundant,

It's common for github, and everybody know thats related to an organization. Redundant, but not ambiguous.

github.com/ [ user | org ] / [ project ]

2 leaves no room for other components, f.e. 'contribs', or individual contrib names, like 'hbtest',

Don't agree!

If each contrib have it's own repository, it wold be fine!

/harbour/hbtest
/harbour/hbfbird
....

3 'harbour-core' might solve that, but it's long and not 8.3 compatible,

/harbour/harbour is OK, for me, as I already mentioned before

4 it's very easy to rename it in forks if someone wants to.

Agreed!

from core.

'core' is also used in other GitHub projects, 'project-core' likewise. There are examples for all variation.
I think 'core' better tells the story that it's the core package, than 'harbour'.

Anyhow, it will be the job of project maintainers to change it and promote new links if deemed useful, depending on new goals and ideas.

[ BTW, contribs in mainstream Harbour are still not fully self-contained. I've made some steps to further untie them from core, so there (in fork) by now, only the /package generator scripts make references to contribs (but some contribs still make references to each other, f.e. to 3rd/sqlite3). For an ultimate solution each contrib will have to be packaged (.deb/.rpm/etc) separately or even better Harbour will have to get its own package management system. ]

from core.

Ok, you convinced me!

from core.