Re: [GSoC 2016] - Status update

Hi everyone, The last GSoC 2016 event is the mentor summit on Oct 28-29-30. At the summit I will be presenting a lightning talk on the External Workspace Manager Plugin. The idea of the lightning talk is to emphasize on student achievement, not on pitching. The time limit is 180 seconds, and 6

[GSOC 2016]- AUTOMATIC DOCUMENT PUBLISHER

Hey , I have been working on a script that can walk through a directory full of repositories , pick out plugin repositories and extract the title of the plugin and the documentation . The code can be found on https://github.com/anyangocynthia/gsoc-automatic-publisher/tree/code-review I

Re: Automatic Plugin Documentation [GSOC 2016]

I have updated my template with the code that pulls the files from github . Some of the assumptions that I have made : 1. All plugin repositories have the keyword "plugin" 2. The plugins are affiliated with github.com/jenkinsci

Re: [GSOC 2016] Support core plugin improvements

Yes it should be possible. No problem On Mon, Jun 6, 2016 at 4:26 PM, Alexandru Somai wrote: > Hello Arnaud, > > Maybe you can do a quick JIRA KT at the next public office hours? As Oleg > mentioned, it would make more sense if all the students are online, because >

Re: [GSOC 2016] Support core plugin improvements

Hello Arnaud, Maybe you can do a quick JIRA KT at the next public office hours? As Oleg mentioned, it would make more sense if all the students are online, because we'll use Jira in one way or another. Regards, Alex On Mon, Jun 6, 2016 at 4:53 PM Arnaud Héritier wrote: >

Re: [GSOC 2016] Support core plugin improvements

Thanks a lot arnaud. Seems like it's working. I didn't know those scripts should be copied into webapp directory. I'll come back soon with the progress.. On Mon, Jun 6, 2016 at 7:28 PM, Arnaud Héritier wrote: > I think that strategy 1/ should work (and is used by several

Re: [GSOC 2016] Support core plugin improvements

I think that strategy 1/ should work (and is used by several plugins) But you need to copy the lib for exemple under *src/main/webapp/js/jstree.min.js* Then import it with ** I'm clearly not a front-end guy and I know that many people are working on this nowadays to better integrate javasccript

Re: [GSOC 2016] Support core plugin improvements

I did it this morning with Minudika but I can do another one this week if needed Thanks a lot for the review. For now I didn't do it On Mon, Jun 6, 2016 at 3:05 PM, Oleg Nenashev wrote: > Hi Arnaud, > > CCed Alex, who may be also interested in JIRA handling KT. > Maybe

Re: [GSOC 2016] Support core plugin improvements

Hi all, I am currently working on the implementation of JENKINS-33090 . For that I have to implement a file browsing tree which will apear on the frontend of support core plugin. I have found this jQuery

Re: [GSOC 2016] Support core plugin improvements

Hi Arnaud, CCed Alex, who may be also interested in JIRA handling KT. Maybe makes sense to perform a KT with all students if you do not mind. Also reviewed the PR. Needs some polishing IMHO BR, Oleg 2016-06-05 23:26 GMT+02:00 Arnaud Héritier : > Hi Minudika, > > Ping me

Re: [GSOC 2016] Support core plugin improvements

Hi Minudika, Ping me on monday and we'll take 15 or 30 minutes to play with Jira. Cheers On Sun, Jun 5, 2016 at 2:46 PM, Minudika Malshan wrote: > Hi, > > @Steve : Could you please do a quick demo on how to use jQuery-plugin with > support core plugin, during the

Re: [GSOC 2016] Support core plugin improvements

Hi, @Steve : Could you please do a quick demo on how to use jQuery-plugin with support core plugin, during the hangout on next Tuesday? @Arnaud : I will try to add some subtasks. But it would be nice if you could show the correct way of dealing with Jirra. Especially within the agile scope.

Re: [GSOC 2016] Support core plugin improvements

