[
https://issues.apache.org/jira/browse/COMDEV-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959661#comment-17959661
]
Hervé Boutemy commented on COMDEV-561:
--------------------------------------
with ATR going forward and promoting declaring every software project released
at Apache, if we do it well, these projects will be declared with DOAP for
projects.a.o to have a more realistic view than what is displayed for 20 years
(that was "as complete as possible")
I'm convinced that our 200 Committees are releasing more something like 2000+
projects than the current 300
=> clearly we'll have a bunch of work in projects.a.o to manage that growth and
adapt our approach
I think svn will be a strong problem to push p.a.o collaboration from all ASF
committers
we need to switch to Git
[~sebb] how do you want us to work on it? I don't have access to the underlying
machine = what restricts me on doing anything without breaking
should I start by getting ssh access to be able to help on the migration?
[~humbedooh] is there anything I should do to be able to see this machine
running? (I know updating is done by Puppet, so I expect only being able to
debug if anything does not work as I expect)
> migrate projects to Git
> -----------------------
>
> Key: COMDEV-561
> URL: https://issues.apache.org/jira/browse/COMDEV-561
> Project: Community Development
> Issue Type: Improvement
> Components: Projects Tool
> Reporter: Hervé Boutemy
> Priority: Major
>
> in COMDEV-288, we let the source code in svn but created a svn2git Git mirror
> https://github.com/apache/comdev-projects
> next step is to make Git read-write
> full impact analysis to be done, but we can immediately list a few topics:
> - cronjobs update to commit to Git instead of svn
> - switch to ASF website publication from Git instead of svn (probably through
> .asf.yaml)
> anything else?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
