Am 14.08.21 um 13:33 schrieb Peter Kovacs:
Last discussion on this topic is at [1]

[1] https://lists.apache.org/thread.html/r64090cf9de98c0147098b5d7d58b5f248c71b42e06d3dcb1c536bc88%40%3Cdev.openoffice.apache.org%3E +1 to move to git. I would separate each tool in an own repository. But as long as it is done I would agree to a devtools repository.

To migrate it back into OpenOffice.git I am at -1 because OpenOffice Code + Build environment is already hard to learn. Especially for new commers.

It is better to cluster by topics.

I also think that code and tools should be separated.

We have the following tools (or maybe also some more):

aoo-stats
bootstrap-connector
build-scripts
bz-tools
genUpdateFeed
guno-extension
hg2svn
lazybones-templates
list-stats
release-scripts
scripts
sdk-examples
svn-stats
updateVersion

I don't think that we should create an own repo for each of them. This would be too much overhead. Please let us keep all tools in 1 repo together. It's just 25 MB of space or a few MBs more.

Marcus



On 12.08.21 18:00, Jim Jagielski wrote:

Any other opinions or comments?

On Aug 6, 2021, at 12:52 PM, Jim Jagielski <j...@jagunet.com> wrote:

To me, it being within OpenOffice.git makes the most sense... but I'm fine either way

On Aug 6, 2021, at 12:49 PM, Dave Fisher <wave4d...@comcast.net> wrote:

Within /Apache/OpenOffice.git repository? Or a new /Apache/OpenOffice-devtools.git?

+1, especially if history is preserved.

Of course there would be wiki and webpages to update.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to