Hi Yes I was thinking about it too. You can create more technical tasks (type : task) and you add them in the current sprint from the backlog view (If you need we can do a tour of Jira to see all the features and especially ones around agile features). I was thinking about a task to implement

Re: [GSOC 2016] Support core plugin improvements

I was refereeing to *Bundle Management UI Sprint* on Jirra [1] [1] https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=156=JENKINS=detail=JENKINS-35341 On Sat, Jun 4, 2016 at 12:09 AM, Minudika Malshan wrote: > Hi Arnaud, > > Shall we add implementing UI

Re: [GSOC 2016] Support core plugin improvements

Hi Arnaud, Shall we add implementing UI components for main task as a subtask? In that way, it will be easy to track the progress I think. Otherwise I will have to comment "I have implemented the backed and have to implement the UI components" :D What do you think? On Mon, May 30, 2016 at 7:11

Re: Automatic Plugin Documentation [GSOC 2016]

(replies inline) On Wed, 01 Jun 2016, Oleg Nenashev wrote: > Yes, raw HTMLs :( > > Do you have regular team meetings in this project. > I have a bunch of questions regarding the plugin documentation format (the > document is not detailed enough), and maybe a short chat is better than a > long

Re: Automatic Plugin Documentation [GSOC 2016]

I can set one up On Wed, Jun 1, 2016 at 8:20 PM, Oleg Nenashev wrote: > Yes, raw HTMLs :( > > Do you have regular team meetings in this project. > I have a bunch of questions regarding the plugin documentation format (the > document is not detailed enough), and maybe a

Re: Automatic Plugin Documentation [GSOC 2016]

Yes, raw HTMLs :( Do you have regular team meetings in this project. I have a bunch of questions regarding the plugin documentation format (the document is not detailed enough), and maybe a short chat is better than a long review-change-review cycle. BR, Oleg 2016-05-31 17:28 GMT+02:00 Baptiste

Re: Automatic Plugin Documentation [GSOC 2016]

Hi, Sorry should already have reviewed the gdoc. Will do this evening. In general, please don't hesitate to ping me e.g. on irc as a reminder to some thread or things you're expecting an answer from Tyler or me. See below for the current email. Le 31 mai 2016 12:30 PM, "Cynthia Anyango"

Re: Automatic Plugin Documentation [GSOC 2016]

@Oleg , - How would you suggest I handle the exploit injection issues plus what is RAM HTML ? :) I feel i would need some help with that @Tyler and @Baptise - How to write multi-page documents I have found pandoc.org which renders multiple files into a single file . for example

Re: [GSOC 2016] Support core plugin improvements

Hi, Sorry I was replying to Steve's mail. He said that we could arrange a meeting on Tuesday. @Steve : If it's possible please let me know the time. anytime would be fine for me. Thanks and regards On Mon, May 30, 2016 at 7:05 PM, Oleg Nenashev wrote: > Hi, > >

Re: [GSOC 2016] Support core plugin improvements

Hi, Lifehack: if you detalize your question in the mailing list, you may get a response from somebody even if your mentors are on holidays (please be sure they deserve them). BR, Oleg 2016-05-30 16:29 GMT+03:00 Minudika Malshan : > Hi, > Shall we arrange a time slot? >

Re: [GSOC 2016] Support core plugin improvements

Hi, Shall we arrange a time slot? On Sun, May 29, 2016 at 5:43 PM, Minudika Malshan wrote: > Thanks a lot :) > > On Sun, May 29, 2016 at 5:32 PM, Steve Christou > wrote: > >> I am not available the next 2 days (us holiday). On Tuesday we can setup

Re: [GSOC 2016] Support core plugin improvements

Thanks a lot :) On Sun, May 29, 2016 at 5:32 PM, Steve Christou wrote: > I am not available the next 2 days (us holiday). On Tuesday we can setup a > hangout. > > On Sat, May 28, 2016 at 5:52 PM Minudika Malshan > wrote: > >> Hello Arnaud, Steve,

