Re: [OpenScienceFramework] [technical] code collaboration on dvn-python-client

19 views
Skip to first unread message

Philip Durbin

unread,
Jan 23, 2014, 3:30:18 PM1/23/14
to openscienc...@googlegroups.com, Robert Liebowitz, dataverse...@googlegroups.com
Ok, I believe Sheila and I just hammered out the details well enough
at http://irclog.iq.harvard.edu/dvn/2014-01-23

I just gave Sheila the same access to the repo that Jeff and Josh
have. She's going to merge her changes and Robert's changes into the
upstream repo at https://github.com/IQSS/dvn-client-python

Sheila, thank you so much for helping with this effort. We really
appreciate it and are excited that ResearchCompendia and OSF are both
interested in using Dataverse APIs. We have both projects flagged as
"coming soon" at http://thedata.org/book/apps :)

I'm going to cc our dataverse-community list as well to keep everyone
in the loop. Exciting times! Pythonistas unite! API ALL THE THINGS!

Phil


On Thu, Jan 23, 2014 at 2:39 PM, sheila miguez <she...@pobox.com> wrote:
> Hi all,
>
> I've discussed this some in #dvn. Ideally I'd like commit privs and hope to
> get at least one other person who is interested in having commit privs, or
> at least interested enough to help review my code. I cringe when I commit to
> master without any review, but sometimes it happens. If anyone else is
> interested, start watching the repo and we can open issues and so forth.
>
>
> On Thu, Jan 23, 2014 at 9:44 AM, sheila miguez <she...@pobox.com> wrote:
>>
>> I did not realize this! And to be honest, I feel like you all have more
>> pythonic instincts than I do because I have spent more of my programming
>> life speaking java -- that tends to warp the brain. :)
>>
>>
>>
>> On Thu, Jan 23, 2014 at 9:39 AM, Jeffrey Spies <je...@cos.io> wrote:
>>>
>>> Because Robert is currently a part-time intern at the Center (and
>>> learning Python style simultaneously), you'll likely find it most
>>> efficient to ask for commit privs for yourself for the time
>>> being--we're certainly behind your vision for this library!
>>>
>>> Jeff.
>>>
>>> On Thu, Jan 23, 2014 at 10:28 AM, sheila miguez <she...@pobox.com> wrote:
>>> > If y'all are uncomfortable with having commit privs for the main repo,
>>> > then
>>> > I can work off Robert's branch and make pull requests to it -- but
>>> > based on
>>> > conversations with pdurbin in #dvn he is happy to provide commit privs
>>> > to
>>> > all or one of you.
>>> >
>>> > My goal is to have something to show Victoria et al next week, which
>>> > may or
>>> > may not include some front end changes -- regardless, I think we/I can
>>> > make
>>> > some quick changes to make things a little more pythonic and that would
>>> > be
>>> > great. I see Robert is already doing that. It will reduce the amount of
>>> > refactoring I will want to do in the researchcompendia code that is
>>> > using
>>> > the dvn_client.
>>> >
>>> > I'm going to nudge to get things in to master periodically. If we don't
>>> > get
>>> > things in to master then we reduce the chances of other people
>>> > collaborating
>>> > on the project. It would be great to have some projects like these that
>>> > we
>>> > can run sprints for at pycon. I am planning to manage a sprint for
>>> > researchcompendia. My push goal is to approach other open science
>>> > related
>>> > projects to see if they would be willing to participate in sprints as
>>> > well.
>>> > The dataverse folks are very friendly! So I'm excited about that.
>>> >
>>> >
>>> > On Wed, Jan 22, 2014 at 5:58 PM, sheila miguez <she...@pobox.com>
>>> > wrote:
>>> >>
>>> >> I like the idea of pushing our improvements to the main repo and doing
>>> >> work off short-lived branches. Hop in #dvn, I think pdurbin will give
>>> >> COS
>>> >> folks commit privs.
>>> >>
>>> >>
>>> >> On Wed, Jan 22, 2014 at 3:57 PM, Joshua Carp
>>> >> <jo...@centerforopenscience.org> wrote:
>>> >>>
>>> >>> One of interns at the COS, Robert Liebowitz, has been leading work
>>> >>> here
>>> >>> on a Dataverse add-on for the OSF. He's been working on his own fork
>>> >>> of the
>>> >>> python client for the API, at
>>> >>> https://github.com/rliebz/dvn-client-python/tree/test. Sheila, we'll
>>> >>> likely
>>> >>> want to merge your work into Robert's fork, and you might want to
>>> >>> pull
>>> >>> Robert's repo as well. Personally, I don't know the python client or
>>> >>> the
>>> >>> Dataverse APIs well enough to manage the IQSS repo at the moment, so
>>> >>> I'm
>>> >>> happy to leave the forks to evolve in parallel, with merges between
>>> >>> them as
>>> >>> necessary. Sheila, Philip, Robert, and anyone else who's
>>> >>> interested--happy
>>> >>> to hear your thoughts on this.
>>> >>>
>>> >>> Josh
>>> >>>
>>> >>>
>>> >>> On Wed, Jan 22, 2014 at 12:56 PM, sheila miguez <she...@pobox.com>
>>> >>> wrote:
>>> >>>>
>>> >>>> For my project, researchcompendia.org we are also looking to do a
>>> >>>> dataverse integration. Tthere is a dvn-python-client project that
>>> >>>> works with
>>> >>>> the dvn api, and I see that OSF folks are using it.
>>> >>>>
>>> >>>> I've got a pull request that adds a little documentation and cleans
>>> >>>> up a
>>> >>>> little bit of the code to get some tests to pass, and after that is
>>> >>>> accepted, I'd like to get the repo in shape to be a python package.
>>> >>>> This
>>> >>>> will involve changing the directory structure around.
>>> >>>>
>>> >>>> Before I do that, I want to know if any of you are actively working
>>> >>>> on
>>> >>>> this so that I don't cause a merge hell if/when I make a commit that
>>> >>>> changes
>>> >>>> the directory structure.
>>> >>>>
>>> >>>> Basically I would like to follow guidelines laid out by python folks
>>> >>>> in
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> http://www.jeffknupp.com/blog/2013/08/16/open-sourcing-a-python-project-the-right-way/
>>> >>>>
>>> >>>> and in
>>> >>>>
>>> >>>> https://github.com/audreyr/cookiecutter-pypackage
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> sheila
>>> >>>>
>>> >>>> --
>>> >>>> You received this message because you are subscribed to the Google
>>> >>>> Groups "Open Science Framework" group.
>>> >>>> To unsubscribe from this group and stop receiving emails from it,
>>> >>>> send
>>> >>>> an email to openscienceframe...@googlegroups.com.
>>> >>>> For more options, visit https://groups.google.com/groups/opt_out.
>>> >>>
>>> >>>
>>> >>> --
>>> >>> You received this message because you are subscribed to the Google
>>> >>> Groups
>>> >>> "Open Science Framework" group.
>>> >>> To unsubscribe from this group and stop receiving emails from it,
>>> >>> send an
>>> >>> email to openscienceframe...@googlegroups.com.
>>> >>> For more options, visit https://groups.google.com/groups/opt_out.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> sheila
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > sheila
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "Open Science Framework" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> > an
>>> > email to openscienceframe...@googlegroups.com.
>>> > For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Open Science Framework" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to openscienceframe...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>>
>> --
>> sheila
>
>
>
>
> --
> sheila
>
> --
> You received this message because you are subscribed to the Google Groups
> "Open Science Framework" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openscienceframe...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.



--
Philip Durbin
Software Developer for http://thedata.org
http://www.iq.harvard.edu/people/philip-durbin
Reply all
Reply to author
Forward
0 new messages