taverna-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Larry Akah <larrya...@gmail.com>
Subject Re: GSoC repositories was Re: GSoC JIRA projects
Date Thu, 07 May 2015 09:02:31 GMT
Thanks i think this is a clear point for me in particular working on the
mobile app project.

cheers.

2015-05-06 19:46 GMT-05:00 Stian Soiland-Reyes <stain@apache.org>:

> GSOC students,
>
>
> The GSOC git repositories have been created, and I also asked INFRA
> for them to be synced to GitHub (which it turns out has to be
> requested separately)
>
>
> The (not-so-useful unless you are a GSOC mentor) repository URLs are:
>
> https://git-wip-us.apache.org/repos/asf/incubator-taverna-mobile
> https://git-wip-us.apache.org/repos/asf/incubator-taverna-databundle-viewer
>
> I have initialized the repositories with a placeholder README.md
> (please edit!) together with the required LICENSE and NOTICE files.
>
> They should appear mirrored to github from 07:00 UTC - after which
> GSOC students should be able to Fork them in GitHub and commit to your
> copies. Then make regular Pull Requests which we (dev@taverna) will be
> able to review and hopefully accept. :)
>
>
> The github URLs should be (from Thursday morning, UK-wise):
>
> https://github.com/apache/incubator-taverna-mobile/
> https://github.com/apache/incubator-taverna-databundle-viewer/
>
>
>
> As for the Taverna Language Command Line GSOC project, I have created
> a placeholder Maven module of taverna-language here:
>
>
> https://github.com/apache/incubator-taverna-language/tree/master/taverna-language-commandline
>
> It is not currently enabled from the parent <modules>, so it should
> not affect build/release of the taverna-language (except for any
> Apache file headers violations, which we must check on accepting pull
> requests anyway)
>
> So here simply fork incubator-taverna-language in GitHub, and in your
> repository modify the taverna-language-commandline/ folder, and then
> submit regular pull requests back.
>
>
>
> Happy coding!  Any questions, just ask on this list. Your mentor
> should be able to help you with practical things like ICLAs and how to
> create a pull request.
>
> You will probably want to start with firing some high-level tasks into
> Jira -- it would be good to see some kind of reflection of the plan
> from your proposals in the Jira issues.
>
>
> Apologies for not structuring this email better.. it is getting late
> at night :-/
>
>
> On 5 May 2015 at 16:16, Ian Dunlop <Ian.Dunlop@manchester.ac.uk> wrote:
> > Hello,
> >
> > I've asked for the repos.
> >
> > https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-9602
> >
> > https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-9601
> >
> > Cheers,
> >
> > Ian
> >
> > -----Original Message-----
> > From: Stian Soiland-Reyes [mailto:stain@apache.org]
> > Sent: 05 May 2015 15:27
> > To: dev@taverna.incubator.apache.org
> > Subject: Re: GSoC repositories was Re: GSoC JIRA projects
> >
> > So the GSOC students shouldn't ask INFRA, one of the existing Taverna
> committers (e.g. you or me!) should.
> >
> > INFRA has made a new landing site for creating issues:
> >
> > https://infrahelp.apache.org/
> >
> > which has the choice for "New Git repository".
> >
> > No need to mention GSOC in the request as it's just another Taverna repo.
> >
> > (Don't forget to add it at http://taverna.incubator.apache.org/code/
> > once it is created!)
> >
> >
> > See
> > https://blogs.apache.org/infra/entry/introducing_jira_service_desk
> >
> > On 5 May 2015 at 15:15, Ian Dunlop <Ian.Dunlop@manchester.ac.uk> wrote:
> >> Hello,
> >>
> >> Sounds like a good plan. I guess the question people will ask is "how
> >> do I ask Apache INFRA?". Are the details needed on here
> >> http://www.apache.org/dev/infra-contact
> >>
> >> Cheers,
> >>
> >> Ian
> >>
> >> -----Original Message-----
> >> From: Stian Soiland-Reyes [mailto:stain@apache.org]
> >> Sent: 05 May 2015 15:12
> >> To: dev@taverna.incubator.apache.org
> >> Subject: Re: GSoC repositories was Re: GSoC JIRA projects
> >>
> >> I think the proposal is that the existing Taverna committers ask Apache
> INFRA to create three new git repositories for the GSOC projects.
> >>
> >> I suggest we do not include "gsoc" in the title as we hope that these
> new modules will live on beyond GSOC - with or without the student.
> >>
> >> The Taverna Language command line can probably go in as a fork/new
> >> Maven module of the existing incubator-taverna-language git repository
> >> - while the other two I agree are new things and therefore should have
> new repositories.
> >>
> >>
> >> So I suggest to ask INFRA to create:
> >>
> >> incubator-taverna-databundle-viewer
> >> incubator-taverna-mobile
> >>
> >> with the same setup as the other Taverna ones. If no-one here says
> otherwise, I'll do so on Thursday.
> >>
> >>
> >> Each of the students will then Fork "their" repo in GitHub, where you
> can push your code every day, and regularly (e.g. every week or so) raise
> pull requests back again to the corresponding Apache GSOC repository. At
> this point the ICLA needs to be signed and on file with Apache.
> >>
> >>
> >> That would notify dev@taverna, and then any of the Taverna committers
> (usually the GSOC mentor) will review and merge/accept, or ask for some
> fixes (e.g. a file was missing from the commit, or a dependency didn't have
> a valid open source license).
> >>
> >> When the code is accepted it will be reflected back in the official
> repository and appear at say apache/incubator-taverna-databundle-viewer.
> >>
> >>
> >> The /apache/ GitHub repositories are mirrors from git.apache.org - so
> merging for us is two git commands in the shell rather than a single button
> click on GitHub, but it's not too different.
> >>
> >> So the students will be able to contribute like any other newcomers to
> the project using GitHub forks and pull requests - the only difference is
> that two of the students will contribute into brand new git repositories.
> >>
> >> Does this sound like a workable plan?
> >>
> >>
> >> On 1 May 2015 at 15:17, Ian Dunlop <Ian.Dunlop@manchester.ac.uk> wrote:
> >>> Hello,
> >>>
> >>> I think the github repos are just read only mirrors of the apache git
> repos. So you push to the apache repo but they are then copied to github.
> Not sure why, I guess the github repos make the projects more publicly
> visible.
> >>>
> >>> Cheers,
> >>>
> >>> Ian
> >>>
> >>> -----Original Message-----
> >>> From: Denis Karyakin [mailto:samhane.me@gmail.com]
> >>> Sent: 01 May 2015 14:49
> >>> To: dev@taverna.incubator.apache.org
> >>> Subject: Re: GSoC repositories was Re: GSoC JIRA projects
> >>>
> >>> It's only proposed names for repositories, not created already I
> >>> think, someone from apache will create these repositories (if it is
> >>> possible)
> >>> And why apache repositories on github has read-only access? We will
> push our commits to git://git.apache.org/ ?
> >>>
> >>>
> >>> 2015-05-01 16:37 GMT+03:00 Larry Akah <larryakah@gmail.com>:
> >>>
> >>>> The code repo link give me a 404 error page :
> >>>> https://github.com/apache/incubator-taverna-gsoc-mobile
> >>>>
> >>>> To which address should i send the ICLA ?
> >>>>
> >>>> Thanks
> >>>>
> >>>> 2015-05-01 8:29 GMT-05:00 Larry Akah <larryakah@gmail.com>:
> >>>>
> >>>> > Great , Thanks @Ian
> >>>> >
> >>>> > Cheers
> >>>> >
> >>>> > 2015-05-01 8:09 GMT-05:00 alaninmcr <alaninmcr@googlemail.com>:
> >>>> >
> >>>> > On 30/04/2015 15:41, Larry Akah wrote:
> >>>> >>
> >>>> >>> Yeah, important one @Ian, how do we host code?
> >>>> >>>
> >>>> >>
> >>>> >> I think there should be three new repositories (one for each
> project).
> >>>> >>
> >>>> >> Perhaps,
> >>>> >> https://github.com/apache/incubator-taverna-gsoc-databundle-viewe
> >>>> >> r
> >>>> >> https://github.com/apache/incubator-taverna-gsoc-language-command
> >>>> >> - l ine https://github.com/apache/incubator-taverna-gsoc-mobile
> >>>> >>
> >>>> >> Although they look a bit strange, I think their content would
be
> >>>> obvious.
> >>>> >>
> >>>> >> The GSoC students need to sign the Apache CLA
> >>>> >> https://www.apache.org/licenses/#clas
> >>>> >>
> >>>> >> Alan
> >>>> >>
> >>>> >>
> >>>> >
> >>>> >
> >>>> > --
> >>>> > *Akah Larry N.H*
> >>>> >
> >>>> > *Lead Software Engineer @ GiftedMom* *Founder IceTech Inc*
> >>>> > *www.iceteck.com*
> >>>> >
> >>>> > Developing technologies for emergence and sustainable development.
> >>>> >
> >>>> >
> >>>>
> >>>>
> >>>> --
> >>>> *Akah Larry N.H*
> >>>>
> >>>> *Lead Software Engineer @ GiftedMom* *Founder IceTech Inc*
> >>>> *www.iceteck.com*
> >>>>
> >>>> Developing technologies for emergence and sustainable development.
> >>>>
> >>
> >>
> >>
> >> --
> >> Stian Soiland-Reyes
> >> Apache Taverna (incubating), Apache Commons RDF (incubating)
> >> http://orcid.org/0000-0001-9842-9718
> >
> >
> >
> > --
> > Stian Soiland-Reyes
> > Apache Taverna (incubating), Apache Commons RDF (incubating)
> > http://orcid.org/0000-0001-9842-9718
>
>
>
> --
> Stian Soiland-Reyes
> Apache Taverna (incubating), Apache Commons RDF (incubating)
> http://orcid.org/0000-0001-9842-9718
>



-- 
*Akah Larry N.H*

*Lead Software Engineer @ GiftedMom*
*Founder IceTech Inc*
*www.iceteck.com*

Developing technologies for emergence and sustainable development.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message