Re: [GSOC 2016] Support core plugin improvements

I am not available the next 2 days (us holiday). On Tuesday we can setup a hangout. On Sat, May 28, 2016 at 5:52 PM Minudika Malshan wrote: > Hello Arnaud, Steve, > > Can we have a hangout? I need to clarify few things about using JavaScript > and Jelly. > I tried few

Re: [GSOC 2016] Support core plugin improvements

Hello Arnaud, Steve, Can we have a hangout? I need to clarify few things about using JavaScript and Jelly. I tried few methods to implement the front end part for the bundle browsing feature. It would be great if you could help me to find the best way for the implementation. Please let me know a

Re: Automatic Plugin Documentation [GSOC 2016]

Hi Cynthia, Thanks for sharing the document! I've added several comments. It definitely requires much more details. My main questions would be: - How to handle the embedded content? - How to secure Jenkins website from exploit injection into ASCIIDOC? (e.g. via RAM HTML) - How to

Re: Automatic Plugin Documentation [GSOC 2016]

Hello everyone , I have put up together a document containing some of the things that will go into various doc files . Please feel free to comment and put up as many suggestions as you can . https://docs.google.com/document/d/1EHX0DJ8alsctFN6POLCehowusuikmnUMeL_5jPHVURA/edit?usp=sharing

Re: Automatic Plugin Documentation [GSOC 2016]

@Baptise I have gone through more than 20 plugin repos(am still going through more) trying to come up with a standard template , I will share the google soon On Tue, May 24, 2016 at 11:00 PM, Baptiste Mathus wrote: > Hi Cynthia, > > Not sure Oleg was referring to a specific

Re: Automatic Plugin Documentation [GSOC 2016]

Hi Cynthia, Not sure Oleg was referring to a specific plugin, more he's willing to convert his plugin docs to asciidoc IIUC. If you already know markdown, then you can consider Asciidoc being quite the same, but being more /standard/ and with more features. If you want examples of actual

Re: Automatic Plugin Documentation [GSOC 2016]

Hey Oleg , Could you please refer me to a plugin that has its documentation in Asciidoc On Sunday, May 15, 2016 at 5:38:35 PM UTC+3, Oleg Nenashev wrote: > > In Jenkins.io we support both Markdown and Asciidoc. > Asciidoc is recommended, because we use it's macros features for > particular

Re: [GSOC 2016] Support core plugin improvements

Hi Minudika, I think you want to have a look at https://github.com/jenkinsci/js-libs and more specically at https://github.com/jenkinsci/js-libs/tree/master/jquery-detached Also, you most probably wanna watch: https://www.youtube.com/watch?v=15947ISwA2w Cheers 2016-05-21 20:34 GMT+02:00

Re: [GSOC 2016] Support core plugin improvements

Hi all, I tried to use some jQuery libraries with Jelly. What I did was, I put the JavaScript files to the folder * "/support-core-plugin/src/main/resources/com/cloudbees/jenkins/support/SupportAction"* and tried to reffer to them from the *"supportAction/index.jelly"* script as follows. **

Re: Automatic Plugin Documentation [GSOC 2016]

If we try so summarize: - Keep It Simple (so that there's a very high chance the APD project does not end being ignored by most developers because it's too much hassle to use) - Not having to release, say, a 1.3.x to fix some typo or whatever in a 1.3 version" (probably a

Re: Automatic Plugin Documentation [GSOC 2016]

I certainly agree that pulling docs from master is the wrong approach. Just like pull the code from master and just building a plugin would be wrong. On Fri, May 20, 2016 at 3:07 AM, Cynthia Anyango wrote: > But I do not want to confuse users with documentation that

Re: Automatic Plugin Documentation [GSOC 2016]

If you simply mark new features with the version number they were/will be introduced in, then users will not be confused by the appearance of a feature in documentation that they do not see in the product. In fact arguably this mode is better for users because they can see what features are

Re: Automatic Plugin Documentation [GSOC 2016]

