[
https://issues.apache.org/jira/browse/COMDEV-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379465#comment-16379465
]
Dave Brondsema commented on COMDEV-256:
---------------------------------------
[https://forge-allura.apache.org/docs/development/extending.html] doesn't
mention importers at all, but it should because importers are another way to
extend Allura. So I was thinking as you learn about importers, you could write
a little bit of explanation that could be added to that documentation page.
Writing about what you learn can be a helpful way to learn if you want. If you
do want to try that, feel free to send something on the mailing list and we can
help too.
> Allura - importers / sync for Bitbucket and Gitlab
> --------------------------------------------------
>
> Key: COMDEV-256
> URL: https://issues.apache.org/jira/browse/COMDEV-256
> Project: Community Development
> Issue Type: New Feature
> Components: GSoC/Mentoring ideas
> Reporter: Dave Brondsema
> Priority: Major
> Labels: gsoc2018, mongodb, python
>
> Allura has a solid framework for doing imports, and has implemented this for
> services like GitHub, Google Code and Trac. It covers aspects from
> Git/Hg/SVN to tickets and wikis.
> It would be great to enhance this to support importing & converting data from
> Bitbucket and Gitlab. The level of integration & conversion may vary
> depending on the format and structure of the services.
> Beyond that, related improvements could be made in supporting ongoing
> synchronization of Git/Hg/SVN repositories (not just a one-time import). Or
> importers for JIRA, or improving importing of Allura's own formats.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
