Hi Guys,
It’s so great to have supportive mentors like you guys! BTW my actual first name is “Parth" and last name is “Sane” just to clarify from the previous email. I am going to prepare the proposal on the fingerprinting engine but I don’t have a clear idea about what to write with respect to the topic although I have some elements already in place for the proposal(Oleg can maybe provide an idea on this regard).
Regards,
Parth Sane
> On 04-Mar-2016, at 2:28 AM, Baptiste Mathus <
bma...@batmat.net> wrote:
>
> Welcome from me too, Parth! (btw, I'm not it's your first name, IIRC in some parts of the world name comes first in presentations, just let us know if so).
>
> +1 with Oleg about the mails to dev ML: to help you understand how we work: actually, the Jenkins community has a *very* open governance model. That is, almost absolutely everything happens (discussions I mean) in public, mostly either on the developer ML, or on IRC (or in GitHub PR btw).
>
> By that I mean: you can, and maybe should, take things public by default when it comes for example to deciding the direction some feature might take. Even if you'll have mentors, they're more dedicated to help you going forward and play an entrypoint to the community, than choosing what should be implemented by alone.
>
> I hope it clarifies things a bit, and not the contrary :). Don't hesitate to ask for precisions about how the community works in case you have questions obviously.
>
> Friendly, welcome on board again!
>
> -- Baptiste
> PS : one of the GSoC Jenkins org admin and Jenkins contributor, just in case you wonder why I'm writing here :).
>
>
>
> 2016-03-03 18:58 GMT+01:00 Oleg Nenashev <
o.v.ne...@gmail.com>:
> Hi Parth,
>
> Yes, it's an interesting topic. My presentation mentions several obstacles, but they should be doable. The only requirement from Jenkins standpoint is to make the Fingerprint storage engine pluggable in order to support the current filesystem approach and other databases in the future.
>
> If you want to focus on this project, my recommendation would be to proceed with a new e-mail to the Jenkins Developers mailing list. You have a good self-introduction here, so you could just repeat it and provide your thoughts on the interesting project.
>
> Best regards,
> Oleg
>
> 2016-03-03 20:38 GMT+03:00 Parth Sane <
laerdev...@gmail.com>:
> Hi,
> So to reiterate on the previous email I think it would be a great idea to improve the fingerprinting system by storing all those prints into a RDBMS like PostgresSQL. Maybe that is something I could build a proposal on. What do you say Oleg?
> Regards,
> Parth Sane
> > On 03-Mar-2016, at 7:35 PM, Oleg Nenashev <
o.v.ne...@gmail.com> wrote:
> >
> > Hi,
> >
> > Let's discuss it at GSoC office hours.
> > We hope to schedule them soon.
> >
> > In general, I keep major 3 directions in mind:
> > • UI improvements
> > • Architecture rework for better extensibility
> > • Backend data storage rework (e.g. support of databases)
> > Best regards,
> > Oleg Nenashev
> >
> > среда, 2 марта 2016 г., 16:15:26 UTC+3 пользователь Parth Sane написал:
> > Hi,
> > I’m interested in fingerprinting of build artefacts. What exactly do we need to do with fingerprinting? Better storage? Better tracking? Its a bit ambiguous for me what part of fingerprinting needs improvement.
> > Please do let me know.
> > Regards,
> > Parth Sane
> > > On 02-Mar-2016, at 4:51 PM, Oleg Nenashev <
o.v.ne...@gmail.com> wrote:
> > >
> > > Hello,
> > >
> > > // Please keep
jenkinsci...@googlegroups.com in Cc.
> > >
> > > Fingerprint Engine story is pretty complex if you want to handle it alone. In general, I hope there will be 2-3 students, so we will be able to share the load. On the other hand, there is no strict requirement to do all the stuff mentioned in this presentation. It is possible to select particular topics interesting to you.
> > >
> > > The current storage engine is not documented very well from the user point of view. It's possible to get some information from Javadoc. Since there is an interest in the topic, I'll prepare the overview presentation on this weekend.
> > >
> > > Currently you can try the following Fingerprint use-cases:
> > > • Fingerprinting of build artifacts:
> > > •
https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint
> > > •
http://thingsyoudidntknowaboutjenkins.tumblr.com/post/24737092433/fingerprinting
> > > • Configuration management:
> > > •
https://wiki.jenkins-ci.org/display/JENKINS/Puppet+Plugin
> > > •
https://wiki.jenkins-ci.org/display/JENKINS/Deployment+Notification+Plugin
> > > • Docker Traceability:
> > > •
https://github.com/jenkinsci/docker-traceability-plugin/blob/master/README.md
> > >
> > > 2016-03-02 13:49 GMT+03:00 Parth Sane <
laerdev...@gmail.com>:
> > > Hi Oleg,
> > > It’s nice to hear from you again. I’m really interested in New generation of Fingerprinting engine for Jenkins. It’s something that I would like to work on. My Java background should help me in this project. This was further confirmed when I saw your slides at
speakerdeck.com. Maybe we can discuss this at a further length?
> > > Regards,
> > > Parth Sane
> > >
> > >> On 02-Mar-2016, at 4:03 PM, Oleg Nenashev <
o.v.ne...@gmail.com> wrote:
> > >>
> > >> Hello,
> > >>
> > >> Thanks for the input! We are looking forward to see your application.
> > >> If you are interested in a particular project idea from our Wiki, it's possible to start discussing it even before the official application.
> > >> Please let us know about the projects you would like to take, an we will add potential mentors to the discussion loop.
> > >>
> > >> Best regards,
> > >> Oleg Nenashev
> > >>
> > >> 2016-03-02 9:48 GMT+03:00 Parth Sane <
laerdev...@gmail.com>:
> > >> Hi,
> > >> I’m currently a 3rd year Computer Engineering student at the University of Mumbai, India. I’m interested in cloud computing, mobile development on platforms like Android and iOS. I usually participate in open source projects not just because I like using that software but also because its really cool code. Now Jenkins in particular piques my interest. It’s the only CI server that runs well cross platform and with the plugins of your choice. With the code base being Java, it makes me more comfortable working with it (if I were to submit a patch) since I have worked on Java technologies involving API design, RDBMS and production code during my internship at BMC Software Inc. I also have been learning Java since 2010 so I do have a fair bit of programming experience under my belt. I have also worked UX design on my personal projects with Bootstrap. I have also submitted a patch for the Linux kernel as well.
> > >> My online profiles are as follows:
> > >> • GitHub: @Boggartfly
> > >> • Twitter: @Parthadvance
> > >> • LinkedIn: Parth Sane
> > >> I thought I should write this email to answer the why me question that would arise when I will submit my application proposal once the GSoC 2016 Student application deadline opens later this month.
> > >> Regards,
> > >> Parth Sane
> > >>
> > >> --
> > >> You received this message because you are subscribed to the Google Groups "Jenkins Google Summer of Code Organization Admins" group.
> > >> To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-gsoc-...@googlegroups.com.
> > >> To post to this group, send email to
jenkinsci...@googlegroups.com.
> > >> To view this discussion on the web, visit
https://groups.google.com/d/msgid/jenkinsci-gsoc-orgs/8597BAE4-8ABC-42D7-AF8A-D6D672081F2F%40gmail.com.
> > >> For more options, visit
https://groups.google.com/d/optout.
> > >>
> > >
> > >
> >
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Google Summer of Code Organization Admins" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-gsoc-...@googlegroups.com.
> To post to this group, send email to
jenkinsci...@googlegroups.com.
> To view this discussion on the web, visit
https://groups.google.com/d/msgid/jenkinsci-gsoc-orgs/CAPfivLCeV2UyQ6BQ0JFpqnwzUgqkRGNAtYydXpu_GKWTeieAig%40mail.gmail.com.
>
> For more options, visit
https://groups.google.com/d/optout.
>