> > But I do not want to confuse users with documentation that does not match > a released plugin. Pulling the docs from master would be a no-go for me. > The master branch may contain work in progress and I do not want to cut a > release just to keep the docs consistent or up-to-date. Pulling

Re: Automatic Plugin Documentation [GSOC 2016]

On Tue, May 17, 2016 at 3:26 PM, Robert Sandell wrote: > I don't think we should have to rely on having to make a release just to > get a fix into the documentation. > The doc generation should be just picked from the master branch during the > static generation of

Re: Automatic Plugin Documentation [GSOC 2016]

> > But I don't want to have to release a new version of my plugin just > because I updated the tutorial or tips & tricks sections. > The new feature bug is present in today's wiki usage as well. > So there could be a manual documentation publishing trigger. Then owners will be able to get the

Re: Automatic Plugin Documentation [GSOC 2016]

But I don't want to have to release a new version of my plugin just because I updated the tutorial or tips & tricks sections. The new feature bug is present in today's wiki usage as well. /B On Tue, May 17, 2016 at 5:57 PM, Cynthia Anyango wrote: > I agree with

Re: Automatic Plugin Documentation [GSOC 2016]

> > I don't think we should have to rely on having to make a release just to > get a fix into the documentation. > The doc generation should be just picked from the master branch during the > static generation of jenkins.io unless that would take too much time. > That way a pull request with a new

Re: Automatic Plugin Documentation [GSOC 2016]

I don't think we should have to rely on having to make a release just to get a fix into the documentation. The doc generation should be just picked from the master branch during the static generation of jenkins.io unless that would take too much time. That way a pull request with a new feature in

Re: Automatic Plugin Documentation [GSOC 2016]

Hey Manfred , Thanks for your feedback , We are going to prototype both asciidoc and markdown the results of the will be hosted on jenkins.io which supports both . I will prepare a plugin subsection in the Documentation section https://jenkins.io/doc/ this is where all the plugin docs will

Re: Automatic Plugin Documentation [GSOC 2016]

In terms of asciidoc (and doc in general) usage for plugins I can see a number of ways for this to work. 1. Just write the docs and rely on the rendering in github. Similar to a readme being rendered just fine github renders any asciidoc or markdown files. E.g. see

Re: Automatic Plugin Documentation [GSOC 2016]

In Jenkins.io we support both Markdown and Asciidoc. Asciidoc is recommended, because we use it's macros features for particular cases. If you need any reference plugin with documentation in Asciidoc, please let me know. I consider moving docs for several plugins to GitHub, so I can migrate one

Re: [GSOC 2016] Support core plugin improvements

Thanks a lot Arnaud and Steve.. That hangout was really helpful for me :) On Sat, May 14, 2016 at 1:33 AM, Minudika Malshan wrote: > Thanks a lot both of you!! > On May 13, 2016 11:47 AM, "Arnaud Héritier" wrote: > >> Let's do this. I am sadly too

Re: [GSOC 2016] Support core plugin improvements

Thanks a lot both of you!! On May 13, 2016 11:47 AM, "Arnaud Héritier" wrote: > Let's do this. I am sadly too often up at this hour ... (kids ...) > > On Fri, May 13, 2016 at 6:56 AM, Minudika Malshan > wrote: > >> +1 from me.. >> On May 13, 2016 6:13

Re: [GSOC 2016] Support core plugin improvements

Let's do this. I am sadly too often up at this hour ... (kids ...) On Fri, May 13, 2016 at 6:56 AM, Minudika Malshan wrote: > +1 from me.. > On May 13, 2016 6:13 AM, "Steve Christou" wrote: > >> @Arnaud @Minudika if you want we can do 8AM On Sunday

Re: [GSOC 2016] Support core plugin improvements

+1 from me.. On May 13, 2016 6:13 AM, "Steve Christou" wrote: > @Arnaud @Minudika if you want we can do 8AM On Sunday for you which is > 11:30 AM (GMT +5:30) and 2 AM for me. > > On Wed, May 11, 2016 at 5:43 PM Arnaud Héritier > wrote: > >> I will try

