manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rafa Haro <rh...@apache.org>
Subject Re: Gsoc 2016
Date Tue, 15 Mar 2016 12:46:09 GMT
Hi Antonio,

After subscribing to Apache's mentors email list, you need to receive the
acknowledge from at least one Apache ManifoldCF PMC member. So, you would
need to write an email similar to this one:

ManifoldCF PMC,

Please acknowledge my request to become a mentor for Google Summer of Code
2016 projects for Apache ManifoldCF

I would like to receive the mentor invite to adperezmorales@gmail.com
I am already signed up on the mentor list.

You can find more information on the process here:
https://community.apache.org/gsoc.html

About the Nuxeo connector as an idea, I would be really interested on this
too. My current company is partially based on Nuxeo, so that would be great
for me also from a personal point of view. Because of that, I could help by
co-mentoring the project. I don't have enough time for mentoring, but I
could act as backup mentor for Antonio

Cheers,
Rafa

On Tue, Mar 15, 2016 at 1:37 PM Antonio David Pérez Morales <
adperezmorales@gmail.com> wrote:

> Hi Karl
>
> Yes, let's wait to see if David would like to implement this new connector
> and in that case prepare and submit a proposal.
> Where do I have to sign up to be a mentor?
>
> For the list ok, I will subscribe after signing up as mentor.
>
> Thanks Karl
>
> Regards
>
> 2016-03-15 13:32 GMT+01:00 Karl Wright <daddywri@gmail.com>:
>
> > Hi Antonio,
> >
> > I think it is perfectly reasonable to build a Nuxeo connector for a GSoC
> > 2016 project.  You'll need to find out if David is interested, and sign
> up
> > to be a mentor, of course.  There's also a mentor list you need to join
> --
> > mentors@apache.org, I think.
> >
> > Thanks!
> > Karl
> >
> >
> > On Tue, Mar 15, 2016 at 8:21 AM, Antonio David Pérez Morales <
> > adperezmorales@gmail.com> wrote:
> >
> > > Hi
> > >
> > > The ideas proposed by Karl are very interesting and are needed to have
> a
> > > more stable version of ManifoldCF in terms of supported connectors.
> > >
> > > Regarding the idea of implement new connectors, I have been working
> > lately
> > > with Nuxeo [1] and I would like to propose it as a potential new
> > connector
> > > to be implemented during this GSoC period.
> > > The idea behind this new connector is to use the Nuxeo REST API [2] to
> > > implement a native connector for Nuxeo.
> > >
> > > Karl, in case you think this is an interesting connector to have, I can
> > > create a new Jira ticket for that and I volunteer to act as mentor of
> > this
> > > possible GSoC project.
> > >
> > > Regards
> > >
> > > [1] http://www.nuxeo.com
> > > [2] https://doc.nuxeo.com/display/NXDOC/REST+API
> > >
> > > 2016-03-15 12:27 GMT+01:00 Karl Wright <daddywri@gmail.com>:
> > >
> > > > Hi David,
> > > >
> > > > Thank you for considering ManifoldCF for your GSoC project.
> > > >
> > > > Most of our potential GSoC projects left over from 2015 involve
> > > connectors
> > > > for proprietary repositories, unfortunately.  These are:
> > > >
> > > > (1) Livelink connector (CONNECTORS-1117) -- need to reimplement using
> > the
> > > > newer REST API
> > > > (2) Finishing off the Alfresco Webscript connector (CONNECTORS-1058)
> --
> > > > need to add the ability to support thread interruptibility
> > > >
> > > > Other projects that have been discussed include working with
> > SharePoint;
> > > > SharePoint has deprecated their web-services API and has instead gone
> > to
> > > a
> > > > REST API, and we'd need a pair of connectors (authority and
> repository)
> > > to
> > > > support that.  That's not properly ticketed in Jira for GSoC yet, and
> > it
> > > > may be too big for one GSoC project, but we can perhaps break it up
> > into
> > > > smaller pieces.
> > > >
> > > > So, if you can show you have access to one of these three proprietary
> > > > repositories for the purposes of development, you could write a
> > proposal
> > > > along those lines.
> > > >
> > > > Alternatively, if you know of any repository that we may not
> currently
> > > have
> > > > a connector for that could prove useful to someone, you could propose
> > > that
> > > > as a project.
> > > >
> > > > We're currently pretty shorthanded when it comes to mentors, so we
> will
> > > > only be able to accept one or two proposals at most this year.
> > > >
> > > > Thanks!
> > > > Karl
> > > >
> > > >
> > > > On Tue, Mar 15, 2016 at 6:44 AM, David Arroyo <
> > > > arroyoescobardavid@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I am David Arroyo, undergraduate Software Engineer at University
of
> > > > > Seville, Spain and I am graduate in a Superior Grade Formative
> Course
> > > on
> > > > > multi-platform application development.
> > > > >
> > > > > During last months, I have been following the mailing list and also
> > > > > reviewing some open issues (some of them tagged as gsoc gsoc2015).
> I
> > > > would
> > > > > be interested to collaborate in this project to get some experience
> > > and I
> > > > > think GSoC could be an interesting opportunity to learn about open
> > > source
> > > > > community development, unkown for me so far, and learning a bit
> more
> > > > about
> > > > > the technologies used in this project.
> > > > >
> > > > > My intention is continue collaborating with the project after GSoC
> > > (both
> > > > if
> > > > > I'm accepted or not) because in summer I have a lot of free time
> and
> > I
> > > > can
> > > > > work fixing issues or developing new functionalities.
> > > > >
> > > > > I am very interested in Manifold and I would like to get
> information
> > > > about
> > > > > some connectors that could be needed to be implemented.
> > > > >
> > > > > I really hope participate in Google Summer of Code 2016 and
> continue
> > to
> > > > > expand my current technical knowledge.
> > > > >
> > > > > Yours faithfully,
> > > > > David Arroyo
> > > > >
> > > > > --
> > > > > David Arroyo Escobar
> > > > >
> > > >
> > >
> >
>

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