[
https://issues.apache.org/jira/browse/TAVERNA-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419235#comment-16419235
]
Stian Soiland-Reyes edited comment on TAVERNA-1037 at 3/29/18 3:55 PM:
-----------------------------------------------------------------------
Hi, [~cr7] - I'm afraid the [GSOC
deadline|https://developers.google.com/open-source/gsoc/timeline] just passed
to apply as a funded GSOC student - but you are of course free to join our open
source project on your own time and submit pull requests!
See
https://taverna.incubator.apache.org/download/code/#contribute-to-apache-taverna
for a general intro.
As a brief overview:
* Sign up to the dev@taverna mailing list
http://taverna.incubator.apache.org/contact
* You can also chat on http://gitter.im/apache/taverna but be aware of timezone
challenges
* Try to build (one of the) modules from
https://taverna.incubator.apache.org/download/code/
* Feel free to ask if a weird error pops up! We can help you set up your
build environment.
* Find a bug or idea you want to work on - we have both old and new issues in
https://issues.apache.org/jira/projects/TAVERNA/summary
* Fork on GitHub, check out to your own branch
* Once you have some kind of (small) fix, raise a Pull Request. Rather multiple
PRs than a single big one!
* Respond to questions to the Pull request, e.g. for suggested code improvements
* If no-one responds to your PR for a few days, perhaps they were on their
Easter break? Just ping on dev@taverna
If you do this consistently, and perhaps even join in other discussions; then
the project is likely to vote you to invite you as a *committer*, in which case
you will get direct write access etc. - however we often still use pull
requests just to structure the discussion so that is more of a "badge" than a
practical difference :)
This way of contributing is generally true for every Apache project.
was (Author: stain):
Hi, [~cr7] - I'm afraid the [GSOC
deadline|https://developers.google.com/open-source/gsoc/timeline] just passed
to apply as a funded GSOC student - but you are of course free to join our open
source project on your own time and submit pull requests!
See
https://taverna.incubator.apache.org/download/code/#contribute-to-apache-taverna
for a general intro.
As a brief overview:
* Sign up to the dev@taverna mailing list
* You can also chat on http://gitter.im/apache/taverna but be aware of timezone
challenges
* Try to build (one of the) modules from
https://taverna.incubator.apache.org/download/code/
* Feel free to ask if a weird error pops up! We can help you set up your
build environment.
* Find a bug or idea you want to work on - we have both old and new issues in
https://issues.apache.org/jira/projects/TAVERNA/summary
* Fork on GitHub, check out to your own branch
* Once you have some kind of (small) fix, raise a Pull Request. Rather multiple
PRs than a single big one!
* Respond to questions to the Pull request, e.g. for suggested code improvements
* If no-one responds to your PR for a few days, perhaps they were on their
Easter break? Just ping on dev@taverna
If you do this consistently, and perhaps even join in other discussions; then
the project is likely to vote you to invite you as a *committer*, in which case
you will get direct write access etc. - however we often still use pull
requests just to structure the discussion so that is more of a "badge" than a
practical difference :)
> GSOC: Use arcp:// URIs in RO Bundle
> -----------------------------------
>
> Key: TAVERNA-1037
> URL: https://issues.apache.org/jira/browse/TAVERNA-1037
> Project: Apache Taverna
> Issue Type: New Feature
> Components: Taverna Language
> Environment: Java, HTTP
> Reporter: Stian Soiland-Reyes
> Priority: Major
> Labels: RFC, gsoc2018, java, uri
>
> This is a project idea for [Google Summer of
> Code|https://summerofcode.withgoogle.com/] (GSOC). To discuss this or other
> ideas with your potential mentor from the Apache Taverna project, sign up and
> post to the
> [dev@taverna|https://taverna.incubator.apache.org/community/lists.html#devtaverna]
> list, including "[GSOC]" in the subject. You may also comment on this Jira
> issue if you have created an account.
> --
> The
> [ro-bundle|https://github.com/apache/incubator-taverna-language/tree/master/taverna-robundle]
> module of Taverna Language currently uses app:// URIs in its Java
> [FileSystem|https://docs.oracle.com/javase/8/docs/api/java/nio/file/FileSystem.html]
> URIs and thus also in its RDF loading.
> This was in accordance with [RO bundle
> spec|https://researchobject.github.io/specifications/bundle/#absolute-uris] –
> however the app:// URI scheme has been since abandoned.
> The arcp URI scheme has been proposed as an alternative to describe paths
> within an archive (e.g. ZIP file):
> [https://tools.ietf.org/id/draft-soilandreyes-arcp-03.html] (This
> Internet-Draft is progressing towards an RFC)
> This proposal suggests to modify RO Bundle to use arcp:// URIs – but not just
> modify app://bf5a0cab-86d7-40da-b588-1ce4953ae13d/ to
> arcp://uuid,bf5a0cab-86d7-40da-b588-1ce4953ae13d/ - but to support the other
> mechanisms suggested by arcp in
> [https://tools.ietf.org/id/draft-soilandreyes-arcp-03.html#rfc.section.4.1]
> That is, it should be possible to open an RO Bundle from a fixed URL as
> identifier, or using its sha256 checksum in readonly mode.
> It should also be possible to lookup an RO Bundle URI from a .well-known
> endpoint as defined in
> [https://tools.ietf.org/id/draft-soilandreyes-arcp-03.html#rfc.section.4.4]
> Extensions to this project could be to add a Java URL handler so that URLs
> from an opened RO Bundle file system also can be used as java.net.URLs. Also
> it could develop a new arcp-java module similar to the reference Python
> implementation https://pypi.python.org/pypi/arcp
> Prospective students are expected to participate in the Apache [Taverna
> community|https://taverna.incubator.apache.org/community/lists.html#devtaverna]
> - but are also welcome to join the [IETF |https://www.ietf.org]review
> process in reviewing or improving the arcp Internet-Draft to progress it
> towards RFC.
> Suggested mentor: Stian Soiland-Reyes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