Re: [GSOC 2016] Support core plugin improvements

@Arnaud @Minudika if you want we can do 8AM On Sunday for you which is 11:30 AM (GMT +5:30) and 2 AM for me. On Wed, May 11, 2016 at 5:43 PM Arnaud Héritier wrote: > I will try to be available but it is often less easy for me the WE with my > kids > If it's not between

Re: [GSOC 2016] Support core plugin improvements

I will try to be available but it is often less easy for me the WE with my kids If it's not between midnight and 9AM my time I could try to join On Wed, May 11, 2016 at 10:18 PM, Minudika Malshan wrote: > Thanks a lot Steve. I am OK with anytime on Saturday and Sunday. >

Re: [GSOC 2016] Support core plugin improvements

Thanks a lot Steve. I am OK with anytime on Saturday and Sunday. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [GSOC 2016] Support core plugin improvements

a Malshan < >>>>>>>>>>>>>>>>>>>>>>>> minudika...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>

Re: [GSOC 2016] Support core plugin improvements

gt;>>>>>>>>>>>>>>>>> hangout? >>>>>>>>>>>>>>>>>>>>>>>> Thanks a lot for your help. >>>>>>>>>>>>>>>>>>>>>>>>

Re: [GSOC 2016] Support core plugin improvements

>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Hi Minudika, >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>&

Re: Automatic Plugin Documentation [GSOC 2016]

I am all for asciidoc first, its the better format after all ;-) On Mon, May 9, 2016 at 1:53 PM, Baptiste Mathus wrote: > +1 Manfred. > IMO, this could even be asciidoc first, and possibly some Markdown flavour > (prolly GH's) secondly. > > > 2016-05-09 21:24 GMT+02:00 Manfred

Re: Automatic Plugin Documentation [GSOC 2016]

+1 Manfred. IMO, this could even be asciidoc first, and possibly some Markdown flavour (prolly GH's) secondly. 2016-05-09 21:24 GMT+02:00 Manfred Moser : > I sure hope this will work with asciidoc as well as markdown files ;-) > > On Mon, May 9, 2016 at 10:54 AM, Cynthia

Re: Automatic Plugin Documentation [GSOC 2016]

I sure hope this will work with asciidoc as well as markdown files ;-) On Mon, May 9, 2016 at 10:54 AM, Cynthia Anyango wrote: > > Hey Martinda , > > Thanks for your feedback . > > All that you have mentioned is within the scope of my project . > > As @Daniel

Re: Automatic Plugin Documentation [GSOC 2016]

Hey Martinda , Thanks for your feedback . All that you have mentioned is within the scope of my project . As @Daniel mentioned I will be introducing various named-by-convention files that will define all that should be contained in a plugin documentation . All the plugin documentation will

Re: Automatic Plugin Documentation [GSOC 2016]

> On 07.05.2016, at 01:00, martinda wrote: > > As a plugin user, and as a very occasional contributor, what would help me > document plugins better and faster would be to know where the documentation I > put in the code ends up on the web, and where to put the

Re: Automatic Plugin Documentation [GSOC 2016]

Hello Cynthia, As a plugin user, and as a very occasional contributor, what would help me document plugins better and faster would be to know where the documentation I put in the code ends up on the web, and where to put the documentation in the code (the help*.html files). I don't know if

Re: [GSoC 2016][support-core plugin] Community Bonding

Hi, Thank you Arnaud for introducing me to the community. First I would like to thank Steve and Arnaud for the massive support they've given me so far throughout this project. It's an honor and a pleasure to work with the amazing Jenkins community. I will do my best on this project and I'm

[GSoC 2016][support-core plugin] Community Bonding

Hi jenkins dev, Minudika's proposal to improve our support-core plugin was accepted by Google (You may have seen this in another thread). I would like to thanks Minudika for joining us and for the interest he has for this subject. Steven and myself will be mentoring this project but from my

Automatic Plugin Documentation [GSOC 2016]

Hey everyone . My proposal for the GSOC project : *Automatic Plugin Documentation was accepted*! Thanks to everyone who helped me out . The help really came a long way to getting the project accepted . During summer , I will be working on grabbing plugin documentation from the github

Re: [GSOC 2016] Support core plugin improvements

nt >>>>>>>>>>>> the UIs for support core plugin? >>>>>>>>>>>> I have to implement some features such as a file explorer. But >>>>>>>>>>>> with only using jelly, I couldn't find a way to do it. >>>>>>>

Re: [GSOC 2016] Support core plugin improvements

gt;>>>>>>> >>>>>>>>>>> Best regards >>>>>>>>>>> Minudika >>>>>>>>>>> >>>>>>>>>>> On Sat, Apr 30, 2016 at 10:25 PM, Minudika Malshan < >>>>>>>>>&g

Re: [GSOC 2016] Support core plugin improvements

>>>>>>>>>> >>>>>>>>>>> Currently I am following Apache Jelly. Could anyone let me know >>>>>>>>>>> how to use AJAX calls with jelly forms please? >>>>>>>>>>> Searched

Re: [GSOC 2016] Support core plugin improvements

>>>>>>>> Minudika >>>>>>>>>> >>>>>>>>>> On Wed, Apr 27, 2016 at 10:17 PM, Minudika Malshan < >>>>>>>>>> minudika...@gmail.com> wrote: >>>>>>>>>> >>>>>&g

Re: [GSOC 2016] Support core plugin improvements

;>>>>>> >>>>>>>>>> @Steve : Sure I am ok with that time. Thanks a lot for your help. >>>>>>>>>> >>>>>>>>>> @Arnaud : I have gone through some of those links. I will go >>>>

Re: [GSOC 2016] Support core plugin improvements

nd I have subscribed only to the mailing lists Jenkins >>>>>>>>> developers and Jenkins Users. Should I subscribe to the other mailing >>>>>>>>> lists >>>>>>>>> also? >>>>>>>>> >>>>>>>>> T

Re: [GSOC 2016] Support core plugin improvements

;>> >>>>>>>> Are you available tomorrow (about an hour) for a screen share so I >>>>>>>> can talk a little bit about Jenkins and the jelly files? I should be >>>>>>>> available after 9 AM EST (I have a 2-3 PM EST meeting). >>

Re: [GSOC 2016] Support core plugin improvements

t;> minudika...@gmail.com> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> At the beginning I was getting familiar with the source code. Now I >>>>>>> am following Jelly since I have to use it for th

Re: [GSOC 2016] Support core plugin improvements

rce code. Now I >>>>>> am following Jelly since I have to use it for the UI implementation. >>>>>> Please let me know further instructions. >>>>>> >>>>>> Thanks and regards. >>>>>> >>>>>> On Tue, Apr 2

Re: [GSOC 2016] Support core plugin improvements

know further instructions. >>>>> >>>>> Thanks and regards. >>>>> >>>>> On Tue, Apr 26, 2016 at 4:07 PM, Minudika Malshan < >>>>> minudika...@gmail.com> wrote: >>>>> >>>>>> Hi, >>>&

Re: [GSOC 2016] Support core plugin improvements

t;> >>>>> It will be a great pleasure to work with you. Looking forward for it :) >>>>> >>>>> Best regards >>>>> >>>>> On Sun, Apr 24, 2016 at 1:58 AM, Arnaud Héritier <aherit...@gmail.com> >>>>>

Re: [GSOC 2016] Support core plugin improvements

Arnaud Héritier <aherit...@gmail.com> >>>> wrote: >>>> >>>>> The pleasure is for us Minudika >>>>> We will come back to you soon. >>>>> >>>>> cheers >>>>> >>>>> On Sat, Apr 23, 2016 at

Re: [GSOC 2016] Support core plugin improvements

gt; wrote: >> >>> The pleasure is for us Minudika >>> We will come back to you soon. >>> >>> cheers >>> >>> On Sat, Apr 23, 2016 at 4:03 PM, Minudika Malshan <minudika...@gmail.com >>> > wrote: >>> >>>&

Re: [GSOC 2016] Support core plugin improvements

n, Apr 24, 2016 at 1:58 AM, Arnaud Héritier <aherit...@gmail.com> >>> wrote: >>> >>>> The pleasure is for us Minudika >>>> We will come back to you soon. >>>> >>>> cheers >>>> >>>> On Sat, Apr 23, 2016

Re: [GSOC 2016] Support core plugin improvements

will come back to you soon. >>> >>> cheers >>> >>> On Sat, Apr 23, 2016 at 4:03 PM, Minudika Malshan <minudika...@gmail.com >>> > wrote: >>> >>>> Hi all, >>>> My proposal for the project support core plugin improveme

Re: [GSOC 2016] Support core plugin improvements

>> >> cheers >> >> On Sat, Apr 23, 2016 at 4:03 PM, Minudika Malshan <minudika...@gmail.com> >> wrote: >> >>> Hi all, >>> My proposal for the project support core plugin improvements has been >>> accepted in gsoc 2016. So first of

Re: [GSOC 2016] Support core plugin improvements

016 at 4:03 PM, Minudika Malshan <minudika...@gmail.com> > wrote: > >> Hi all, >> My proposal for the project support core plugin improvements has been >> accepted in gsoc 2016. So first of all I'd like to thank each and everyone >> of you for the valuable support

Re: [GSoC 2016] - On the acceptance results (Jenkins project)

None of your answers can make me feel content at this moment but I want to continue work on Jenkins UI. On Saturday, April 23, 2016 at 5:20:42 AM UTC+5:30, Arshad Khan wrote: > > Hello, > > I want to ask some questions regarding the major concerns that you listed > in the email about my gsoc

Re: [GSOC 2016] Support core plugin improvements

The pleasure is for us Minudika We will come back to you soon. cheers On Sat, Apr 23, 2016 at 4:03 PM, Minudika Malshan <minudika...@gmail.com> wrote: > Hi all, > My proposal for the project support core plugin improvements has been > accepted in gsoc 2016. So first of all I'

Re: [GSOC 2016] Support core plugin improvements

Hi all, My proposal for the project support core plugin improvements has been accepted in gsoc 2016. So first of all I'd like to thank each and everyone of you for the valuable support you gave me. So far I have got familiar with the plugin and its source code. Please let me know the procedure I

Re: [GSoC 2016] - On the acceptance results (Jenkins project)

Arshad, As you say, this is your first experience. Oleg explained that we actually had to process dozens of applications. So, in the end, that's also life. Your proposal was definitely correct, but as we also had only a few slots allocated by Google (independently of us), we had to make some

GSOC 2016

Hi all, My proposal for the project support core plugin improvements has been accepted in gsoc 2016. So first of all I'd like to thank each and everyone of you for the valuable support you gave me. So far I was getting familiar with the source code. Please let me know the procedure I have

Re: [GSoC 2016] - On the acceptance results (Jenkins project)

Dear Arshad, I understand your concerns. This is a result of voting by mentors, so I do not feel eligible to answer all comments on my own. Especially in the case when I do not completely agree with the aggregated feedback. I'll forward the concerns to mentors and let them discuss. Please note

Re: [GSoC 2016] - On the acceptance results (Jenkins project)

On Saturday, April 23, 2016 at 5:20:42 AM UTC+5:30, Arshad Khan wrote: > > Hello, > > I want to ask some questions regarding the major concerns that you listed > in the email about my gsoc proposal. > > > lack of the new features (mostly redesign/styling focus) >> > > I had two major points

[GSoC 2016] - On the acceptance results (Jenkins project)

Hello, I want to ask some questions regarding the major concerns that you listed in the email about my gsoc proposal. lack of the new features (mostly redesign/styling focus) > I had two major points in my mind i.e., usability and consistency. I did not wanted to make unwanted changes to

Re: [GSoC 2016] - Status update

rks/>. Student application results will be known on April 22nd. Best regards, Oleg 2016-03-31 8:42 GMT+02:00 Parth Sane <laerdevstud...@gmail.com>: > Hi Oleg, > I was wondering when we(students) will know about our application results > for GSoC 2016. I'm really looking forward to par

Re: [GSoC 2016] - Status update

Hi Oleg, I was wondering when we(students) will know about our application results for GSoC 2016. I'm really looking forward to participate in GSoC 2016 if my proposal gets accepted! Regards, Parth Sane On Wednesday, 30 March 2016 22:25:23 UTC+5:30, Oleg Nenashev wrote: > > Hi, > >

[GSoC 2016] - Status update

Hi, Thanks again to all students and mentors for your hard work during about ten office hours and dozens of other calls/chats! Just a summary of the ongoing GSoC2016 activity: - We have successfully handled the student application period - We have got a bunch of proposals (mentors cannot

Re: [GSOC 2016] Jenkin website - Search Implementation

Yes, such project would be definitely interesting and useful to the community. Would be nice to see a proposal draft. Then we would be able to review it and make some suggestions. BR, Oleg среда, 23 марта 2016 г., 22:56:09 UTC+1 пользователь Aayush Ranaut написал: > > Hi, > > After discussion

Re: [GSOC 2016]External Workspace Manager

Thanks for your remind, I have completed the process Best regards, Johnson On Fri, Mar 25, 2016 at 6:34 AM, martinda < martin.danjo...@gmail.com [martin.danjo...@gmail.com] > wrote: Johnson, Please submit your final proposal as per the Google process. Google has a firm deadline, and I was

Re: [GSOC 2016]External Workspace Manager

Johnson, Please submit your final proposal as per the Google process. Google has a firm deadline, and I was told that their site can be slow to respond as the deadline approaches. Thanks, Martin On Tuesday, March 22, 2016 at 8:40:44 AM UTC-4, Johnson Li wrote: > > Sorry about that, I have

Re: [GSOC 2016] Support core plugin improvements

Hi all, I submitted my final proposal to google. Thanks a lot for your guidance and support. Hopefully looking forward to work on this project. Thanks again. Best regards On Thu, Mar 24, 2016 at 8:23 PM, Oleg Nenashev wrote: > IMHO it's ready to go. > Thanks for

Re: [GSOC 2016] Support core plugin improvements

IMHO it's ready to go. Thanks for polishing it! четверг, 24 марта 2016 г., 8:18:48 UTC+1 пользователь Arnaud Héritier написал: > > Perfect. Thanks a lot. > > Le jeudi 24 mars 2016, Minudika Malshan > a écrit : > >> Hi all, >> >> Thanks a lot for your feedback. >> @Arnaud

Re: [GSOC 2016] Support core plugin improvements

Perfect. Thanks a lot. Le jeudi 24 mars 2016, Minudika Malshan a écrit : > Hi all, > > Thanks a lot for your feedback. > @Arnaud : Yes I followed those guide lines when creating my proposal. > > I will go through the whole proposal one more time, finalize it and submit >

Re: [GSOC 2016] Support core plugin improvements

Hi all, Thanks a lot for your feedback. @Arnaud : Yes I followed those guide lines when creating my proposal. I will go through the whole proposal one more time, finalize it and submit the final proposal by tonight. Best Regards On Thu, Mar 24, 2016 at 12:12 PM, Arnaud Héritier

Re: [GSOC 2016] Support core plugin improvements

Minudika For me it seems that your proposal is conform to http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/ I think you are ready to submit it On Thu, Mar 24, 2016 at 4:35 AM, Steve Christou wrote: > Hello Minudika, > > I like the proposal! I have no

  1   2   >